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.
Problem: The client is experiencing an issue where the name of a Custom Post Type (CPT) is not displaying correctly in breadcrumbs. Specifically, the translated version of the CPT is not showing up on the page.
Solution: We have identified this as a known issue related to the Advanced Custom Fields plugin version 6.1, which introduced the ability to register custom post types and custom taxonomies. Currently, WPML does not support translating the labels associated with these features. We have confirmed the problem exists by reproducing it on a test site.
Unfortunately, there is no workaround available at this time. However, we are actively working on a solution to support these new features in the Advanced Custom Fields plugin. We have escalated this matter and are monitoring it closely. While there is no estimated time of arrival for the fix, we recommend bookmarking the errata page at https://wpml.org/errata/advanced-custom-fields-6-1-custom-post-types-and-custom-taxonomies-labels-not-translatable-yet/ to stay updated or subscribe to the comments on that page for notifications.
Once the issue is resolved, we will provide an update through this ticket.
If this solution does not seem relevant to your situation, please do not hesitate to open a new support ticket at our support forum.
