Problem: If you're experiencing issues where translations are restarting without any updates to the original content, and you notice symbols like the eye or stuck symbol on your articles, this might be due to settings in your WPML configuration. Solution: We recommend checking if you have the 'Translate Everything Automatically' feature enabled in WPML. This feature might be causing translations to restart whenever there are minor edits or updates in your content management system, even if these changes are not directly related to the content itself. To resolve this, you can either adjust the settings to disable automatic retranslation or manage how WPML handles changes in your content.
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. If issues persist, please do not hesitate to open a new support ticket with us for further assistance at WPML support forum.
Problem: The client is experiencing an issue where translations are not completing on one of their websites using WPML, despite all plugins being up-to-date. Solution: We recommend increasing the WP Memory limit to 256M, as the minimum required by WPML is 128M, and the client's current WP Memory Limit is set to 40M. To do this, add the following code to the
1
wp-config.php
file:
1
define('WP_MEMORY_LIMIT', '256M');
This line should be placed just before the comment:
1
/* That's all, stop editing! Happy blogging. */
After making this change, the client should verify the current settings at WPML > Support > WordPress and attempt the translation again. If the hosting provider limits these settings, we advise contacting them to request an increase. For optimal performance, even higher values than 256M are beneficial. WPML minimum requirements
If the problem persists after increasing the WP Memory limit, we suggest opening a new support ticket. We also highly recommend checking related known issues, verifying the version of the permanent fix, and confirming that the latest versions of themes and plugins are installed. If the provided solution is outdated or not applicable to your case, please do not hesitate to contact us for further assistance.
