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 needs to translate full pages on their site using WPML and is facing issues with the new version where the option to save each sentence individually is missing. This results in some translations not being saved and some being flagged incorrectly. Solution: We recommend using the new Advanced Translation Editor (ATE) which automatically saves the segments as you translate. However, if you prefer to manually save each segment, you can do so by pressing
Ctrl + Enter
.
If this solution does not resolve your issue or seems outdated, please check the 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. If the problem persists, we highly recommend opening a new support ticket for further assistance.
Problem: The client encountered issues while updating recruiter information on translated destination pages using Elementor. Specifically, they were unable to save changes and received a warning about potential loss of edits when trying to replace a recruiter on the Finnish version of a page. Solution: We recommend ensuring that WPML and Elementor are used in accordance with our compatibility guidelines, which can be found here: https://wpml.org/documentation/plugins-compatibility/elementor/. The issue described was not directly related to WPML. When editing translated pages, it is crucial not to use Elementor directly but to utilize WPML's Translation Editor. This approach was successfully used on the German version of the page, where the recruiter was correctly updated. To resolve the issue on the Finnish page, the client should update the information using the Translation Editor to ensure the changes are properly saved and displayed.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 further assistance is needed, please do not hesitate to open a new support ticket at WPML support forum.
Problem: You are unable to re-add existing users as translators in WPML after an update, and you are concerned about losing translations when updating translated job pages. Solution: To resolve the issue of re-adding existing users as translators, you need to edit the
wp_capabilities
key in the
wp_usermeta
table. Remove the "translate" value for the affected users. This adjustment will allow you to add them back as translators. After making this change, please ensure to add the correct language pairs for each translator as needed. If you are unsure what to do, don't proceed with the above. Take a backup of the DB of your site before proceeding! If you're experiencing similar issues or if this solution does not apply due to different circumstances or 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 the problem persists, please do not hesitate to open a new support ticket at WPML support forum for further assistance.
