Problem: If you're experiencing an issue where WPML requests the translation of an entire page after updating a single block on your homepage, this is due to the Advanced Translation Editor (ATE) treating modified content as new because there's no translation memory match for the updated paragraph. Solution:
Since the paragraph content was modified and there is no existing translation memory match for the updated paragraph, the Advanced Translation Editor treats it as new content and requires it to be translated again as a new paragraph. However, the existing translation will still be displayed on the front-end.
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. Should you need further assistance, please open a new support ticket at WPML support forum.
Problem: If you're experiencing an issue where your Hungarian translations have disappeared from your website, and previously translated content is no longer visible, it might be due to a synchronization issue or a plugin error. Solution: We recommend checking if the ACF Field Groups are set to "translatable" and if only Hungarian was translated. By default, the ACF Field Groups should be set to "do not translate". If they are set incorrectly, removing the translation should resolve the issue. Additionally, ensure that you have the latest versions of themes and plugins installed. If the problem persists, consider checking for any plugin errors that might have been reported by your WordPress system.
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 these steps do not resolve the issue, please open a new support ticket.
Problem: The client is facing an issue where the text in the WPML Advanced Translation Editor (ATE) does not match what appears on the frontend. This discrepancy persists even after updating the content via ATE. The problem is suspected to be linked to the Speed Optimizer plugin, which might not be compatible with WPML. Solution: We recommend contacting the support team or developers of the Speed Optimizer plugin to inquire about its compatibility with WPML. If the plugin is found to be incompatible, suggest that the developers join our Go Global program, where our Compatibility developers will assist in making their product fully compatible with WPML at no cost.
If this solution does not resolve your issue or seems outdated, please check the related known issues, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket here.
If this solution does not resolve your issue or seems irrelevant due to being 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 needed, please open a new support ticket at WPML support forum for further assistance.
Problem: If you're experiencing issues where translated content does not appear on the frontend, and the translated page is completely blank in Bricks Builder after using the Advanced Translation Editor, this might be due to a specific bug or conflict. Solution: We recommend you try the following steps to resolve the issue: 1. Go to the Pages tab and switch the language to a secondary one using the flag in the top-bar. 2. Send the translation to the Trash Can. 3. Remove the translation from the Trash Can (completely delete it). 4. Repeat these steps for every problematic page. 5. Re-translate the page. Note that WPML saves your translations in the Translation Memory, so you won't need to recreate the translations from scratch. Simply add the translation and save. All the fields will already be translated for you.
If this solution does not resolve your issue or seems irrelevant due to being 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 problem persists, please open a new support ticket.
