Problem: You purchased a WPML subscription and used all your translation credits on multiple languages, but now need to focus on French and Russian. After deactivating the unnecessary languages, you attempted to delete their translations from the database, but the deletion process is stuck and does not complete. Solution: If the deletion process is stuck, we recommend restarting the process. Here are the steps you should follow: 1. Temporarily deactivate the unnecessary language. 2. Navigate to Posts or Pages, switch to the deactivated language, and bulk delete the translations. 3. Clear the trash if necessary.
Please note 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 issue persists, please open a new support ticket at WPML support forum.
Problem: You are trying to translate new listings and update translations of old listings, but the Advanced Translation Editor (ATE) is not loading. Instead, you see a spinning wheel with a message: 'Unable to retrieve job details.' Solution: We have confirmed that all systems related to the ATE are now functioning correctly. However, there might be a short delay as the system processes a backlog of accumulated jobs. We recommend trying to access the ATE again now. If you continue to experience issues, please check the related known issues and verify that you have installed the latest versions of WPML and its extensions. If the problem persists, we highly recommend opening a new support ticket for further assistance. You can do so here: WPML support forum.
Problem: After updating the WPML translation plugin, you are unable to translate messages. Clicking the translation icon leads to a screen that continuously reloads without allowing translations. Solution: We recommend you test the translation again. There has been an update that should resolve this. If this solution does not resolve your issue or seems outdated, please check the related known issues and confirm that you have installed the latest versions of themes and plugins. If problems persist, we highly recommend opening a new support ticket at WPML support forum for further assistance.
Problem: The client manually installed a new WPML update because it wasn't showing in the WordPress updates section or in plugins, which resulted in a critical error on the website. Solution: We logged into the site and attempted to update the WPML plugins via the Plugins -> Add New -> Commercial page. However, the site was still pointing to localhost, which we identified from the WPML -> Support page notice indicating the site was detected at localhost. This could interfere with updating plugins from a publicly mapped address.
To resolve this, we deactivated all plugins, switched to the standard WP theme 2025, updated the WPML plugins (WPML, String Translation, and WCML), and then reactivated these along with WooCommerce. After these steps, the fatal error was no longer present.
We recommend the client to try reproducing the issue with the current setup and report the steps if the error reoccurs. Additionally, we advised using PHP 8.2 until newer versions are fully supported, as PHP 8.4 is still in beta support by WordPress. For more details on PHP compatibility, visit WordPress PHP Compatibility.
If this solution does not resolve your issue or seems outdated, please check 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 at WPML support forum.
