Mihai Grigori

Thanks for reporting this @amelie9! We’re aware of this problem and will be releasing a fix shortly (within the hour after this reply).

EDIT: a new version was released to address this issue: 4.2.3

• This reply was modified 7 years, 2 months ago by Mihai Grigori.

Speaking of fairness, if you feel differently about WooCommerce Multilingual, I think you should at least be able to update the rating here. ??

Your experience with WPML is equally important, however. Let me know what is your username on the WPML support forum and I’ll try to see if there’s anything I can help with about your tickets.

Cheers!

@simooo you left a review for WooCommerce Multilingual here.

WooCommerce Multilingual is a FREE plugin that requires WPML to function and is developed by the same company as WPML.

To be clear – do yu have specific difficulties with WooCommerce Multilingual?

Your suggestion makes sense @thesun1. It’s been added to our queue and will be included in a future update soon. Thanks for reporting this!

@vyskoczilova What do you mean by a hybrid link?

@wpadgyda Have you identified exact steps how you can replicate this or does it happen randomly?

If you have the steps, can you add them here so we can see the problem in action and then address it?

Thanks!

Hi @kabak133 – have you tried getting help with this in our support?

Something similar (maybe this exact thing) was indeed fixed for the upcoming version. This warning could also go away when you simply check the button to check for updates.

If that doesn’t solve it, or the warning doesn’t dissappear by itself, I recommend that you open a support ticket with details about how this happens, and we’ll assist.

Cheers!

I’m sorry to hear you’re having a not so great experience @kysil.

It’s needless to say that we’re doing our best and, as you realized by invoking anyone else to create a ‘worthy’ product, it’s not an easy task. ??

We’re still committed to help so if you have a specific problem with the new version or with older versions of WooCommerce Multilingual, please create a ticket or mention me in an existing ticket you may have in our support at wpml.org and we’ll expedite it. The least we can do right now.

Skipping from 4.1.0 to 4.1.2 happened because we realized we needed to fix one more thing right after creating 4.1.1. We left 4.1.1 as a valid version but we just didn’t push it as an upgrade notification to everyone.

Cheers & I hope we can straighten things at least a little bit for you! ??

What WPML version are you using @rodrigocoragem96?

@awethemes, this function was added to WooCommerce 2.6.

You could upgrade to WooCommerce 2.6 to avoid this error before we add an update in WooCommerce Multilingual. (we’re adding one)

What WooCommerce version are you using?

You’re welcome!

One of the possible causes for this, @thibotus01, is a that migration logic from WooCommerce 4.0 to 4.1 has not run.

You can try to fix this by triggering it this way: in the options table, change the value of the option ‘_wcml_version’ to ‘4.0.0’.

Do you know how to do this?

Found it. Fixing this right now.

No, you will not lose your settings if you delete the plugin files.
The settings are kept in the database.