Problem: The client reported that the default language content is displayed instead of the translated content, specifically for string translations, while other site contents render correctly in the translated language. This issue was observed on a site using the Radiant Curacao child theme, and it was noted that the untranslated strings were from custom Gutenberg blocks and other theme elements like custom post types.
Solution: 1. We recommended increasing the WordPress memory limit to at least 256MB by adding the following code to the wp-config.php file:
2. We advised checking for cache issues or persistent object caching that might interfere with WPML string rendering. 3. The untranslated strings in the homepage were identified as coming from custom Gutenberg blocks that hadn't been registered with WPML. To resolve this, the client needed to register these blocks for translation, which could be done following the guide at https://wpml.org/documentation/support/language-configuration-files/make-custom-gutenberg-blocks-translatable/.
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 reported that ACF-Extended form messages and attributes were not syncing correctly. Although the values appeared in the string translator, they were not displayed correctly on the frontend. Specific messages like "Validation failed. 8 fields require attention" and "Form updated" remained untranslated despite having translations assigned in the string translation editor. Solution: We recommended enabling the translation for ACF-Extended forms in WPML settings. Here are the steps we followed: 1. Navigate to WPML > Settings > Post Types Translation. 2. Find 'Forms (acfe-form)' and select 'Translatable - only show translated items'. This adjustment should ensure that the forms and their respective messages display the correct translations on the frontend.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we highly recommend checking the related known issues and verifying that you have installed the latest versions of themes and plugins. If the problem persists, please open a new support ticket.
Problem: The client was experiencing issues with translations not appearing on the live website using WPML's Advanced Translation Editor (ATE). Additionally, the return paths for translations were incorrect, and there were issues with Gutenberg block content not being recognized by WPML. Solution: We first verified that the translations were appearing correctly on the specified page. To address the issue with Gutenberg blocks, we provided a custom XML configuration to be added in WPML > Settings > Custom XML Configuration. The client was advised to add the following code:
Additionally, we suggested creating a new page with similar content to see if the issue with duplicates persists, indicating a possible conflict with the theme or another plugin.
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 problem persists, please open a new support ticket.
