Problem: The client is experiencing issues with currency symbols not displaying correctly on their multilingual WooCommerce site. They have to manually add code to their functions.php file to switch currency symbols between English and Arabic, depending on the current language. Despite using WPML's String Translation for the currency, the Arabic currency symbol disappears or does not display correctly when the site language is switched.
Solution: 1. Understand that WPML does not control how WooCommerce displays or formats currency symbols. The issue arises from the custom code used to switch currency symbols based on the site's current language. 2. Remove any currency symbol translations from WPML String Translation to avoid conflicts, as these symbols are fixed and do not require translation. 3. Ensure that the custom filter code is correctly implemented to change the currency symbol based on the current language. This code is necessary because WooCommerce does not automatically adjust currency symbols based on WPML's language settings.
If this solution does not resolve your issue or seems outdated, we recommend 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 https://wpml.org/forums/.
Problem: The client is experiencing an issue where the currency symbol on their website displays in Arabic when the site is in English, despite needing it to match the language currently being displayed (English or Arabic). Solution: If you're facing a similar issue where the currency symbol does not match the website's language, we recommend checking the solution provided in a related support ticket. This involves configuring WPML to correctly translate custom currency symbols in WooCommerce. You can find detailed instructions on how to address this issue by visiting the following link: Translation of Custom Currency Symbols in WooCommerce Using WPML.
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 the issue persists, please open a new support ticket at WPML support forum for further assistance.
Problem: You are trying to change the main font family to 'TAJAWAL' for Arabic text only on your website, but the default theme font is being applied instead. Solution: To apply the 'TAJAWAL' font to Arabic text only, you can use custom CSS. Here is an example of how you can specify the font for Arabic content:
This CSS rule targets the body element only when the content language is Arabic (specified by :lang(ar)) and applies the 'TAJAWAL' font. Ensure you add this CSS to your theme or via a custom CSS plugin.
If this solution does not resolve your issue or seems outdated, we 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: You are trying to translate the 'home' keyword in the Google breadcrumb on your website to Arabic, but despite making changes in string translations and the admin area, it remains in English. Solution: We recommend following these steps: 1. Navigate to WPML >> Theme and Plugins localization page. 2. Scan the parent “RiseHand” theme. 3. Go to WPML >> String Translation page. 4. Search for the 'Home' string and add the translation. After these steps, the translation should appear correctly. You can update the translation if needed by visiting the String Translation page in your WPML admin area.
If this solution does not resolve your issue or seems outdated, 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: You are trying to translate the countdown timer labels in Elementor to Arabic, but they appear in English. Additionally, the top bar is not displaying in Arabic as expected. Solution: We recommend two methods to resolve this issue: 1. Method 1: WPML Translation Editor - Open the default language page in Edit mode. - Make a small change, such as adding a + sign in the page title. - Update the page by pressing the “Update” button. - Remove the small change made in the previous step. - Update the page again. - Now, open the translated page in WPML Translation Editor and search for the button URLs, add the translation, and press the Complete Translation button. 2. Method 2: Default WordPress Editor - Disable the WPML Translation Editor for that particular page and translate the page manually. You can follow the steps outlined in this documentation: Using different translation editors for different pages.
If these solutions do not resolve your issue or seem outdated, 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 the problem persists, please open a new support ticket.
Problem: The client is experiencing issues with mobile responsiveness not working correctly when using the Slider Revolution plugin alongside WPML. Solution: We recommend the following steps to isolate and potentially resolve the issue: 1. Export the Arabic language slider from your site. 2. Log in to a fresh WordPress site using the auto login URL provided. 3. Import the slider into the fresh WordPress site by navigating to Slider Revolution >> Overview >> Import Slider. 4. Create a new page and insert the slider to check if the issue persists. 5. If the issue continues, consider contacting Slider Revolution support for further assistance. 6. If the problem arises only after activating the WPML plugin, please inform us so we can investigate further.
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 the issue persists, please open a new support ticket at WPML support forum.
Problem: The client is unable to find the word 'TAG' for translation in the WPML string translation and is experiencing issues with maintaining language-specific versions of the footer using Elementor. The footer links are in English on the Arabic version of the site, and updating the footer in Arabic also affects the English version. Solution: We recommend scanning the WooCommerce plugin to ensure all translatable strings are available. This can be done by following the steps outlined in our documentation on Finding Strings that Don't Appear on the String Translation Page. After scanning, try searching for the strings again using the String Translation tool. Additionally, to address the issue with the footer, please verify where the footer information was inserted. If it was created using a page builder like Elementor or directly into the theme options, this might affect how translations are managed.
If these steps do not resolve your issues or if the solution 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. Should the problem persist, please do not hesitate to open a new support ticket with us for further assistance at WPML Support Forum.
Problem: The client was unable to translate certain texts into Arabic, including the word 'SHOP' and phrases in the top bar of their website. Additionally, Arabic characters in the Slider Revolution were displaying backwards and separated. Solution: For the Slider Revolution issue, we recommended accessing WP Admin -> Slider Revolution and editing the 'Demo-rtl 1' slider used for Arabic. The client should remove the text layers and add them again without applying animation effects that break the words into individual letters. For the text in the top bar, which is managed by the 'Thim Elementor Kit' plugin (not WPML-compatible), we attempted standard methods to find the text through string translation but were unsuccessful. We offered to download a clone/snapshot of the website to further investigate how the plugin manages this text. For the image accordion issue, we made the fields translatable by adding custom XML configuration to the WPML settings. The client should open the page in the default language, make a minor edit to refresh the elements detected by WPML, and then proceed with the translation.
If this solution does not resolve your issue or seems outdated, 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client is experiencing two issues on their Arabic language website: 1. The currency symbol displays Arabic symbols when the website is in English. 2. The footer menu items are not correctly aligned right-to-left (RTL) in Arabic; instead, they align left-to-right (LTR), and attempts to fix this with Elementor result in automatic reversion to English. Solution: We recommend using a child theme or an external plugin to implement changes that will persist through theme updates. This approach will help maintain the desired currency symbol and footer menu alignment across theme updates.
If this solution does not resolve your issues or seems outdated, please check the related known issues and ensure you have the latest versions of themes and plugins installed. If problems persist, we encourage you to open a new support ticket.
