Problem:
If you're experiencing issues where automatic translation does not initiate or gets stuck when trying to translate new content, and there are no error logs displayed, this might be similar to the issue we addressed.
Solution:
First, we recommend checking the ATE error logs by navigating to WPML->Support->ATE Error Logs in your dashboard to identify any errors that might be preventing the translation process. If no errors are listed there, it's possible that an error 500 occurred.
Next, enable debugging in your WordPress environment to capture more detailed error information. You can do this by editing your
file:
1. Change
define('WP_DEBUG', false); to
define('WP_DEBUG', true);2. Add the following lines just before 'stop editing here':
ini_set('log_errors', TRUE);<br />ini_set('error_reporting', E_ALL);<br />ini_set('error_log', dirname(__FILE__) . '/error_log.txt');This setup will create an
file in your site's root directory, which can help us diagnose the issue further.
If these steps do not resolve the issue or if you prefer not to perform them yourself, we can provide a staging environment to investigate the problem without affecting your live site. Please let us know if you wish to proceed in this manner.
Keep in mind that this solution might be outdated or not applicable to your specific 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.
