Problem: The client needed to remove a translated 'Standard Header' Elementor template from their WPML translation and was unsure how to proceed. After successfully deleting the translated header, the header appeared blank, indicating a potential issue with display conditions or caching.
Solution: 1. To remove the translated header, switch to the target language, navigate to Templates → Theme Builder, locate the translated 'Standard Header', and delete it. 2. To address the blank header issue, ensure the default header's display conditions cover all languages and clear the site's cache. This includes: - Editing the default header in Elementor and setting display conditions to 'Entire Site'. - Clearing Elementor's cache and any other site caching. 3. If the header still doesn't appear, make a minor edit to the default header to trigger an update, ensure the translation status is synchronized, and check the menu settings in the affected language.
If these steps do not resolve the issue or if the solution seems outdated or irrelevant to your case, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. Should further assistance be needed, please open a new support ticket at WPML support forum.
Problem: The client created a custom language, Afrikaans, with the code af-za by mistake and needs it to be /af/ to match the site they are migrating. They have already translated content and cannot start over but are unable to change the language code in WPML. Solution: Unfortunately, you cannot directly change the language code of an existing custom language in WPML. However, you can preserve your translations by transferring them to a new custom language with the correct code. Here are the steps to do this safely: 1. Navigate to WPML → Languages and add a new custom language for Afrikaans with the correct code (/af/). 2. Manually transfer your translations from the old language code (af-za) to the new one (/af/).
If this solution does not apply to your case, or if it seems outdated, we recommend checking the related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If further assistance is needed, please open a new support ticket at our support forum.
