Home›Support›English Support›[Resolved] Woocommerce not working as expected with wpml, for the secondary language
[Resolved] Woocommerce not working as expected with wpml, for the secondary language
This thread is resolved. Here is a description of the problem and solution.
Problem: The client is experiencing issues with WooCommerce functionalities on their Greek version of the site. Specifically, the minimum product quantity that can be added exceeds the actual stock, and the Availability Section is not displayed after selecting a product variation.
Solution: We discovered that disabling the WPML String Translation plugin resolved the issue. The problem was likely due to incorrect translation of strings that are not meant to be translated because they are related to settings, not text. For example, strings like
woocommerce_allowed_countries
and
woocommerce_notify_no_stock_amount
should not be translated. We recommend the client to delete all such strings from the String Translation table. If the issue persists after cleaning up the table, we suggest setting up a test site with WPML to further investigate the problem. It may also be helpful to contact the plugin provider, such as Chrocoblock, for assistance with testing their plugin on the test site.
Please note that this solution might be outdated or not applicable to your case. If the issue persists, 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 necessary, do not hesitate to open a new support ticket for further assistance.
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.
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
I can not confirm an issue with the Availability Feature on my test site.
I see on your site the following message on the dashboard:
"Your Elementor Pro license has expired."
This also includes that your "JetWooBuilder" product template might not be working as expected, as you are not able to use PRO widgets without having Elementor PRO registered on your site.
Please register Elementor PRO and then test again.
I understand, but the issue has nothing to do with the Elementor Pro version.
I see that the test site does not have any issues, and it works perfectly; maybe you should check the files to see if there is some misconfiguration; maybe it is the FTP files
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
I will continue checking, but please take note, that in the current state of your site, you will not be able to edit the widgets on your product template or use Elementor PRO features and this can cause unexpected issues, too.
Thanks for informing me! i know that, and the dev will update the Licence as soon as possible. I hope you can fix it as soon as possible, as it has been 1 week since we opened the ticket..
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
As I already took a copy of the site where the issue persisted in a minimal setup and I yet was unable to recreate the issue on a sandbox, it is kind of complex to find out what is causing the issue, but I should have an update for you tomorrow.
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
I can still not confirm what is causing the issue, but on my test site, on which it works, I am using Elementor PRO 3.19.1 while your site uses 3.19.0.
Please update Elementor PRO, then test again and let me know the results.
Thank you for your continuous efforts to resolve the issue at hand. As previously mentioned, I believe that the problem is not related to the version of Elementor PRO being used, nor to the licensing. Given this issue's ongoing nature, it seems that the root cause lies elsewhere.
Your expertise and understanding of WPML's intricacies are invaluable in this situation, and I trust that together we can identify and address the underlying problem. I look forward to any additional insights or suggestions you might have that do not solely focus on the Elementor PRO version upgrade.