Problem: After updating WPML to the latest version, the client is unable to translate content and encounters a 500 error when attempting to use the string translation or open the WPML support tab. The issue began after URL slug manipulations were made, which might have caused disruptions in the translation engine. Solution: We recommend enabling the debug log to identify the specific cause of the 500 error. You can follow the instructions here: https://wpml.org/documentation/support/debugging-wpml/. After enabling the debug log, please share the log files with us for further analysis. If the problem persists, consider reverting to a previous stable version of WPML and its components, as this resolved the issue temporarily for the client.
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 continues, please open a new support ticket at WPML support forum for personalized assistance.
Problem:
I am trying to upgrade to version 4.7.3 of WPML on our multisite as advised. After the upgrade, the site crashed. We attempted to downgrade to version 4.7.2, but the site still does not work.
Solution:
We could fix the issue by deactivating and deleting WPML 4.72 as well as string translations. Then we uploaded version 4.7.3 newly from the WPML site. Only after we then activated WPML 4.7.3 we then downloaded string translations from the commercial tab in the multisite network and activated it on the sub site.
Problem: The client is transitioning their site from WP Bakery to Astra/Spectra and needs to re-translate pages without changing the existing slugs. They are concerned about how to manage slug translations and media during this process. Solution: 1. To prevent slug changes during re-translation, set the WPML → Settings → Translated documents options → Page URL to "Auto-generate from title". This prevents slugs from being translated and keeps them as is.
2. When re-translating pages, if you do not want to override existing translations, WPML will not update the translations unless the original content is modified. If you choose to override, WPML will ask whether to update the translation based on new content.
3. For managing slugs, if "Translate" is selected, WPML will create a new translated slug. If "Copy from original" is selected, it will use the slug from the original language. There is currently no option to keep existing translated slugs if overriding translations; manual adjustment is necessary after overriding.
4. For images, you can use different images for each language without translating the image content. Upload language-specific images using the media translation tool.
If this solution does not fully address your issue or seems outdated, we recommend opening a new support ticket. Also, check related known issues at WPML Known Issues and ensure you have the latest versions of themes and plugins installed. For further assistance, please visit our support forum.
