Problem: The client is experiencing issues with translating the homepages of their website into different languages using WPML. Specifically, the English version shows a Lithuanian slider, and the Estonian, Latvian, and Russian versions lack menus and footers. Additionally, an unwanted search box appears at the bottom of these pages. Solution: 1. To address the slider issue in the English version, we recommend using the method described in Creating Multilingual Sliders with Revolution Slider and WPML. 2. For the missing menus and footers in the Estonian, Latvian, and Russian versions, we have split the ticket to focus specifically on this issue. You can follow the progress and find solutions here: Menu and Footer Missing on Translated Homepage. 3. Regarding the search box appearing at the bottom, please confirm if this element should not be present, and we can provide further assistance on this matter.
Please note that the solution provided might be outdated or not applicable to your specific 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. If the issue persists, please open a new support ticket.
Problem: If you're experiencing issues where the translation method element is unclickable in the WordPress sidebar when trying to translate a product, it might be due to the translation method settings. Solution: First, check the translation method for the product in the WordPress sidebar. If it's set to "WordPress Editor" and you wish to use the WPML Translation Editor, you need to change this setting to "WPML Translation Editor". Additionally, if you are using Advanced Custom Fields (ACF) on this product, ensure that the ACF field groups are set to "Same fields across languages". This setting is necessary to use the WPML Translation Editor effectively. If your ACF field groups are set to "Different fields across languages", you will need to use the WordPress Editor as your translation method. For more detailed guidance on translating ACF fields, visit Translate sites built with ACF.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also highly suggest 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. For further assistance, please contact us at WPML support forum.
Problem: The client is experiencing issues with updating translations using the Classic Translation Editor in WPML. Instead of opening in the Classic Translation Editor, it redirects to the standard WordPress editor. Additionally, the English version of the page displays in Dutch, indicating a mix-up in source and translation languages. Solution: We recommend the following steps to resolve the issue: 1. Edit the Dutch language page and disconnect it from its translation. This can be done by following the instructions here: https://wpml.org/faq/how-to-disconnect-translations-from-the-default-language-page-or-post/ 2. After disconnecting, reconnect the page and set Dutch as the primary language.
If this solution does not apply to your case, or if it seems outdated, 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. If issues persist, please open a new support ticket at WPML support forum.
Problem: The client is experiencing an issue where ACF fields are not synchronized between English and German versions on their WordPress site, despite setting the fields to be translated and using ACF Pro in expert mode.
Solution: 1. We recommend using the 'Same on all languages' setting instead of 'expert mode' to ensure that all necessary information syncs automatically across different languages. 2. If 'expert mode' is necessary, consult the documentation to understand which option to use for each field type. 3. After adjusting the custom field translation mode, make a minor change in the original language version of the page (e.g., add an extra space) and save it. This should prompt an update in the translated versions. 4. If fields still do not appear synchronized, the client found success by exporting the Post Type and Group Fields via the ACF tool, removing them, and then reimporting them, which forced synchronization.
If these steps do not resolve the issue or if the solution seems outdated or irrelevant, we highly recommend checking related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If problems persist, please open a new support ticket.
