Problem: You are experiencing an issue where string translations revert to previous versions even after clearing the cache in WPML and the W3 Total Cache plugin, and deactivating the latter. The server does not have cache functions. Solution: The issue might be related to how textdomains are loaded in your theme or plugins, especially with the changes introduced in WordPress 6.7. We recommend checking if your theme or any plugins are using an outdated method to call textdomains. You should discuss this with your theme's developer. For more details, see the discussion on WordPress support.
If this solution does not apply to your case, or if it becomes outdated, we highly recommend checking related known issues at WPML 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: You are using WPML with ACF Multilingual and have encountered an issue where the custom post type's permalink works as expected in the primary language (English), but the permalink structure is broken in a secondary language. Solution: This behavior might be expected due to the design of ACF's custom post types (CPT) functionality, which may not fully support multilingual permalink structures. We recommend setting up a staging environment to conduct further tests and identify a possible solution. If this issue persists, check if the post is published as a Draft.
Problem: The client is experiencing issues where the WPML translation editor does not display the target language texts of block contents in post_content, despite the normal WordPress editor showing the target language texts. The client is using WP Import Export Lite and Really Simple CSV Importer for data migration.
Solution: 1. This is a recognized issue with the WPML plugin. We are aware of the problem where translated content does not show in the translation editor after import. Our developers are currently working on a solution. For updates, please check the errata page: WPML All Import - Imported posts don't show the translated content in the translation editor. 2. The code "{"translatedWithWPMLTM":"1"}" found in the blocks of the target language contents is a leftover from the previous website and is not causing the issue. 3. Switching to WP All Import PRO will not resolve this issue as the necessary feature is still under development.
If this solution does not apply to your case, or if it seems outdated, we highly recommend opening a new support ticket. Also, check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. For further assistance, please visit our support forum at WPML support forum.
