Problem: The client reported that translations originally created with the Classic Translation Editor (CTE) were unexpectedly opening in the Advanced Translation Editor (ATE), despite the setting to use ATE for older translations being disabled. Solution: We investigated and found that the posts in question had been previously edited using ATE, which caused them to continue opening in ATE. We manually switched the editor for the specific post back to CTE. To prevent this issue, ensure the option 'Use also for old translations created with the Classic Translation Editor' remains unchecked in WPML → Settings. If you encounter similar issues or prefer to use CTE for other posts, please inform us, and we can apply the same adjustment.
Please note that this solution might not apply to your case if it's outdated or not relevant. 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 experiencing issues with translations not being saved in the WPML Translation Editor. Specifically, translations disappear when moving to the next segment, and only a fraction of translations are saved after multiple attempts. Solution: 1. Update all WPML components: Ensure that all WPML plugins are updated to the latest versions available. 2. Increase PHP Configuration Limits: Increase the
max_input_vars
to 10000 and the WP memory limit to at least 256MB. These changes can be made in the
php.ini
,
.htaccess
, or
wp-config.php
files. 3. Clear Caches: Clear all caches including WordPress site cache and browser cache to ensure new settings take effect.
If these steps do not resolve the issue or if the solution seems 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 problems persist, please open a new support ticket for further assistance at WPML support forum.
Problem: The client is experiencing an issue where some H1 and H2 tags remain in English on the Dutch version of a page, despite the translation showing as complete in WPML. Solution: We discovered that the issue was due to missing translation support for the Elementor Title widget. We resolved this by adding the following XML configuration to WPML -> Settings -> Custom XML Configuration:
To apply these changes, follow these steps: 1. Visit the original New Zealand page in English and make a minor edit, then save. 2. Edit the Dutch translation and apply the changes to the title texts. 3. Ensure the translation is marked as 100% complete. This should ensure that the titles display correctly in Dutch.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we recommend opening a new support ticket. We also 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. For further assistance, please visit our support forum at https://wpml.org/forums/forum/english-support/.
Problem: The client is experiencing duplicated content on product detail pages when WPML is disabled. This issue persists even after disabling the Elementor Pro template and creating a new product detail page template. Solution: We identified that the duplication occurs because the underlying database query retrieves multiple products that share the same slug. This is not specific to WPML; it also happens without WPML if multiple products have identical slugs. To resolve this, the client needs to ensure that each product has a unique slug. This can be achieved by either cleaning up the database entries or manually adjusting the slugs to follow the standard setting of 'Auto generate from title (default)'. For illustration, here is a sandbox example demonstrating the same behavior with identical slugs.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also 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. For further assistance, please visit our support forum.
