Problem: The client is experiencing an issue where the header overlaps with the content on many translated pages, and the header does not inherit the style of the original page.
Solution: First, we recommend checking the display conditions in the Elementor Header Footer Builder. If the conditions are set for specific pages in one language, they may not apply correctly to the translated pages. To fix this: 1. Go to Appearance > Elementor Header Footer Builder and filter for the translated language. 2. Open the translated templates and locate the "Display on:" section. 3. Remove the current conditions for the Spanish versions of the WooCommerce pages. 4. Search for and add the correct translations of those pages, then save the template.
Another solution involves translating the display conditions using the WPML Translation Editor: 1. Navigate to WPML > Settings > Custom Field Translation and set
ehf_target_include_locations
and
ehf_target_exclude_locations
to "Translate". 2. Edit and save the original template, then translate it using the WPML Translation Editor. 3. In the Translation Editor, translate the post IDs to match the IDs of the translated pages. For assistance in finding post IDs in WordPress, refer to this guide.
We are also considering implementing a WPML Hook inside the "Elementor Header & Footer Builder" for automatic display condition adjustments in each language, which may require cooperation with the plugin author.
If these solutions do not seem relevant to your situation, please open a new support ticket with us for further assistance.
Problem: The client is experiencing an issue where the header overlaps with the content on many translated pages, and the header does not inherit the style of the original page.
Solution: We recommend checking the page builder or theme to identify the custom field that contains the page styling, which may include terms like "style", "css", "layout", or "styling". This custom field should be set to "copy" in WPML's settings to ensure the style is carried over to the translated pages.
To do this: 1. Go to WPML → Settings and locate the Custom Field Translation section. 2. Search for the terms "style", "css", "layout", or "styling" to find the relevant custom fields. 3. If no results appear, click on "Show system fields" to reveal hidden fields. 4. Once identified, set the custom field to "copy". 5. Make a minor edit to the original language page and save it. 6. Open the translated page and save it again to copy the CSS over.
Problem: The client is experiencing issues with a sidebar used to filter products on a tour page. The sidebar is not translated into other languages, and filtering does not work on the translated tour pages, resulting in zero results. Additionally, the client is unable to generate links for filtered products under different categories in the translated languages.
Solution: 1. To translate the strings in the filters, we recommend following the steps in our guide on Translating Widgets. 2. If there are strings that are not available for translation, please refer to our guide on Finding Strings that Don’t Appear on the String Translation Page. 3. We also request that the client provides a step-by-step description of how to edit the configuration in these filters to better understand the scenario. 4. Additionally, we ask for temporary access (wp-admin and FTP) to the site to investigate the issue more thoroughly. It is important to back up the site before providing access to ensure safety.
If this solution does not seem relevant to your situation, please do not hesitate to open a new support ticket with us.
Then, make sure that ElementsKit's Templates are translated and have properly set the Type as "Active" and matching display condition in each language.
Problem:
The Tripgo Theme from Ovatheme is adding custom fields "General Settings" to each content on the WordPress Editor which allows you to set a Header, Sidebar, or Footer Template per content.
On the translated content the template do not show up.
Solution:
First, make sure that your Templates are translated.
Then go to WPML > Settings > Custom Field Translation and set the following fields to "copy":
