George Botsev
Forum Replies Created
-
I am marking this ticket as resolved due to inactivity here.
I am marking this issue as resolved.
If the problem persists for you, please consider opening a new ticket in wpml.org support forum where we can attempt to diagnose the issue more in-depth.Hello and Happy New Year!!!
You have mentioned the version that you are using of WooCommerce, however you forgot to mention the other versions that are in play – like for WooCommerce Multilingual.
I would suggest you to make backup of your website first, and then first update to the latest WPML and WooCommerce Multilingual 3.7.7 (currently) and then try again and see if the error persists.
You might have to update the original product (not the translation, just the original).
Also if you can test in a minimal setup – it would be good – by minimal I mean only WPML and WooCommerce + WooCommerce Multilingual, and a default theme – sometimes the issues lies in compatibility with other plugins or themes.Let me know how it goes and if I can help you any further.
If you wish – it is always better to open a new ticket in wpml.org support forum, where we can help you on your site.You are welcome!
Have a happy holidays!!!Or you can just remove the line.
I think that I see the error.
I have just reported it to our developers.
You need to go to wp-content/plugins/woocommerce-multilingual/inc/compatibility.php and change the line:
require_once WCML_PLUGIN_PATH . '/compatibility/wc_ajax_layered_nav_widget.class.php';
to
require_once WCML_PLUGIN_PATH . '/compatibility/class-wcml-ajax-layered-nav-widget.php';Thank you for testing, I will provide this information to our developers.
Can you please provide more information about the error 500?
There might have been many reasons for that error. What the server log has to report about that? Could you please check?
Also please take a look at our FAQ about this matter here: https://wpml.org/faq/500-error/We still have not been able to reproduce the problem, however one customer reprted that translating the endpoing in WPML > String Translation resolves the issue.
Please search for the order-pay string in WPML > String Translation and assign it some translation.Let me know if this helps for you.
Hello,
our plugin depends on WPML for its multilanguage capabilities and features and on WooCommerce for its e-commerce capabilities and features.
WooCommerce has a kind of country detection, WPML has a browser-language detection and redirection. To have what you need, if I understand you correctly, then there might be a need for additional custom coding work.
You can translate or create products in the language that you want to have them. You can have different menu items and different translation for all pages and home page included, however you can use different templates for different language, but this requires some coding.@ap.koponen thank you for escalating this ticket. I think it might be related to other issue here on the forums that is already escalated.
Would you mind please to respond to the supporter in that ticket and also provide him a duplicator clone, so that we can investigate the issue further?Okay, we are unable to reproduce the problem, so it would be very beneficial if you can create a ticket in wpml.org forum with the same question, so that we can investigate further and get a duplicator package with one of your site that is affected.
I have escalated this to our developers to take a look.
I will get back to you when they respond and provide more information.Could you please provide here the link to your ticket?
We can continue debugging this further on the wpml.org forum.I wonder if this issue may be related to the bug in WordPress Core: https://core.trac.wordpress.org/ticket/35012
Because in WPML we have a work-around for this: https://wpml.org/errata/redirect-loop-using-slug-different-posts/