Problem: The client has a WPML website with many ACF groups, including clones with repeaters inside. Despite setting translation preferences correctly, many fields set to 'Translate' do not appear in the Advanced Translation Editor (ATE) or get translated automatically via the Translation Dashboard. Solution: The issue was due to clone fields used multiple times on a single page where some inner fields had the same name, set to seamless without a field name prefix. This caused problems with translating specific sections. The solution involved: 1. Activating an inactive field group. 2. Synchronizing field translation preferences with JSON using the ACF tools. 3. Resaving the original homepage and its translations. For detailed steps on setting translation preferences for ACF fields and synchronizing them with WPML, visit WPML documentation.
If this solution does not resolve your issue, or if it 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. If needed, please open a new support ticket at WPML support forum.
Problem: You are using WPML with WP Recipe Maker (WPRM) and encountering issues where the recipe card in a translated post does not automatically switch to the corresponding translated recipe. Instead, it retains the original English recipe card, requiring manual replacement to display the correct language version. Solution: This behavior is expected as per the plugin author’s documentation. WPRM treats recipes as independent custom post types, and when inserted via a shortcode like
[wprm-recipe id="123"]
, the ID is treated as a static reference. To address this, you can use the XML configuration approach you've set up. After saving the XML configuration, you should open the translation in the WPML editor, search for the recipe ID, and manually replace it with the corresponding translated recipe ID. This manual step is necessary because WPRM does not support automatic translation or ID switching for recipe cards.
If this solution does not resolve your issue or seems outdated, we 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client needs to translate a form created with Metform into Greek, but Metform is not compatible with the WPML Translation Editor. Solution: 1) Set the 'Forms (metform-form)' to 'Translatable, only show translated items' in WPML > Settings > Post Type Translation. 2) Translate the forms directly in Metform > Forms. Each translated form will have a unique shortcode. Manually place the correct shortcode on each page for each language. 3) Use the WordPress Editor as a translation method and create each form in Elementor. Follow this guide: Using different translation editors for different pages. 4) After creating a Greek form, scan MetForm for new strings at WPML > Theme & Plugin Localization and revise WPML > String Translation for strings from MetForms. 5) If these steps do not resolve the issue, consider using a compatible form plugin such as Contact Form 7 or WP Forms, listed here: WPML compatible form plugins.
Please note that this solution 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 at WPML support forum.
Problem: The client installed the WPML plugin and translated almost the entire website, but the menu remains in Italian when switching languages. The menu is created using the Divi Theme Builder and the Divi Menu Flex plugin, with each item linking to a Divi Layout used as a submenu. Solution: We checked the client's setup and restored the default WPML translation settings for the Divi Theme Builder as per the recommended defaults found here: https://github.com/OnTheGoSystems/wpml-config/blob/master/Divi/wpml-config.xml. After restoring the settings, we saved the default header template and translated it via WPML → Translation Dashboard, which corrected the menu appearance in the secondary language. However, since the client is using the DiviMenus plugin, a third-party solution, some elements were still not being translated or copied properly. This issue requires WPML compatibility within the plugin itself, typically involving adding proper XML configuration and implementing WPML hooks in the plugin code. We recommend contacting the plugin author and sharing the following documentation with them to achieve WPML compatibility: https://wpml.org/documentation/support/achieving-wpml-compatibility-for-your-themes-and-plugins/ and https://wpml.org/documentation/support/go-global-program/.
If this solution does not resolve your issue or 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: You are developing a website using the Ekko theme with WPBakery and encountering issues where page components are not available for translation in the Advanced Translation Editor. You have tried adding a custom XML configuration, but it did not resolve the issue. Solution: Each custom page builder widget requires a proper configuration to be translatable with the WPML Translation Editor. This configuration is typically the responsibility of the theme or plugin author. Since your theme is marketed as WPML-compatible, we recommend contacting KeyDesign to report the issue (https://keydesign-themes.com/). Additionally, you can create a custom XML configuration yourself and save it at WPML > Settings > Custom XML Configuration. For guidance on maintaining compatibility with WPML, you can refer to our WPML Developer Guide (https://wpml.org/documentation/support/maintaining-wpbakery-page-builder-compatibility-with-wpml/). If you need further assistance, feel free to contact us, and we can help you create configurations for one or two widgets.
Please note that this solution might be outdated or not applicable to your specific case. We highly recommend checking related known issues (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 for further assistance.
Problem: You are working on a site under development and trying to translate custom Ninja Form fields using WPML, but you couldn't find any documentation on how to do this. Solution: We have resolved this issue in the latest version of the plugin. Please ensure that you update your plugins. After updating, use the following filter to set the configuration for Ninja Forms:
This code snippet should help you configure the translation settings for your custom fields in Ninja Forms.
If this solution does not apply to your case, or if it seems outdated, we highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If you still face issues, please open a new support ticket.
Problem: You have used Elementor to tag a container as a link, selecting a dynamic link to a page. However, after translating the page, the link does not redirect to the appropriate language version but instead leads back to the main language. Solution: We recommend trying to replace the dynamic URL with a custom URL to see if this resolves the issue.
If this solution does not apply to your case, or if it seems outdated, please check the related known issues and verify that you have installed the latest versions of themes and plugins. If the problem persists, we encourage you to open a new support ticket at our support forum for further assistance.
Problem: If you're experiencing issues where a radio button is not translated correctly on your site, such as 'ledigt', 'udlejet', and 'reserveret' still appearing in Danish, the issue might be with how the choices are set in your ACF fields settings. Solution: We recommend checking your ACF fields settings. For example, the choices should be set like this:
red : Red
Once this is set, you need to translate 'Red' in the string translations to ensure it displays correctly in your desired language. In your current setup, it appears that the choices only have values and not labels, such as:
DKK pr. plads
DKK pr. m²
DKK pr. måned
Please modify these choices as recommended.
If this solution does not apply because it's outdated or not relevant 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. If issues persist, please open a new support ticket at WPML support forum for further assistance.
Problem: The client has translated Term Meta to Portuguese via WPML's Translation Dashboard under Yoast SEO > Term Meta, but the Term Meta of their taxonomies still appears in English in the backend, although it is correctly translated on the frontend. Solution: 1. We have identified that Yoast SEO term metas are not stored using the standard WordPress API but as a serialized option, which can lead to issues if the data becomes too large. 2. To manage translations, we recommend using the WPML Translation Dashboard to translate Yoast SEO term meta, ensuring it displays correctly on the frontend. 3. If editing is necessary, it should be done via the Advanced Translation Editor (ATE), and the term meta should be re-sent for manual translation if it was initially auto-translated. This will not incur additional credits as the translations are saved in ATE's translation memory. 4. We are considering implementing a feature where the Yoast SEO term meta field in the backend will be locked with a recommendation to use ATE for translations, to prevent issues with direct edits.
Please note that this solution 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: The client reported that slides are not being translated despite following the guidance provided in the WPML errata for the Woodmart theme. Solution: We first asked the client to confirm if they are using the latest version of their theme, as the issue might have been resolved in a recent update by the theme author. We also requested screenshots to understand how the slides are built or configured. Additionally, we suggested making a minor change to a slide, updating it, and then checking if it appears in WPML → Translation Dashboard.
If this solution does not resolve your issue, or if it 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. If the problem persists, please open a new support ticket.
