Problem: The client reported that after updating language settings to shorten the name and adjust the mapping for Portuguese, automatic translations for Portuguese were not completing, although it worked for other languages. Solution: 1. **Update Your WPML Components** * Go to **Plugins → Add New Plugin** in your WordPress dashboard. * Click on the **Commercial** tab. * Click the **Check for updates** button. * Update the **OTGS Installer** plugin to its latest version. 2. **Cancel Any Stuck Automatic Translation Jobs** * Go to **WPML → Support**. * Find and click the **Troubleshooting** page link. * Scroll down and click the **Cancel in-progress automatic jobs** button. 3. **Verify Portuguese Language Mapping** * Navigate to **WPML → Translation Dashboard** and click the **Tools** tab. * Click on **Language Mappings**. * Ensure Portuguese is correctly mapped to a supported language for automatic translation. 4. **Test Automatic Translation with a Small Batch** * Go back to **WPML → Translation Dashboard**. * Select a small batch of content and initiate a test translation to Portuguese.
If these steps do not resolve your issue, or if the solution seems outdated or irrelevant 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 problems persist, please open a new support ticket at WPML support forum for further assistance.
Problem: The client activated multilingual and automatic translation features on their website but encountered a Litespeed server error when accessing translated pages. The error seemed to be related to the virtual '/en/' directory not existing on the server. Solution: We recommended verifying that the object cache was enabled on the Litespeed server and suggested using a mu-snippet plugin to disable cache groups. The client was instructed to create a new .php file in the wp-content/mu-plugins directory and insert the following code:
Additionally, we clarified that there should not be a separate '/en' directory on the server as WPML handles it virtually, which could be causing 404 errors.
If this solution does not resolve the issue or seems irrelevant due to being 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 further assistance is needed, please open a new support ticket at WPML support forum.
