This thread is resolved. Here is a description of the problem and solution.
Problem:
Custom order received endpoint redirects to default language if using classic checkout block/shortcode
Solution:
This issue is fixed with the latest version of WooCommerce Multilingual & Multicurrency - 5.3.2. Please update to the latest version.
Relevant Documentation:
https://wpml.org/download/woocommerce-multilingual-multicurrency/?section=changelog
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.
Our next available supporter will start replying to tickets in about 5.30 hours from now. Thank you for your understanding.
Tagged: Compatibility, WCML
Related documentation:
This topic contains 43 replies, has 2 voices.
Last updated by Itamar 11 months ago.
Assisted by: Itamar.
Author | Posts |
---|---|
November 22, 2023 at 3:43 pm #14900467 | |
T4ng |
This is something we see from our development environments, with up-to-date plugins, with only WPML + WooCommerce + WooCommerce multlingual + Storefront + systemPay (our french payment platform, offered only to french buyers). I am trying to: Instead, I got: |
November 22, 2023 at 4:29 pm #14900967 | |
T4ng |
As a comparison, this setup has the same plugins up to date, but WCML which stays on 5.2.1, instead of 5.3 : it works fine. hidden link |
November 23, 2023 at 10:17 am #14906151 | |
Itamar Supporter
Languages: English (English ) Hebrew (עברית ) Timezone: Asia/Jerusalem (GMT+02:00) |
Hi, and thanks for the videos. According to the debug information of your site, WPML CMS (our core plugin) and WooCommerce are not updated to their latest versions. Please update WPML and WooCommerce to their latest versions and check if the problem persists. WPML 4.6.7 This is the first essential debugging step. If the problem persists, we will need to replicate it on a test site, which I'll prepare for this case. Thanks, |
November 23, 2023 at 10:40 am #14906587 | |
T4ng |
Hi Itamar, It already took us more than a day to narrow towards this issue. I sent you debug information from one of our environment, at some point of testing, so that you have a rough idea of what the setup is. But it doesn't reflect all the tests we did. WooCommerce 8.3.1 was released 2 days ago and fixes nothing related to this. Since our last global update, the fact that we update ONLY WCML from 5.2. to 5.3 makes the issue occurs. In any of our tests, the problem occurs everytime WCML 5.3 is installed, never when WCML 5.2, or 5.2.1 (yes we took time to test this one as well) is installed instead, whatever the theme, other plugin activated, or WordPress version. So yes, even if you don't see it from the debug log I provided, we already tested that this issue occurs on: WCML 5.3 >> redirect to orginal language checkout page before rederecting to payment platform with wrong currency == Doesn't work Can you please test it? Thank you. Best regards, |
November 23, 2023 at 5:35 pm #14910759 | |
Itamar Supporter
Languages: English (English ) Hebrew (עברית ) Timezone: Asia/Jerusalem (GMT+02:00) |
Hi, Thanks for trying my suggestions and adding a detailed description. It helps! It seems we are facing an issue specific to the Systempay for WooCommerce plugin. This plugin is unknown to us and not on our list of officially compatible plugins: https://wpml.org/plugin/ We need to replicate this issue on a fresh WordPress installation. Then, I'll be able to escalate it to our compatibility team. For this, I created a test website with a clean WordPress install. You can access it through this link: hidden link With this link, you'll be directly logged in. Could you please install the Systempay for WooCommerce plugin and see if the issue is replicable on a clean WordPress installation? Please configure WPML and WooCommerce as set on your site (just the basic configurations needed to replicate the issue are enough). Please also ensure you install the latest version of the plugin. Please let us know when everything is finished and you can replicate the problem. Regards, |
November 24, 2023 at 2:55 pm #14918703 | |
T4ng |
Hi, I configured the environment as close as ours as I could. Unfortunately, I couldn't reproduce the issue. Thanks |
November 26, 2023 at 12:18 pm #14924563 | |
Itamar Supporter
Languages: English (English ) Hebrew (עברית ) Timezone: Asia/Jerusalem (GMT+02:00) |
Hi, and thanks for testing this on the sandbox site. I suspect that there is a collision with the theme or another plugin that might cause this problem. If possible, get your site into a minimum environment. Minimum environment means switching to a default WordPress theme like TwentyTwenty-One and no plugins activated except WPML. First, you will need to check if the problem persists when the theme is switched to TwentyTwenty-One (for example). If it persists, then deactivate all plugins except the WPML and its add-ons, WooCommerce itself (without its extensions), and the SystemPay plugin. Then please check if the problem persists. If it does not persist, start by activating the plugins one by one and check when the problem comes back, then report to me which was the culprit plugin.
|
November 26, 2023 at 4:57 pm #14925427 | |
T4ng |
Hi, I ran my tests with the Storefront theme, instead of our custom theme, with only these plugins active: So tell me if I'm wrong, but I think there shouldn't be any custom logic involved in that setup. When I order from the French version of the website, I'm redirected to /checkout/ with both SystemPay and Stripe, with WCML 5.3. |
November 26, 2023 at 5:53 pm #14925693 | |
Itamar Supporter
Languages: English (English ) Hebrew (עברית ) Timezone: Asia/Jerusalem (GMT+02:00) |
Hi, I didn't know the WooCommerce Stripe Gateway plugin was also needed for this issue. But in general, I'd say that it sounds like you did the test correctly. On the other hand, we can see (as you tested) that it does work with the same setup on the test site. So, it is weird that it still happens on your site. Please let me have access to your site. I will need to consult our second-tier supporters on this issue. Alternatively, please contact the developers of Systempay for the WooCommerce plugin with this issue. If you need further help with this, please share the access details to your site with me. Privacy and Security Policy |
November 26, 2023 at 8:12 pm #14925777 | |
Itamar Supporter
Languages: English (English ) Hebrew (עברית ) Timezone: Asia/Jerusalem (GMT+02:00) |
Hi, You wrote: "What I can do, though, is providing you with the database. Can you please explain to which code you refer to? Something is wrong with the Dropbox link you sent me. I get nothing with this link. In any case, it is better that you will migrate your site to our Cloudways server. In the next private message, I'll share with you all the details on migrating your site to our server. |
November 26, 2023 at 8:26 pm #14925859 | |
T4ng |
Please replace the ftp:// part with https:// to get the proper DropBox link. |
November 26, 2023 at 9:22 pm #14925883 | |
T4ng |
I just applied this database to a fresh clean WordPress install, on which I only added the plugins mentioned earlier, and StoreFront theme. Same issue. |
November 27, 2023 at 11:38 am #14929489 | |
Itamar Supporter
Languages: English (English ) Hebrew (עברית ) Timezone: Asia/Jerusalem (GMT+02:00) |
Hi, I want to remind you that Systempay for WooCommerce is not officially compatible with WPML and WooCommerce Multilingual & Multicurrency. According to our records, only a few of our clients use this plugin. I checked with my colleagues and searched our forum, and could find a similar report. That ,said we want to try and help further. You were not able to replicate the issue on our sandbox site. And you cannot give us access to your site (it is a local site, as you say). To check if we can help further, we need a copy of your site migrated to our Cloudways server. I think you might have missed my previous private message with the details on migrating your site to our Cloudways server. So I'm adding it again in the following private message. Regards, |
November 27, 2023 at 11:53 am #14929537 | |
T4ng |
Hi Itamar. So there's obviously something wrong with our database. |
November 27, 2023 at 12:21 pm #14929725 | |
T4ng |
I didn't want to send the website because it has huge content. Anyway, I cleaned it to make it smaller for you. Then I tested, again, the site works, and the issue is definitely still there. Now, I filled all the required information. Unfortunately, the transfer didn't work: I can't drop content from a working environment to allow you to make a copy. |