Problem: The client reported a bug where content was being randomly erased when translating from one language to another using Elementor. The issue persisted even after creating new blank homepages and manually recreating them. The client's hosting provider and Elementor support suggested the issue might be related to WPML.
Solution: We recommended the following steps to troubleshoot the issue: 1. Keep the English page open after restoring it. 2. Edit the default language page using Elementor. 3. Change the image on the page. 4. Update the page. 5. Check if the English page remains unaffected.
Additionally, we advised the client to cancel any in-progress translation jobs in WPML-> Translation Management-> Jobs tab, as using multiple editors for translation is not recommended. We also provided a guide for manual translation with WPML and Elementor: Using different translation editors for different pages.
If the solution provided does not resolve the issue or seems irrelevant due to being outdated or not applicable to your case, we encourage you to open a new support ticket. 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. For further assistance, please contact us in the WPML support forum.
Problem: The client discovered that all strings translated from English to Bulgarian were deleted and replaced by their translations, causing elements on English pages to appear in Bulgarian. The issue was also present on the staging site, ruling out a cache problem. Additionally, there was a concern about taxonomy translation where a sub-category was missing its parent category.
Solution: 1. We resolved the synchronization issue indicated by the warning at the top of the backend. 2. We navigated to WPML -> String Translation, searched for, and deleted the entries for 'grad'. 3. We went to WPML -> Settings -> Taxonomy translation, selected 'City', and added 'city' as a translation for the 'grad' slug, then saved the changes. 4. In the 'Real State' section under 'City', we fixed a sub-category that was missing its parent category in English. 5. We advised the client to follow these steps on the production site. 6. We also highlighted the importance of saving theme options in the correct backend language, as saving them in a secondary language might have caused the default language for strings to change.
Please note that this solution might not be relevant to your case, as it could be outdated or not applicable. If you're experiencing similar 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 the problem persists, please open a new support ticket with us.
Problem: The client was experiencing random 404 errors on their multilingual website for specific URLs, such as 'label' and 'agency' pages. The issue persisted even after saving permalinks and enabling/disabling plugins. It was noted that the problem disappeared when the WPML String Translation plugin was disabled.
Solution: We identified that the issue was related to the incorrect translation of slugs for custom post types and taxonomies. We advised the client to: 1. Translate custom post types and taxonomies in the WPML -> Settings -> Post Types Translation and WPML -> Taxonomies Translation sections, respectively. 2. Avoid translating admin strings that end in "_rewrite_base" in the WPML -> String Translation. 3. We deleted the incorrect admin strings for "agency" and "label" from the WPML -> String Translation, which resolved the 404 errors.
For the separate issue regarding the author bio description not translating, we created a new ticket to address it specifically.
Please note that the solution provided might be irrelevant if it's outdated or not applicable to your case. If you're 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 the problem persists, please open a new support ticket with us.
