| 开发者 | tazeenehsan |
|---|---|
| 更新时间 | 2026年8月16日 00:50 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv3 |
| 版权网址: | 版权信息 |
Install Header Footer Builder, click Add New under the Header Footer menu, design your header with Elementor or the block editor, then set display conditions to choose where it appears. No code, no theme file edits, no child theme needed.
Yes. Header Footer Builder adds Elementor support to its templates, so you can design any header or footer visually with the free version of Elementor. The plugin handles the display conditions and decides which template loads on each page.
No. Elementor Pro's Theme Builder is not required — Header Footer Builder provides the template system and display conditions itself, and works with the free version of Elementor.
Yes. Templates are standard WordPress custom posts, so the Gutenberg block editor works out of the box with no extra configuration.
Yes. Create a header template, open Conditions, add an include rule for Front Page, and save. That template appears only on your front page.
Yes. Create multiple header templates and give each its own display conditions. The plugin automatically picks the best-matching template for every page request.
Create a blank template (no content), add an include rule for that specific page, and it overrides the default. You can also add an exclude rule to a sitewide template to remove it from selected pages.
The plugin uses priority scoring: a rule targeting a specific page beats a rule targeting all pages, which beats a sitewide rule. If two templates still tie, the most recently published one wins.
Yes. Dedicated display conditions let you target single product pages, the cart, and checkout — perfect for a minimal checkout header that reduces cart abandonment.
Not yet with a dedicated condition — those are on our roadmap. Today you can still control them indirectly (for example with a sitewide header and an exclude rule), and a template assigned to "All Pages" will apply if the shop page is a standard WordPress page.
Not with a dedicated rule yet — built-in condition types currently cover posts and pages sitewide, plus specific individual posts/pages/categories/tags. Support for arbitrary custom post types is planned.
Tested with Astra, GeneratePress, OceanWP, Kadence, and Hello Elementor. It works with any theme that uses standard header and footer template regions.
No. Template matching runs a single efficient database query per page load. There are no external API calls, no tracking scripts, and no unnecessary assets loaded on the front end.
Yes — unlimited templates, all display conditions, Elementor and Gutenberg support, and WooCommerce targeting are all free.
Yes. The admin dashboard is powered entirely by custom REST API routes under the ultihefo/v1 namespace, templates are a standard custom post type, and conditions are stored in a single post meta field — all readable and writable with normal WordPress APIs. A ultihefo_demo_capability_check filter lets you change which capability is required to manage templates.
Yes. The plugin ships with a .pot translation template, so the admin dashboard and frontend strings can be localized into any language using standard WordPress translation tools.
The plugin works on standard WordPress installs. Network-wide multisite configuration is not yet supported.
wp_is_block_theme(), used since 1.0.1)ultihefo/v1 REST namespace and the ultihefo_demo_capability_check filter.pot file)