Problem: The client reported an issue where the translation status incorrectly showed as pending, even though there were no pending translations. Solution: Initially, we suggested following the instructions in our guide to resolve issues where the translation process is stuck. This guide can be found here: https://wpml.org/faq/translation-status-stuck-or-displaying-the-error-wpml-didnt-manage-to-translate-this-page/ When the problem persisted, we identified that 25 translation jobs were stuck in the database with a status of '2' . We resolved this by executing the following SQL command to manually change their status to '9':
update
`icl_translation_status`
set status = 9
where status = 2
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 at https://wpml.org/forums/forum/english-support/.
Problem: The client's website crashed due to multiple WPML requests, specifically with POST requests to admin-ajax.php. The issue persists even after disabling other plugins, indicating that WPML is the cause.
Solution: We recommend enabling the debug mode to track any errors that might be causing the issue. To do this, add the following lines to the wp-config.php file:
define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);
@ini_set('display_errors', 0);
define('SCRIPT_DEBUG', true);
This will create a debug.log file in the wp-content folder, which can help identify the problem. For more detailed instructions, please refer to our documentation on debugging WPML.
If these steps do not resolve the issue or if the debug log does not provide clear insights, we encourage you to share the log using a service like Pastebin and provide us with access to your wp-admin area for further investigation. Please ensure you back up your site before providing any access.
If this solution doesn't look relevant, please open a new support ticket in our WPML support forum.
Problem: The client reported receiving numerous warnings in their logs and experiencing API timeouts related to WPML's translation jobs.
Solution: 1. We requested temporary access to the client's wp-admin and FTP to investigate the issue and asked for steps to reproduce the problem. We emphasized the importance of backing up the site and database before proceeding, recommending the Duplicator plugin for this purpose. 2. Our development team created a modified version of WPML 4.6.7 to better log the XLIFF errors the client encountered. We asked the client to back up their site and confirm if we could install this package. We provided a link to view the contents of the package.
