Jan Gerald Starosa

Hi @itapress ,

Thank you for bringing this to our attention! You’re absolutely right, the translation files bundled within the plugin are currently taking priority over the community-contributed translations from ww.wp.xz.cn.

Our developers are already working on an update to the plugin’s translation structure to ensure the ww.wp.xz.cn files are recognized automatically.

In the meantime, the solution you found is exactly what we recommend: manually deleting the Dutch language folder inside the plugin’s /languages directory.

This allows the system to pull the 100% complete translations from the web.

Could you please confirm if everything is working perfectly on your end after removing that folder?
We’ll make sure the permanent fix is included in our very next update!

Regards,

Hi @sevenstarsystems ,

thanks for reporting this!

We looked into the code and couldn’t reproduce a case where UAE/HFE removes
the tag, hfe-header.php calls wp_head() before we clear its hooks, so the title should always be rendered. That said, we’d like to dig deeper to confirm whether something specific to your setup is triggering this.

Before applying the workaround, we’d caution against it, it reads raw post meta from SEO plugins, which store title templates (e.g. %%title%% %%sep%% %%sitename%% in Yoast, %title% %sep() %sitename% in Rank Math), not the final rendered strings. The fix would inject those unprocessed variables directly into <title>, which would likely hurt SEO more than a missing tag would.

Could you share a few details so we can investigate properly?

• Which theme you are using?
• Which SEO plugin (Yoast, Rank Math, AIOSEO, or none)?
• In the HFE settings, which compatibility mode is selected – Default or Option 2?
• Is this happening on all pages or specific ones?
• Can you share a URL where we can inspect the rendered HTML?

We want to make sure we fix the root cause rather than patch over it.

Thanks!

Hi @julisazavala3 ,

Thanks for reaching out!

That’s a great question. To set this up, go into the settings for your homepage header and locate the Display Conditions (or ‘Display On’ settings). From there, choose ‘Front Page’ to assign it specifically to your homepage.

Please let me know if it displays as expected once you save those changes!

Regards,

Hi @alijonab332 ,

Thank you so much for reaching out, and I completely understand how frustrating it can be when everything looks perfect in the builder but doesn’t appear on the live site, you’re definitely not alone, this is one of the most common (and thankfully easy to fix) issues with the UAE plugin. Let’s get it sorted for you.

In almost every case, the cause is one of the following. Could you please check them in order?

1. Display Conditions aren’t set (this is the #1 reason, 9 times out of 10) Your header/footer template needs to be told where to appear on the site.

• Go to Appearance → Header Footer Builder and open your template.
• In the right-hand sidebar, find the “Display On” box.
• Click Add Condition and choose something like “Entire Website”, or target specific pages/post types as needed.
• Click Update.

Without at least one display rule, the layout will only ever render inside the editor.

2. The template is still a Draft Please double-check the template status is Published, not Draft or Pending Review.

3. Your theme may need “Theme Support” enabled The plugin works out of the box with Astra, Hello Elementor, GeneratePress, OceanWP, Kadence, and Genesis. If you’re using a different theme:

• Go to Appearance → Header Footer Builder → Theme Support
• Follow the instructions shown there (usually a one-line snippet to register support).

4. Your theme’s built-in header/footer is overriding ours Some themes render their own header/footer first. In your theme’s Customizer, try disabling the theme header/footer so our template can take over. (In Astra, for example: Customizer → Header Builder / Footer Builder → disable.)

5. Caching or CDN is serving an old version If you use WP Rocket, LiteSpeed, W3TC, or Cloudflare, please clear:

• Plugin cache → Server cache → Browser cache → CDN cache

6. Elementor CSS needs regenerating Head to Elementor → Tools → Regenerate CSS & Data, and also click Sync Library.

7. Plugin/theme conflict If none of the above works, please temporarily deactivate all plugins except Elementor and our plugin, switch to the Hello Elementor theme as a test, and check whether the header/footer appears. If it does, you can reactivate plugins one by one to identify the conflict.

Hi @nsluc93,

Thank you for the detailed follow-up and for sharing those debugging steps, that level of detail is really helpful!

What you’re describing, Atomic CSS loading correctly on regular pages but not enqueuing for Theme Builder templates (footer/header), points to a rendering context issue with how Elementor 4.x’s Atomic Styles Manager handles templates outside the main post loop. Theme Builder templates are rendered at a different point in the WordPress loading cycle, which can cause the Atomic CSS enqueue hook to miss those templates entirely.

Looking forward to assisting you further!

Best regards,
Jan – BSF Support Team

• This reply was modified 1 month, 3 weeks ago by Jan Gerald Starosa.
• This reply was modified 1 month, 3 weeks ago by Jan Gerald Starosa.
• This reply was modified 1 month, 3 weeks ago by Jan Gerald Starosa.

Hi @athena1979,

Thank you for reaching out!

The {SocialShare} in the mailto link is a dynamic placeholder that gets replaced with the page or post title when the link is rendered, so the email subject and body should display the actual title rather than the literal token.

That said, the Social Share widget currently does not include a built-in option to fully customize the email subject or body text from the widget settings. This would require custom development work, which is outside the scope of our support.

If this is a feature you’d like to see added natively, we’d encourage you to submit a feature request – We also track feature requests on our official ideas board if you’d like to submit or vote there.

We appreciate your understanding, and please don’t hesitate to reach out if you have any other questions!

Hi @juliereader ,

I wanted to follow up on this ticket, as I haven’t heard back from you in a couple of weeks.

I’m going to go ahead and mark this as ‘resolved’ for now to keep our queue organized.

If you are still experiencing this issue or have any new questions, please feel free to open a new ticket or reply here, and I’ll be happy to jump back in and assist you!