BugWP logo BugWP
Back to Community
Home / Community / Plugin → Royal elementor addons and templates

How to Fix Header and Footer Translation Issues with Royal Elementor Addons and Polylang/WPML

17 threads Sep 7, 2025 Plugin → Royal elementor addons and templates

Content

Understanding the Translation Challenge

A common issue reported by users of the 'Royal Elementor Addons and Templates' plugin is difficulty translating Theme Builder templates, specifically headers and footers, when using popular multilingual plugins like Polylang or WPML. Users often find that while page content translates correctly, the header and footer templates stubbornly remain in the original language on the front end.

Why Does This Happen?

Based on community reports, this is not a simple bug but a complex compatibility challenge. The 'Royal Elementor Addons and Templates' plugin builds its templates in a specific way. Multilingual plugins sometimes struggle to detect and replace these dynamic template parts on the front end after translation. The issue is often related to how the templates are registered and called by the theme, rather than a fault with the translation process itself.

Common Solutions and Workarounds

1. The Conditional Display Method (for Polylang)

This is a frequently mentioned manual workaround that many users have found success with.

  1. Create separate header and footer templates for each language (e.g., "Header - English," "Header - Spanish").
  2. In the Elementor Theme Builder, edit each template and click on 'Display Conditions'.
  3. For your English header, set a condition to show on 'Entire Site' AND 'Language: English'.
  4. For your Spanish header, set a condition to show on 'Entire Site' AND 'Language: Spanish'.
  5. Repeat this process for your footer templates.

This method bypasses the direct translation system and instead uses the theme builder's native conditional logic to serve the correct template.

2. Ensure Proper Integration Plugin is Active

For Polylang, many threads mention using the 'Connect Polylang for Elementor' bridge plugin. For WPML, ensure the 'WPML String Translation' and 'WPML CMS Navigation' modules are active. These plugins are often essential for handling Elementor and theme builder translations correctly.

3. Check String Translation (for WPML)

If individual strings from addons (like button text) are not translating:

  1. Navigate to WPML → String Translation.
  2. Ensure the context for scanning is set correctly. Sometimes strings are registered under a different domain.
  3. If strings are missing, use the 'Scan for strings' function to force WPML to find translatable text within the plugin's modules.

4. Recreate vs. Translate

Some users have reported that using the 'Duplicate' function in WPML to create a new translated template, rather than translating the existing one, can sometimes yield better results. However, you must then manually set the language and translation relationships for the new template within your multilingual plugin's settings.

When to Seek Further Help

If these steps do not resolve the issue, the problem may be specific to your site's configuration. The 'Royal Elementor Addons and Templates' team often requests system information to replicate issues. You can provide this by:

  1. Going to Tools > Site Health > Info and clicking "Copy site info to clipboard."
  2. Exporting your site's content via Tools > Export.

Providing this information can help them debug complex, environment-specific conflicts.

Conclusion

Translation issues with headers and footers are a known point of complexity. The most reliable solution is often the manual conditional display method. Since compatibility relies on integration between two major plugins, it's also recommended to ensure both 'Royal Elementor Addons' and your chosen multilingual plugin (Polylang/WPML) are updated to their latest versions to benefit from any recent compatibility improvements.

Related Support Threads Support