Problem: The client reported that translations were 100% complete but not showing on the respective language pages. The issue was observed with pages using the Divi theme and particularly with global modules, which are meant to be the same across multiple pages. The client had cleared all caches but the problem persisted.
Solution: 1. We identified that the 'Divi Module Builder' plugin was not compatible with WPML, which was causing the translation issues. 2. We recommended that the client contact the plugin's support team and inquire about compatibility with WPML. 3. We suggested that the plugin's authors join our Go Global program so our Compatibility developers could help test and make the plugin compatible with WPML. 4. Upon further investigation, we found that regular Divi modules could be translated without issues, but the problem was isolated to 'Divi Custom Modules'. 5. We advised the client to reach out to the plugin author to collaborate with our compatibility team. 6. The client discovered that the issue was related to the use of 'global' modules in Divi, which need to be translated from within the Divi library, not within the page itself.
If the solution provided here does not resolve your issue or 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 with us for further assistance.
Problem: The client was unable to save the Divi Theme Homepage on their multisite and encountered a 'save failed' error. The issue disappeared when the WPML plugin was deactivated. Deleting the translated page did not resolve the issue.
Solution: We imported the client's site locally for testing and did not encounter any issues with a 512MB memory limit. The error logs from the live site indicated a PHP fatal error due to the memory limit being exhausted. To solve this, we recommended that the client request their hosting provider to increase the PHP memory limit. Additionally, we advised the client to increase the WordPress memory limit by adding the following line to their wp-config.php file:
define( 'WP_MEMORY_LIMIT', '512M' );
The wp-config.php file can be accessed and edited via SFTP. The current WordPress memory limit can be confirmed under WPML -> Support in the Info section. For more information on editing the wp-config.php file and adjusting memory limits, we provided a documentation link:
