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.
Problem: The client was unable to find two specific strings for translation in the Admin texts of their website's login and register elements.
Solution: We recommended the client to make a full backup of their site before proceeding. After gaining temporary access to the client's WP-admin, we scanned for strings in the "Houzez Login Register" plugin from WPML -> Theme and plugins localization. We successfully located the strings and they can now be found in WPML -> String Translation, under the domain "houzez-login-register".
Problem:
The client was trying to translate permalinks slugs for the custom taxonomies set from the Houzez theme but encountered issues where the expected translated slugs were not appearing, and instead, the original language slug was still being used. Additionally, the client faced 404 errors on the translated pages.
Solution:
Note: While using the theme Houzez, make sure that you translate the custom taxonomies that come with the theme only from the page: WPML -> Settings -> Taxonomies Translation section (all the taxonomies that come with the theme are set here). You shouldn't add the strings that end in "_rewrite_base" for translation in the WPML -> String Translation, as it will give error 404 on the translation pages.
For the strings that show on the property page (ex: "Garage size" or "Description"), you should check on WPML -> String Translation and translate those strings from there.
1. We recommended flushing the website's cache and then navigating to WP Admin -> Settings -> Permalinks to click the "Save" button, which flushes the permalinks.
2. We advised checking the documentation for using the Houzez theme with WPML, specifically for translating taxonomies:
3. We instructed the client to add strings for translation from WPML -> String Translations -> Translate texts in admin screens, and to change the string language to "BG" as they are set to English by default.
4. We clarified that the string "features" from the domain "houzez_settings]property_feature_rewrite_base" should not be translated in WPML -> String Translation, as it is should be translated in WPML -> Settings -> Taxonomies Translation section.
5. For the author page translation, we explained that the bio/description found on the author's page in the backend is translatable using WPML -> String Translation -> More options. Also, the theme Houzez has a custom post type "Agents" and offers the possibility to translate it as any other default post type.
If this solution does not seem relevant to your situation, please open a new support ticket with us.
Problem: The client wants to define Page B as the translation of Page A while having those two pages completely different, built differently with Elementor, and is unable to find the option to 'translate independently'. Solution: If you're experiencing the issue of wanting to have two pages with different layouts in different languages using WPML and Elementor, we recommend the following steps: 1. Create a duplicate of the page you want to translate. 2. Go to the duplicated page. 3. Click on the 'Translate independently' button. This will allow you to have different layouts for each language. For more detailed instructions, please refer to our documentation on Using Different Translation Editors for Different Pages.
If this solution doesn't look relevant to your issue, please open a new support ticket in our support forum.
It would be necessary to configure it with some code customization. At this point, I'm afraid it is beyond the scope of this support forum but we recommend that you check our contractors page: https://wpml.org/contractors/.
We use cookies to optimize our website and services. Your consent allows us to process data such as browsing behavior. Not consenting may affect some features.
Functional
Always active
Required for our website to operate and communicate correctly.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
We use these to analyze the statistics of our site. Collected information is completely anonymous.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
These cookies track your browsing to provide ads relevant to you.
