Problem: The client was unable to translate a custom link field ('Case Study') associated with a custom post type ('Customer') using WPML's Advanced Translation Editor (ATE), despite having set the ACF fields as translatable. Solution: We recommended checking if using the Search option in ATE would return the URLs needed for translation. We also suggested testing with a different ACF field type, specifically the URL field, to see if the issue persists. After further investigation and consultation with our second-tier support, we escalated the issue for deeper analysis. We provided a video guide and an errata page (https://wpml.org/errata/advanced-custom-fields-external-links-are-not-translatable-in-same-fields-across-languages-mode/) explaining the steps to make the link field translatable. Finally, our second-tier specialists confirmed the solution by applying specific code, as shown in another video (https://www.loom.com/share/813a329ec1c54627a3c2e3f5c4ada205).
If this solution does not resolve your issue, 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 the problem persists, please open a new support ticket at WPML support forum.
Problem: The client reported that the translated versions of their pages were not displaying the correct localized URLs, despite being correctly configured in the Advanced WPML Editor. They use the Greenshift plugin for page building, and previously, link translations worked correctly. However, recently, the translated links were not reflecting on the frontend even though they appeared correct in the WPML Advanced Translation Editor.
Solution: We advised the client that each Custom Gutenberg Block requires a proper XML configuration to be translatable with the WPML Translation Editor. The Greenshift plugin includes a configuration, but it was not capturing links. We provided a custom XML configuration to address this issue:
We instructed the client to save this configuration in WPML > Settings under the "Custom XML Configuration" tab, then edit the block on the original content, save the page, and update the translation. We also escalated the issue to our compatibility team to reach out to Greenshift.
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 further assistance is needed, please open a new support ticket at https://wpml.org/forums/.
Problem: If you're trying to fix technical SEO issues like improper URLs and need these changes to propagate to different language versions of your site, you might encounter issues where changes do not always apply. This could be due to issues in the Media Translation add-on, specifically causing double slashes (//) in media links. Solution: First, ensure you have a backup of your site. Then, if you're comfortable with code changes, you can manually edit the file at
Save the changes. However, this is a temporary workaround. We have released WPML 4.9.3, which includes a permanent fix for this issue. You can download the new version from https://wpml.org/account/downloads/. After updating, you can remove the manual code edit.
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 unable to access and edit the translation of the navigation block for footer menus using WPML’s Advanced Translation Editor. They need to update incorrect translated links and manage visibility of links per language. Solution: 1. To edit the links in the translated footer content, access the site editor here: Site Editor Link. 2. After updating the links, navigate to WPML > Translation Management > Site Templates, find 'Footer – Template Part', and resend it for translation. 3. If a different footer for each language is required, editing must be done manually for each language, as shown in this screen recording: Screen Recording. 4. Alternatively, replace the template part with a reusable block that conditionally displays footer links based on the current language using WPML conditions. This allows the same reusable block to dynamically show appropriate footer links across all languages.
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.
Problem: If you're experiencing issues where the translated content of your custom post types is displayed using the default single post template instead of your custom template, this might be due to the templates not being translated. Solution: We recommend translating your Site Templates and Template Parts to ensure they apply correctly in different languages. First, check if these templates are available for translation at WPML > Translation Management > Dashboard. If they are not translated, create a translation job for each template or template part. You can then access and complete these translations to 100% using the WPML Translation Editor or automatic translation at WPML > Translations. Additionally, be aware of potential display condition issues when editing templates in a second language within the Site Editor. A workaround for this issue can be found at https://wpml.org/errata/template-is-not-applied-to-translated-page/.
Please note that this solution might be irrelevant if it's outdated or not applicable 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 issue persists, please open a new support ticket at WPML support forum.
Problem: The client is using the GreenShift Builder with WPML to build and translate their website. While translating the homepage using WPML’s Advanced Translation Editor, the translated version displays the default language content instead of the translated content. Additionally, an error in the backend indicates that the block contains unexpected or invalid content, prompting a block recovery message. Solution: We resolved the issue by updating the GreenShift plugin and its add-ons to the latest version. It is crucial to follow the correct WPML translation process and avoid editing the translated content directly in the Gutenberg editor. After these updates and following the proper procedures, we tested the system thoroughly and confirmed that everything is now working as expected.
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.
Problem: The client is developing a site and wants to set up the primary .com domain in American English with a directory for British English. Solution: 1. Go to WPML > Languages > Site Languages and click "Edit Languages". 2. Add a new custom language using the language code "en-us" for American English. By default, the pre-installed English in WPML uses the locale en_US. Change this to en_GB for British English. 3. You can upload custom flags for each language. Find flags ready to use in WPML's plugin folder on the server. For more details on custom flags, visit Guide for flags. 4. In WPML > Languages > Language URL format, select "Different languages in directories" and save the WordPress Permalinks if you adjust this option. 5. Ensure that American English is set as the Site Default language in WPML > Languages > Site Languages.
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 this does not resolve your issue, please open a new support ticket at WPML support forum.
