You are trying to update translations for your WordPress site using WPML but encounter errors. Specifically, for the homepage, you receive the error 'we tried three times but failed. Please contact support'. For other pages, you encounter a fatal WordPress error or an error message.
Solution:
We have created separate tickets to track the issues you are facing with WPML more efficiently. Please follow the workarounds suggested in these tickets:
Additionally, create a new post (a simple one for testing) and check if you can translate it as expected. For already translated pages that are showing errors, try the workaround suggested here: Translation status stuck or displaying an error.
If these solutions do not resolve your issue or seem 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.
The debug log is showing multiple notices indicating that the creation of dynamic property wpml_cms_nav_cache::$cache_to_option is deprecated.
Solution:
If you're experiencing this issue, we recommend deactivating the WPML CMS Nav plugin as it is not essential for the operation of WPML or String Translation.
Alternatively, you can set the debug mode to false to temporarily resolve the issue. To do this, add or modify the following code in your wp-config.php file:
define('WP_DEBUG', false);
Please ensure to back up your site before making these changes.
If this solution does not apply to your case, or if it becomes 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 further assistance is needed, please open a new support ticket at WPML support forum.
If you're experiencing a fatal error while translating a page or post, specifically a PHP Fatal error indicating 'Uncaught TypeError: strtr(): Argument #1 ($string) must be of type string, array given', this might be due to incorrect translation settings for Themify custom fields.
Solution:
We recommend following these steps to resolve the issue:
1) Navigate to WPML>>Settings>>Custom Fields Translation 2) Click on the System fields link 3) Search for fields by *_themify* 4) Set the *_themify_builder_settings_json* to Don't translate 5) Save the changes
Please ensure to perform a full site backup before making these changes.
If this solution does not resolve your 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.
