This will save errors to a debug.log file in the /wp-content/directory. For more details, visit: https://wpml.org/documentation/support/debugging-wpml/. 5. Deactivate the WPML CMS Nav plugin temporarily as it should not affect translations. 6. Update your WPML plugin and add-ons to the latest version, 4.7.0, following the instructions here: http://wpml.org/faq/install-wpml/.
If these steps do not resolve your issue or the solution seems outdated, 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 at WPML support forum.
Problem: The client is considering recreating their existing website and wants to understand the implications for their current translations.
Solution: If you're planning to recreate your site, you might not need to redo all translations provided that:
The URL of the site remains the same.
The site is registered under the same WPML account, even if using a different site key.
The content that was previously translated remains unchanged.
If you used the Advanced Translation Editor (ATE) or automatic translation before, your translations are saved in Translation Memory. This means if the same sentence is sent again for translation, it will be reused.
However, be aware of potential issues:
Changes in design that alter the content could require new translations.
Changes in style or design elements that affect the visual presentation but not the content might also need updates.
We recommend testing these changes on a staging site before applying them to your live site.
If this solution does not apply to your case, or if it seems outdated, please check the related known issues, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If issues persist, we highly recommend opening a new support ticket at WPML support forum.
