Problem: The client was unable to edit a /US page with Elementor without the changes being overwritten by WPML. They were also concerned about the correct settings for automatic translations and whether duplicating pages for the Australian and USA versions, rather than translating them, was causing issues with changes being reverted.
Solution: 1. We advised that manual edits on translated content inside Elementor should be avoided if the WPML Translation Editor is used, as it will overwrite those changes. 2. To display alternative media in second languages, the client should use the WPML Media Translation addon. This allows uploading alternative media files for other languages and creates an entry in the media library for those files. 3. When translating Elementor content, the client should not use WPML String Translation but rather the WPML Translation Editor or the WordPress Editor. It is important not to use both methods simultaneously to prevent overwriting. 4. If content is duplicated with WPML, it is crucial to mark the duplicate as "Translate independently" to avoid overwriting when the original content is edited. 5. For automatic translations, the client should choose the most suitable option based on their workflow and review preferences.
If the provided solution does not apply or is outdated, or if you are still experiencing issues, we highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If necessary, please open a new support ticket for further assistance.
Problem: The client was experiencing an issue where activating the WPML plugin resulted in only the header being displayed and the rest of the page being blank. When the WPML plugin was active, the language switcher was not visible. Solution: The client resolved the issue by reinstalling the WPML plugin, which restored the site to its full functionality.
If you're experiencing a similar issue, we recommend trying to reinstall the WPML plugin. However, please note that this solution might be irrelevant due to it being outdated or not applicable to your case. If the problem persists, we highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. Should you need further assistance, please do not hesitate to open a new support ticket in the WPML support forum.
Problem: The client reported an issue with the String Translation table in their site, specifically a missing
icl_string_page
table in the database. This was not immediately affecting the site's operation but could lead to critical issues in the future. Additionally, there were no strings listed for translation in the WPML String Translation interface, and a database error was reported.
Solution: We recommended the client to: 1. Enable WordPress Debug Mode to check for any errors or warnings from WPML. 2. Visit WPML>>String Translation to verify if strings are listed for translation. After further investigation, we identified that the string translation tables were missing indexing. We resolved the issue by running a SQL patch on the client's site. We asked the client to check their site and provide feedback.
If this solution does not seem relevant to your issue, please do not hesitate to open a new support ticket by visiting our WPML support forum.
