George Botsev

Thank you for reporting the problem with the notice.
I will escalate this for our developers to fix.

Hello, you can get and test with our latest beta version from wpml.org in Accounts > Downloads – and then scroll to the bottom of the list.
In that beta version this issue should be resolved.

Please do mind that that version is suitable only for testing purposes and using it on a production server is not recommended.
Also if you decide to use it, make complete website and database backup first.

The issue should be resolved in the just-released beta of WooCommerce Multilingual – it is available @ wpml.org > Account > Downloads

As far as I can see, we have two issues here. Thankfully they are both reported to the appropriate persons – for the other scripts to WPML developers and now for the cart_widget.js to WooCommerce Multilingual developers.

I managed to reproduce the issue.
This is escalated to our developers now. Thank you for reporting it.

Hello @webdados
Thank you for reporting this.
I need to ask – were this fixed for you in 3.6 version? and perhaps this is a regression? Or this was not fixed at all – even in version 3.6?
I will do some tests in my local environment and I will notify our developers about this issue.

Hello Tom,
This issue needs more in-dept look and I would like to suggest you to open a new ticket at the forum in WPML.org so that we can debug this further in-depth.

Hello again.
Thank you for opening a new ticket.
I think that we might have here a known bug, so it would be best if you can test our latest beta version available at wpml.org.

Please make sure you make complete website and database backup before that and be sure to do the test on a staging or testing server first.

Thank you for reporting this, and providing the fix for that plugin.
Our compatibility team is on the case.

Thank you. I will get now your ticket and continue to debug there.

@alex_webber the original poster did not provided us any details.
If you are willing to investigate further this case, perhaps you will?
Could you please open a new support ticket in wpml.org so that we can investigate this further?

Thank you @webdados, I will include this for our compatibility team.

@kaia Konsap does the issue persist if the language is not hidden?
Can you provide more information please?
At first glance this seems to be a known problem and it might be related to our issues mentioned above. I would suggest you to open a new ticket in WPML.org forum so that we can analyze and determine the issue.

In my opinion this “Price:” is a custom string that is in your theme template.
You might need to re-scan your theme for strings from WPML > Theme and plugin localization. You need to mark “Translate by WPML” if it is not yet marked and then scan your theme for strings.
If this does not help – then we will need a closer look at your theme, so I would recommend you that you open a ticket in WPML.org forum where the supporter specialists would find the issue and try to help you with that.

I think that you misunderstood me. I did not suggest to not report bugs. I am just letting you know that we did not investigated this plugin and any details are welcome.
We are always willing to help with the compatibility with other plugins and to make some improvements. Any information that you can submit is welcome.