사용 가능한 솔루션

Problem:
The client is experiencing issues with WPML on their website where some words are not translated into Arabic, and some details are missing in the Arabic version of the property details section.
Solution:
1. We recommended following the steps in the WPML documentation to find and translate untranslated strings. For more details, visit https://wpml.org/documentation/getting-started-guide/string-translation/finding-strings-that-dont-appear-on-the-string-translation-page/
2. Ensure all steps are followed as described in the WP Residence theme's specific WPML guide at https://help.wpresidence.net/article/wpml-help/
3. We checked the site and found that the strings appear translated when accessing the site in incognito mode, indicating a cache issue. We advised the client to consult with the theme authors to resolve the cache issue caused by the theme.

If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, 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 problems persist, please open a new support ticket.

Problem:
You are using Elementor with WPML on your site and have encountered an issue where updating a custom field in one language affects the other language in an Elementor Loop Carousel. Specifically, when you update the custom field setting in the English version, it also changes the setting for the Polish version, due to shared widget configuration across languages.
Solution:
To resolve this issue, we recommend using a manual translation approach to prevent synchronization of the custom fields across different languages. You can find detailed instructions on how to implement this by visiting the following documentation: Using Different Translation Editors for Different Pages.

If this solution does not apply to your case, or if it seems outdated, please check the related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. We highly recommend opening a new support ticket if you continue to experience issues.

Problem:
You are working on a site and want to exclude certain paragraphs or headings on specific pages from automatic translation using WPML. You have encountered issues where you cannot clear a translation field and save it empty in the ATE, and editing through the WP editor causes the translation to disappear.
Solution:
Excluding specific paragraphs or headings from automatic translation within the same page using WPML's automatic translation system is not directly possible. To achieve different content on specific translated pages, you can switch from using ATE to the WP editor for those specific pages. This allows you to fully customize the translated versions, including removing content altogether. For detailed steps on how to switch editors and customize translations, please visit Using Different Translation Editors for Different Pages.

Please note that this solution might be outdated or not applicable to your specific case. 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 this does not resolve your issue, please open a new support ticket at WPML support forum.

Problem:
The client reported issues with untranslated content on their multilingual website. Specifically, the 'Skin Handle' dropdown was still in Chinese on the Chinese Traditional page, English interface URL snippets appeared in Chinese on WhatsApp, and certain elements on the Checkout page (product names and payment options) were not translated.
Solution:
We recommended the client to use the WPML String Translation to search for and translate the strings that were not appearing in the correct language. For detailed guidance, we suggested visiting the WPML String Translation documentation.

If this solution does not resolve the issue or seems outdated, we advise 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. For further assistance, please visit our support forum at WPML Support Forum.

Problem:
The client is experiencing issues with a custom language switcher in the header menu of their site. The switcher is required to open on click as per the client's requirements, but it does not close smoothly and lags.

Solution:
We suggested modifying the CSS to improve the functionality of the language switcher. Here are the steps and code provided:

.wpml-ls-legacy-dropdown-click .wpml-ls-sub-menu {<br />    transition: none !important;<br />}<br /><br />.wpml-ls-legacy-dropdown-click.wpml-ls-item-toggle .wpml-ls-sub-menu {<br />    transition: none !important;<br />}

If these changes do not resolve the issue, we recommend removing any previous conflicting CSS and ensuring no custom scripts are interfering. Additionally, we suggested that the client might consider consulting with a professional from WPML contractors for further customization, as this falls outside our standard support scope.

If this solution does not apply to your case, or if it seems outdated, please check the related known issues, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. Should issues persist, we highly recommend opening a new support ticket here.