Pierre Sylvestre

Hello @hoangbien,

Could you please open a support ticket on the WPML forum? You will get all the needed assistance to fix your problem.

Thank you,
Pierre

Hi @mostafas1990,

Can you reproduce the problem on a brand new product? (I tried on my dev site and I have no problem)

It could also be an issue with a 3rd party addon, so I suggest you open a support ticket with our WPML support, providing your debug information and the steps to reproduce the issue (it might depend on your workflow).

Thanks,
Pierre

Hi @dyin,

Unfortunately, I have no actual hint to share. It could be related to your theme, because of some configuration, or a compatibility issue with another plugin.

I invite you to open a ticket with the WPML support to get a full assistance.

Thanks,
Pierre

Could it be a result of calling the language slug ‘ca’ ?

Yes @psychosis51, the language code “ca” is for Catalan, and this is a preset language, you won’t be able to edit it.

If you are on a new site, I suggest to create a new custom language on this page (click on “Add language”) and use the language code “en-ca” for the Canadian English.

If this is an old site, you will have to manually update the database. You can get help to do this with our WPML support.

Thanks,
Pierre

Hi @psychosis51,

Could you please share a screenshot of what you see on https://staging.streamz-global.com/wp-admin/admin.php?page=sitepress-multilingual-cms%2Fmenu%2Flanguages.php&trop=1 ?

Thanks,
Pierre

Thanks for the details @wondercrow!

I carefully read the forum ticket and our internal support ticket. I think the suggestion to Clear the cart contents when language or currency change is the right setting in that case.

If you look at the explanation of this feature, it was specifically developed to avoid this kind of issues:

Sometimes, the products in your site might come with multiple complex options like table-rate shipping, or can be of a specific product type like subscriptions or bookings. This allows for a very complex combination of products and their options, all of which are crucial for the final checkout process. Sometimes, synchronizing all these options when customers switch language or currency does not work correctly.

As I said, we are working to have the wider compatibility, but we can have an infinite combination of plugins and addons. That’s why in some cases we offer specific settings to workaround possible issues.

Thanks for using WCML and sharing your feedback ??

• This reply was modified 4 years, 7 months ago by Pierre Sylvestre.

Hi @wondercrow,

Thanks for reporting the issue to Woocommerce Force Sells.

We understand that issues coming from updates are frustrating and we are working in deep to avoid this as much as possible.

For your information, we are running more than 3000 unit/integration tests and more than 200 end-to-end tests just on WooCommerce Multilingual (and we have even more tests on WPML side). And our automated test base is growing everyday.

Our challenge with WooCommerce Multilingual is to have the wider compatibility (we have approximately 200 WC extensions declared as compatible).

We are currently evaluating new ways to involve 3rd party plugin authors and help reporting issues (mostly during our beta release cycles).

It would be also interesting to know which plugins you updated (seems you updated both WPML and WCML at the same time) and from which versions.

Thanks,
Pierre

Hi @sue_c,

“WooCommerce Gateways Country Limiter” was initially a separate plugin, but it was integrated into WooCommerce Multilingual 4.10.0. So you can just deactivate and remove “WooCommerce Gateways Country Limiter” from your WordPress install.

Hi @yipengcmp,

Did you already checked the WPML documentation about media translation?

If you are stuck with this issue, I suggest that you open a ticket on the WPML support forum and provide your debug information so that we can quickly evaluate possible issues on your setup.

Thanks,
Pierre

Hi @tomiye,

This problem on my website occurred after I upgraded WordPress 5.2 to 5.4.2

So this problem might not be related to WooCommerce Multilingual…

I recommend you to try isolating the problem with a minimal installation (if possible on a test server) by temporarily deactivating 3rd part plugins and see if your can reproduce the problem when WCML is activated and not reproduce when WCML is deactivated.

Note that this WC addon is not part of our compatible list but you can invite the author to our Go Global program and we’ll provide assistance to fix possible incompatibilities.

If you are running in more troubles, I also recommend that you open a ticket on our dedicated support forum where you will get faster assistance.

Thanks,
Pierre

Hi @tomiye,

When you say you changed the priority in add_action(‘xxxxx’,100,3), is it in a 3rd party plugin or inside WooCommerce Multilingual? Could you write the whole line without the “xxxxx”?

Could you please open a support ticket on WPML forum and provide your debug information? That way it will be easier for us to give you assistance.

Then, please share the link here so I can follow up.

Thanks,
Pierre

Hi @apprique,

We regret if you had troubles with WooCommerce Multilingual.

When the site key is missing or the account is expired, WPML displays a message but it should not block the plugin. There’s a “dismiss” link if you are on a test site.

Concerning the price synchronization, it’s hard to tell what’s the actual problem. Sometimes it could be an incompatibility with a 3rd party addon.

Did you already shared this on our support forum? If not, I strongly advise you to do it so we can provide a dedicated support. Then, please paste the link here so I can follow up.

Thank you!

Hi @vmarko,

I am Pierre from WPML team.

We have an errata on wpml.org and it’s quite old now.

I am trying to follow up and finalize a solution.

As for the WPML, some things need to be changed on both sides. So we are still in progress regarding this.

On our side, we have no pending development task. According to the errata, it just requires an improvement on the method \Extension_Wpml_Plugin::w3tc_url_to_docroot_filename.

Please let me know if there’s something we can do to move this forward.

Thanks,
Pierre

• This reply was modified 4 years, 10 months ago by Pierre Sylvestre.

I opened a pull request here https://github.com/Automattic/hyperdb/pull/13 to fix this issue. Basically, I copied the code from the legacy wpdb class.

This should also fix potential issues for CREATE, ALTER, TRUNCATE and DROP queries.

Hello,

We have been facing the same issue and we came to the same conclusion. The returned value for $wpdb->query( "TRUNCATE wp_icl_languages" ) returns int(0), but the table is actually truncated.

The fix suggested by @mcanever_fastbooking is working for me too, but I added it at line 741 instead.

I just did a test with a “DROP TABLE” query and the result is int(0) even if successful.

IMHO, the problem is more generic and also occurs for other kind of queries. AFAICS, the var $return_val is mainly updated as an integer matching the affected rows. It should also return a boolean sometimes.

Thanks,
Pierre