Skip Navigation

This thread is resolved. Here is a description of the problem and solution.

Problem:
The client's customers are redirected to the order-received endpoint in the primary language after completing an order, despite the rest of the order process working correctly in the respective languages. This issue persists with payment providers Mollie and Pay.nl and occurs on a multi-domain setup.

Solution:

* Update WCML to the latest version, as the issue should be resolved in WCML v5.3.2.

If the issue persists even with the WCML v5.3.2, please follow the steps below to further troubleshoot the issue:

1. Ensure all endpoints are correctly translated in WooCommerce -> WooCommerce Multilingual -> Store URLs and complete all tasks listed in WooCommerce -> WooCommerce Multilingual -> Status.
2. Test for plugin conflicts by:

- Switching to a default WordPress theme

- Deactivating all non-essential plugins, leaving only WPML, WCML, and necessary plugins to reproduce the issue active

- Ensuring a full backup is made before testing

3. Check the WooCommerce default checkout page setup and look for JavaScript errors in the browser console or related logs in WooCommerce -> Status -> Logs.
4. As a temporary workaround, replace the "Classic Checkout" block or Shortcode with the default Checkout block on the checkout page. A guide can be found in this video: https://tinyurl.com/ynkg55k8.

If this solution does not seem relevant to your situation, please open a new support ticket at WPML support forum.

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

Tagged: 

This topic contains 15 replies, has 3 voices.

Last updated by Marsel Nikolli 1 year, 4 months ago.

Assisted by: Marsel Nikolli.

Author Posts
November 30, 2023 at 10:40 am #14960959

henkd-6

When a customer finishes his order, he is always sent to the order-received endpoint in the primary language. We have tried many things, but can’t seem to change this behavior ourselves. We have even (partly) switched from payment provider, to check if that changes anything.

Both Molly and Pay.nl point to the Dutch order-received endpoint after an order is finished. How can we solve this?

Everything else in the order process works fine and in the correct language, including all transactional e-mails.

It concerns: hidden link, hidden link and hidden link

December 1, 2023 at 10:05 am #14971037

Marsel Nikolli

Hi,



Thank you for contacting WPML Support, I will be happy to help you today.


Can you please make sure all the endpoints are correctly translated in WooCommerce -> WooCommerce Multilingual -> Store URLs and also make sure all the "to-do's" are done in WooCommerce -> WooCommerce Multilingual -> Status.

Try it out and let me know how it goes.

Looking forward to your reply,
Marsel

December 1, 2023 at 11:49 am #14972133

henkd-6

Hi, we translated all store URL's and made sure that all 'to-do's' were done. Unfortunately it doesn't fix the problem. If I test with a fake order plugin, it does go to the correct language.
If we have a payment with Mollie or Pay.nl, it always goes to the Dutch language. We also get the order confirmation e-mail in the correct language.

December 1, 2023 at 2:30 pm #14973689

Marsel Nikolli

Thank you for the update.

In order to further troubleshoot, would it be possible to check if the issue happens in a minimal setup, that meaning:

- set a default WP theme
- keep active only WPML and WCML Plugins and the necessary plugins to reproduce issue
- disable all other plugins

After, check if the issue is still happening.
This will help checking if there might be any compatibility issue with any other plugin.

Note: Please make sure you have a full backup (files & database) before trying anything on your website.

Looking forward to your reply,
Marsel

December 3, 2023 at 2:04 pm #14980143

henkd-6

Hello Marsel,

I tried as you told me, but we still have the same issue if we disable everything except WPML related plugins and Pay.nl.

I also tried the same setup on a staging site. The only difference is that we use language folders there instead of different domains. On that setup everything works fine.

Do you have more suggestions to make the payments work correctly on our multi domain setup?

December 4, 2023 at 9:03 am #14983395

Marsel Nikolli

Hi,

Thank you for the update.

1) Can you please tell me how how the WooCommerce default checkout page is created (is it the default one or a custom page that you have created and is being used as a checkout page)?

2) Do you notice any JavaScript error on the console log in the case when the page is redirected?

3) Please check if anything shows up on the WC logs:
go to WP admin -> WooCommerce -> Status -> Logs tab and check if there is any log related to the issue.

Looking forward to your reply,
Marsel

December 4, 2023 at 9:47 am #14983927

henkd-6

Hi Marsel,

1) I think it is the default one, but I am not 100% sure. How can I see that? The checkout page works fine in every language. It is just the order-received page that is always going to the default one.
2) We don't get any JS errors in the console with Mollie. We do get one with Pay.nl There it says: Unrecognized Content-Security-Policy directive ‘require-trusted-types-for’.
3) There was no error log related to the issue.

We do see the same issue on loveish.fr. We don't see the same issue on Dutchdoll.de. Most of the settings on these sites are identical.

December 4, 2023 at 12:33 pm #14986759

henkd-6

Hello again,

I reverted WCML to version 5.2.1 on a testsite and then the issue seems to disappear. As soon as I update to version 5.3.0 or 5.3.1, we have the same issue. So the problem seems to be introduced in version 5.3.0. Do you have any suggestions on how to fix the problem on this latest version of WCML? And is it safe to (temporarily) downgrade to this old version on a production site?

December 4, 2023 at 12:46 pm #14986857

Marsel Nikolli

Thanks for the info.

Is is possible to check if there is any difference in terms of plugins used on the websites you are having the issue with the one that is working fine (plugin versions (WPML and WCML), WP version, server configuration)?

In order to further troubleshoot the issue I would require a copy of your website to test it locally and further escalate the issue if needed.

You can use the Duplicator plugin(https://wordpress.org/plugins/duplicator/) in order to create a copy of your website, and upload the backup on a file sharing website (Google Drive, Dropbox, etc.), please send me the link to download the backup after.

I’ve set your next reply as private in order for you to provide the backup link.

Thank you,
Marsel

December 4, 2023 at 12:55 pm #14986875

bjornE-6

Hi, I'm jumping in with the same issue. Also after updating WCML. We also use Mollie and the order-received points to the main (NL in our case) language.

December 4, 2023 at 1:32 pm #14987257

henkd-6

Hi, unfortunately I am not able to duplicate the whole site due to server restrictions. Would it help if I just give access to the back-end of our site?

There is no difference in plugins. The only difference was that the other site was not yet updated to the latest version of WCML. After updating to WCML 5.3.1 it had the same issue. When we downgraded it to 5.2.1, the issue disappeared. I noticed that meanwhile another WPML + Mollie user reacted here as well, so I assume it is a general issue with version 5.3.0 and above.

The problem also disappears when we change the url structure to folders, instead of separate domains.

We have this issue with both Mollie and Pay.nl. When we use a fake payment plugin it is fine.

December 4, 2023 at 2:01 pm #14987601

henkd-6

Hi, we downgraded to 5.2.1 as short term solution because our conversion measurement for Google ads was getting wrong information as well. Please check how it can be solved for new versions. I think everyone with Pay.nl or Mollie, in combination with multidomain setup, has the same problem.

December 4, 2023 at 2:17 pm #14987867

Marsel Nikolli

Hi,

Thank you for the update and clarification of the situation.

The issue has already been escalated to the 2nd tier support team.
As soon as we have an update I'll let you know.

For the time being, a colleague suggested this workaround and see if it works:

"This problem seems to occur specifically when the WooCommerce checkout page is built using Shortcode or the "Classic Checkout" Block.

I recommend adding the default Checkout block on the checkout page instead of the "Classic Checkout" block or Shortcode. For guidance on how to do this, please refer to this video: hidden link."

*Note: If you want to try the workaround please make sure you have a full backup of your website before making any changes.

Thank you for understanding and please let me know if the workaround works in your case.
Marsel

December 4, 2023 at 3:38 pm #14988831

henkd-6

Hello, this workaround seems to work for the correct language. However, the themes on our different websites (Shoptimizer and Woodmart) do not support this, so it will break our layout completely. Also the Pay.nl plugin does not support this 'default checkout' block and gives errors. We will wait for a solution from your 2nd tier support.

December 4, 2023 at 4:03 pm #14989199

Marsel Nikolli

Thank you for your update.
I'll let you know as soon as I have an update from the team.

Regards,
Marsel