Shouldn't cart_widget.js be loaded on the translated domain?

Thank you Webdados for pointing this to us.

I am waiting a reply from the developer team and I will reply to you shortly.

Cool!

This problem will be fixed in our next version (3.6) which it will be out soon.

Thank you one more time for pointing this to our attention.

Are we there yet? ??

The 3.6 is out so I set this to resolved

Not fixed.

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.

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

The main reason this is a problem for me is that I’m using Autoptimize to concatenate/minify scripts. If this script is loaded from another domain rather than the current language one, Autoptimize will see it as an external script and won’t concatenate him with the others.

They have made some changes on their development version to detect the several WPML domains and concatenate anyway, which solves the issue for me.

Anyway I think this should be fixed on your side. All the script should be loaded from the current language domain.
I honestly can’t say if this was OK on 3.6. Today, on the last version. The problem persists.

I have a test WPML install (which I even provided the details to you on another thread on WPML.org https://wpml.org/forums/topic/wpml-conflict-with-newest-version-of-woocommerce-subscriptions/page/2/ ) with last versions of all: WPML (4 plugins) + WooCommerce + WooCommerce ML + 2015 theme and nothing else and the problem is there.

As a matter of fact it’s interesting that also xmlrpc.php ping back + emoji javascript + jquery.js + jquery-migrate.min.js and wlwmanifest.xml are also loaded from them main domain when seeing a secondary language domain, so this might not be isolated to WooCommerce ML but be a wider problem on WPML.

George Botsev: roger that.

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.

So to update you about these issues.
They should be all resolved respectfully in the new WooCommerce Multilingual and the upcoming WPML versions.

Sorry for the lack of reply from my end, but I’ve been stuck on another project.

I can confirm the cart_widget.js issue is solved.

I still have these loading from the main domain:

• jquery.js
• xmlrpc.php
• wp-emoji-release.min.js
• jquery-migrate.js
• wlwmanifest.xml

But these are not WCML related. I’ve updated this post on wpml.org -> https://wpml.org/forums/topic/site_url-breaking-autoptimize/

Yes, the second part – resource files will be addressed in WPML 3.3

However for wlwmanifest.xml and xmlrpc.php the things are different because they are handled in a different manner and it may not be possible to handle them safely at this time, so it might go to a future version.