403Webshell
Server IP : 108.167.142.43  /  Your IP : 216.73.217.58
Web Server : Apache
System : Linux gator4174.hostgator.com 5.14.0-687.39.1.el9_8.x86_64 #1 SMP PREEMPT_DYNAMIC Tue Aug 18 06:09:16 EDT 2026 x86_64
User : delarice ( 2406)
PHP Version : 8.3.36
Disable Function : NONE
MySQL : OFF  |  cURL : ON  |  WGET : ON  |  Perl : ON  |  Python : OFF  |  Sudo : ON  |  Pkexec : ON
Directory :  /home2/delarice/public_html/wp-content/plugins/header-footer-elementor/inc/

Upload File :
current_dir [ Writeable ] document_root [ Writeable ]

 

Command :


[ Back ]     

Current File : /home2/delarice/public_html/wp-content/plugins/header-footer-elementor/inc//architecture.md
---
module: core
owner: UNKNOWN
---

# core

## Responsibility

- The plugin boot/core layer. `Header_Footer_Elementor` is the singleton entry point: it gates on Elementor availability, detects the active theme and loads the matching compat adapter, wires the global hooks, and pulls in every other module via `includes()`. `hfe-functions.php` holds the header/footer/before-footer render + enabled-check helpers the whole plugin calls.
- Stops at the subfolder boundaries (`abilities/`, `angie/`, `compatibility/`, `lib/`, `settings/`, `widgets-manager/`) and `admin/`, `themes/` — it only `require`s them, never defines them.

## Why it is this way

- Every include and hook sits behind an Elementor-availability gate because the plugin is inert without Elementor; boot order is hand-tuned so the render helpers exist before anything calls them.
- Analytics is deliberately loaded after theme detection (outside `includes()`) so its event logic sees the theme-support options the constructor has already written.

## Related ADRs

None yet.

Youez - 2016 - github.com/yon3zu
LinuXploit