Problem: The client wants to display different chat icons for different languages on their website: a WhatsApp chat icon for English and a Telegram chat icon for Russian.
For the implementation of a different plugin for the Telegram chat in the Russian language, we advised that this would require custom coding. Since custom work is beyond the scope of our support policy, we recommended that the client hire a developer or a WPML contractor, which can be found here: https://wpml.org/contractors.
If the provided solution is not applicable due to being outdated or not relevant to your case, we suggest opening a new support ticket. We also 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.
Problem: The client is using the Divi theme and Divi theme builder to design specific pages such as My Account & Cart page in both Arabic and English. They are facing an issue where changes made to the theme in one language are also affecting the other language. Additionally, after translating the user account page and refreshing, the translation does not appear to be saved. Solution: Firstly, if the Body Template has already been translated, we recommend manually editing the translated version by accessing it through the
et_body_layout
post type in WordPress. Here are the steps: 1. Log in to your WordPress Admin panel. 2. Add `/wp-admin/edit.php?post_type=et_body_layout` to your domain in the URL bar to access all Body layouts. 3. Switch to the language of the translated layout. 4. Find and edit the translated Body template as needed.
If the issue persists, follow these additional steps: 1. Empty the Divi Cache. 2. Go to WPML > Support > Troubleshooting. 3. Select "Body Layouts" from the dropdown in the Cleanup section, then choose "Synchronize posts taxonomies". 4. Click on additional options: Clear WPML Caches, Language information, and Adjust post-type assignment for translations. 5. Translate the layout via the
et_body_layout
post type.
After these steps, the Arabic translation should be properly saved and displayed. If this solution does not resolve the issue, please open a new support ticket with us.
Problem: The client is unable to translate the Search input label in the YITH WooCommerce Ajax Search plugin even after translating the string in WPML > String Translation. Solution: We recommend going to WPML -> String Translation and looking for the domain
admin_texts_yith_wcas_search_input_label
. Once found, translate the placeholder text within this domain.
Problem:
The attribute of the products do not match in languges, and when we are on the page of a Attribute, for example, blue color in Arabic language, the language switcher is displayed, but if you first enter blue color in English language, the language switcher for Arabic translation is not displayed.
Solution:
You must follow our instructions when working with WPML and WP All Import.
If you are importing translated posts with taxonomies (categories, tags, or custom taxonomies), you must create the exact same taxonomies in your WordPress site before importing the post files.
