This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
Tagged: Exception
This topic contains 12 replies, has 3 voices.
Last updated by Waqas Bin Hasan 1 year, 8 months ago.
Assisted by: Waqas Bin Hasan.
Author | Posts |
---|---|
August 24, 2023 at 1:35 pm #14286043 | |
edmondU |
Dear WPML Support, I hope this email finds you well. I'm writing to address a concern regarding the translation of my website's footer and header using WPML. While my original content is in Albanian, I have been attempting to translate it to both Italian and English. I've made sure to correctly translate the strings in the 'String Translation' section. However, despite these efforts, the changes are not reflecting on the live page. For your convenience, I've attached several photos showcasing the problem. You can see the discrepancies between the translated strings in the WPML backend and how they appear (or don't appear) on the actual website. Could you kindly assist in determining the root of this problem and suggest potential solutions? It's vital for my site's visitors to have a seamless experience in their preferred language. Thank you in advance for your prompt attention to this matter. I appreciate your support. |
August 26, 2023 at 10:33 pm #14295343 | |
Andreas W. WPML Supporter since 12/2018 Languages: English (English ) Spanish (Español ) German (Deutsch ) Timezone: America/Lima (GMT-05:00) |
Hello, Our apologies for the delay in answering, as we are handling a high demand for support requests. One of my colleagues will assist you shortly on this matter. In the meantime it would be great if you could follow my advises or provide us more information about the issue: 1) Do I understand right, that you are using Widgets and translating them with String Translation? 2) Could it be that the strings are by default assigned to English and you still need to adjust the source language of those strings? 3) If not, could you instead please try to create one widget per language? 4) If this still will not solve the issue, please provide us with more details about how the footer was created. IMPORTANT: Best regards |
August 28, 2023 at 8:48 am #14298453 | |
edmondU |
Dear Andreas, First of all, thank you for your response. I appreciate the time you're taking to assist me. To address your questions and clarify my situation: Yes, I am currently using widgets and have been translating them using the String translation tool. Regarding the themes and languages: The theme's default language is set to English. However, when I set Albanian as the main language in WPML WooCommerce Multilingual and Multicurrency, the products defaulted to Albanian. As a result, I had to manually translate the product listings to both Italian and English. Now, here's where I encountered some challenges. As I dove into the String translation section, intending to translate the widgets and a few other strings to finalize the translation process, I noticed that some WooCommerce or Theme Strings, which were originally in English, required translation to both Albanian and Italian. Fortunately, in several instances, the translation process worked seamlessly for both languages. However, I'm currently facing a hiccup with the translation of certain widgets, particularly those in the Footer and Header sections. For some reason, these specific widgets aren't translating as expected. Given your expertise, do you have any specific recommendations or best practices on how to approach this? I'm keen to ensure a consistent translation across all parts of the website, and any advice or insight you can offer would be invaluable. Thank you in advance for your guidance. I look forward to your suggestions. Warm regards |
August 28, 2023 at 12:10 pm #14300641 | |
Waqas Bin Hasan WPML Supporter since 05/2014
Languages: English (English ) Timezone: Asia/Karachi (GMT+05:00) |
Hi, Thank you for contacting the support. I am assigned this ticket and 'll try my best to help you fix the problem. First of all, I ‘ll advise you to fix “WP Memory Limit” to at least 128MB while 256MB is recommended. See https://wpml.org/home/minimum-requirements/ for detailed information. You can set this in your wp-config.php file by adding following code: define( 'WP_MEMORY_LIMIT', '128M' ); define( 'WP_MAX_MEMORY_LIMIT', '256M' ); Remember to add these lines before the line where it says: You mentioned that "...these specific widgets aren't translating as expected...", are they not appearing in Translation Editor or String Translation? Or if they are appearing but not appearing correctly? Sometimes widgets need to be registered properly with WPML. This is a common case among page builders. Because they keep evolving with new features, widgets and updates. May I ask you to check the following guides and see if these help? - The7 Theme: https://wpml.org/documentation/theme-compatibility/creating-multilingual-sites-using-the7-theme-and-wpml/ - Elementor Page Builder: https://wpml.org/documentation/plugins-compatibility/elementor/ - Registering Page Builder Widgets: https://wpml.org/documentation/support/language-configuration-files/how-to-register-page-builder-widgets-for-translation/ Please also make sure that the templates used in a page (header, footer and etc) are also translated completely. Please let me know. Regards. |
August 29, 2023 at 9:19 am #14305667 | |
edmondU |
Hi, |
August 29, 2023 at 12:45 pm #14307269 | |
Waqas Bin Hasan WPML Supporter since 05/2014
Languages: English (English ) Timezone: Asia/Karachi (GMT+05:00) |
Thank you for the details. Please see attached and let me know if the red pen marked words are what you are referring to Mini Cart? I see these are not translated while checking English translation. While in the cart (hidden link) I see strings translated correctly. Can you find those strings in WPML -> String Translation and translate accordingly? If not, please check this guide https://wpml.org/documentation/getting-started-guide/string-translation/finding-strings-that-dont-appear-on-the-string-translation-page/ and see if you can scan your theme and relevant plugins to bring these strings into String Translation? Please let me know and I'll try my best to further assist you on the matter. |
August 30, 2023 at 9:57 am #14312223 | |
edmondU |
Hi, |
August 30, 2023 at 1:13 pm #14314035 | |
Waqas Bin Hasan WPML Supporter since 05/2014
Languages: English (English ) Timezone: Asia/Karachi (GMT+05:00) |
Thanks for the updates. May I ask for admin access to your website to check the issue in detail? You can create a separate admin user for this purpose, which can be deleted afterwards. Remember to take full backup of your website and database before proceeding. However, a staging/test site is highly recommended, because I may need to try some changes/fixes on the site (including plugins & themes deactivation), which may cause conflicts with the live site otherwise. Please confirm it in your next reply or let me know if you do not agree with the mentioned. I've set your next reply as private to share this information safely. IMPORTANT: If you don't see the section for providing access information, do not write in the message box or the information may appear as public. See https://wpml.org/purchase/support-policy/privacy-and-security-when-providing-debug-information-for-support/ for details on privacy and security. |
August 31, 2023 at 9:23 am #14318617 | |
edmondU |
Dear WPML Support Team, I hope this email finds you well. I've been encountering a persistent issue with my website's checkout process and require your expertise to resolve it. The primary problem arises when switching languages on the checkout page. Here's a breakdown of the issues I'm facing: In the default language: When switching languages on the checkout page, the cart's content doesn't display, and it prompts a message asking the user to go back. In Italian: The situation is even more troubling. Switching to Italian on the checkout page redirects users to a 404 error page, which is affecting my conversions and user experience significantly. These problems have become quite concerning as they directly impact my sales and the trustworthiness of my website. I've taken several troubleshooting steps including checking for theme and plugin conflicts, ensuring WPML and related plugins are updated, and verifying the translation integrity. However, I'm still facing these issues, and I believe there might be a deeper compatibility or configuration problem that I'm missing. Can you please assist me in diagnosing and resolving this? My website and its seamless functioning are crucial to my business, and it's imperative that I get this sorted as soon as possible. If you require any further information or access details to assist better, please let me know, and I'll provide them promptly. Thank you in advance for your time and support. I look forward to your prompt response. Warm regards New threads created by Waqas Bin Hasan and linked to this one are listed below: https://wpml.org/forums/topic/split-switching-languages-on-the-checkout-page/ |
August 31, 2023 at 11:17 am #14319853 | |
Waqas Bin Hasan WPML Supporter since 05/2014
Languages: English (English ) Timezone: Asia/Karachi (GMT+05:00) |
Thank you for the access, I'll check soon and 'll get back to you accordingly. Please note that in this ticket I'll be dealing with the original issue about Header and Footer translations. While for the other issue regarding "switching language on checkout" has been split to a new ticket at https://wpml.org/forums/topic/split-switching-languages-on-the-checkout-page/. This 'll be handled by our support accordingly. As per forum policy we can only handle one issue per ticket. So you can get more to the point help, without mixing up several issues in one long ticket. |
August 31, 2023 at 11:40 am #14320259 | |
Waqas Bin Hasan WPML Supporter since 05/2014
Languages: English (English ) Timezone: Asia/Karachi (GMT+05:00) |
I just checked quickly and can see that headers, footers and all other areas are translated and visible on frontend correctly. Besides this I also checked strings in Mini Cart, they are all available in ATE and ST as you've already translated the template (hidden link). But when I try to edit this template, I am getting an error (see attached). Perhaps it's been corrupted. I'll advise to try the followings: IMPORTANT: Take full backup of your website and database beforehand. - Update your The7 theme to the latest version. Please let me know if this helps. Or I'll have to try with minimal setup like deactivating all other plugins and checking with another theme. In this case, I can arrange a fresh sandbox site for you (if you haven't a staging site) to investigate on that. Please note that we are not allowed to make changes and investigate by this practice on a live site. |
August 31, 2023 at 2:26 pm #14321479 | |
edmondU |
Hi, Thank you in advance. |
September 1, 2023 at 7:50 am #14324919 | |
Waqas Bin Hasan WPML Supporter since 05/2014
Languages: English (English ) Timezone: Asia/Karachi (GMT+05:00) |
Thank you for your patience and cooperation. I've checked again and even 've registered that Mini Cart widget in WPML -> Settings -> Custom XML Config: <wpml-config> <elementor-widgets> <widget name="the7-woocommerce-cart-preview"> <fields> <field type="MiniCart: Title Text" editor_type="LINE">widget_title_text</field> <field type="MiniCart: SubTotal Text" editor_type="LINE">subtotal_text</field> <field type="MiniCart: ShopButton Text" editor_type="LINE">shop_button_text</field> <field type="MiniCart: ShopButton URL" editor_type="LINK">shop_button_link>url</field> <field type="MiniCart: ViewCart Button Text" editor_type="LINE">view_cart_button_text</field> <field type="MiniCart: CheckoutButton Text" editor_type="LINE">checkout_button_text</field> <field type="MiniCart: EmptyCart Text" editor_type="LINE">empty_cart_text</field> <field type="MiniCart: EmptyCartButton Shop Text" editor_type="LINE">empty_cart_button_shop_text</field> <field type="MiniCart: EmptyCartButton URL" editor_type="LINK">empty_cart_button_link>url</field> </fields> </widget> </elementor-widgets> </wpml-config> by following this guide https://wpml.org/documentation/support/language-configuration-files/how-to-register-page-builder-widgets-for-translation/. All of the text fields and URLs appear in ATE and are translated correctly. But unfortunately there seems to be the problem with the plugin "PRO Elements" for the frontend display. This plugin isn't on our compatibility list (https://wpml.org/plugin/?wpv_view_count=120064&wpv-plugin-functionality=0&wpv_post_search=PRO+Elements&wpv-wpcf-recommendation-flag=&wpv_filter_submit=Search) and is a derivative work from the Elementor Pro and lacks proper support. I'll advise to do the following: - Update your theme to the latest version. I tried but it failed. And then check again if it solves the problem. - If it doesn't then either use Elementor Pro or contact the plugin author to resolve the issue. In short, this isn't a problem with the WPML, but is with the unsupported/incompatible plugin. |