Problem: The client has translated their homepage, but the changes are not reflecting on the site. Additionally, some products have lost their featured images, and attempts to perform a bulk update for 3,000 products result in a 503 error. Solution: For the homepage translation not reflecting: 1. Clear all caches on the site, including server-level, CDN, and WordPress caching plugins. 2. Cancel any stuck translation jobs for the homepage via WPML → Translation Dashboard → Jobs. 3. Make a minor edit to the homepage in the default language and save it. 4. Resend the homepage for translation through WPML → Translation Dashboard.
For the issue with product featured images and the 503 error: 1. Pause any automatic translation processes in WPML to free up server resources. 2. Increase server resources like PHP memory limit or execution time to handle bulk updates.
If these steps do not resolve the issues or if the solution becomes outdated, we 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.
Problem: If you're experiencing a blank screen when trying to edit translations in the Advanced Translation Editor on your WordPress site, this could be due to insufficient memory allocated to WordPress. Solution: We recommend you try the following steps: 1. Increase the WordPress memory limit to at least 256MB. You can do this by adding the following code to your
Add this code above the line that says /* That's all, stop editing! Happy blogging. */. You can verify the updated memory limit in WPML -> Support. 2. Check if there is a relevant workaround on our errata page for known issues. For instance, issues related to WordPress 6.7 not loading .mo files can be found here: WordPress 6.7 .mo files issue. 3. Make a minor edit to the content in the original language, save the changes, and then update the translation.
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 the problem persists, please open a new support ticket.
