[Resolved] Wrong order complete page when paying with Stripe (WooCommerce)
This thread is resolved. Here is a description of the problem and solution.
Problem: If you're completing a checkout in a secondary language and using Stripe as the payment method, you might be redirected to an incorrect 'thank you' page. The URL lacks the language parameter, leading you to the primary language's checkout page instead of the secondary language's 'order-received' endpoint. Solution: We recommend downgrading the String Translation Plugin to version 3.2.6 or WCML to version 5.2.1 as a temporary solution. You can download these versions from your WPML account. Additionally, we have a workaround that involves updating WooCommerce Multilingual to the latest version and following the steps provided in our Errata page:
When I finish the checkout in the secondary language (english) and I choose Stripe (the official woocommerce add-on) as payment method, I'm getting redirected on the wrong thank you page:
``` hidden link
```
But the url is missing the `/en/` language parameter, `cassa` is the checkout page page in the primary language, but `order-received` is the endpoint in the secondary language.
Apologies for the delayed response. We are currently dealing with a slightly higher volume of tickets than usual, which is the main reason for the delay. Rest assured, we are doing our best to reduce the response time while ensuring that each ticket receives an efficient and thorough reply.
I understand the issue you're having. Since the "Thank You" page is dependent on the "order-received" endpoint, please make sure that the endpoint has been translated correctly in the "WooCommerce > WooCommerce Multilingual > Stores URLs" tab.
The endpoints have been correctly translated already...
Please note, as stated in my first message, the issue is not with the endpoint, which is correct, but with the page slug (which is in primary language instead of secondary) and with the language parameter /en/ which is missing from the URL.
Hi There,
I hope you're doing well. Sorry for the delay in responding due to the weekend.
Thank you for the clarification. As the issue persists, a closer inspection will be required to understand the root cause of the issue.
I would like to request temporary access (wp-admin and FTP) to your site to take a better look at the issue. It would be better to have a testing site where the issue is replicated.
You will find the needed fields below the comment area when you log in to leave your next reply. The information you will enter is private which means only you and I can see and have access to it.
Maybe I'll need to replicate your site locally. For this, I’ll need to temporarily install a plugin called “Duplicator” or "All in One WP Migration" on your site. This will allow me to create a copy of your site and your content. Once the problem is resolved I will delete the local site. Let me know if this is ok with you.
IMPORTANT
-Please backup site files and database before providing us access.
-If you do not see the wp-admin/FTP fields this means your post & website login details will be made PUBLIC. DO NOT post your website details unless you see the required wp-admin/FTP fields. If you do not, please ask me to enable the private box. The private box looks like this: hidden link
We usually prefer access to a staging site, but given the additional VPN configuration needed to access your Staging site, it would be more convenient if you could provide access to your Production site instead. Please make sure to take a full backup of the site including the database. There's no need for FTP Access, as we can use a File Manager plugin if necessary.
Before I begin work on the Production site, I'd like to inquire if activating the 'Cash on Delivery' or 'Cheque Payment' methods is acceptable. Since the issue occurs on the Order Completed page, testing might require enabling an alternative payment gateway.
Additionally, could you please also provide test card details? This will allow me to complete the checkout process using that card information.
I have enabled the private fields for you to securely share the access information. Looking forward to your response.
Hello There,
Thank you for sharing the access information.
The account you've shared seems to lack the necessary permissions to access areas such as Plugins, Theme, and WooCommerce Status. I believe the issue might be caused by a plugin conflict, but since I don't have access to the plugin section, I'm unable to conduct further testing. Could you please assign full privileges to the account so that I can investigate the issue without any restrictions?
After a detailed examination, I was able to replicate the issue in my development environment. Upon clicking the checkout button, the system redirects to the default checkout page. However, if the order-received endpoint is translated, this redirection leads to a "Not Found"/404 page.
This problem seems to occur specifically when the WooCommerce checkout page is built using `Shortcode` or the "Classic Checkout" Block. I have escalated this issue to our development team for further analysis. Rest assured, I will keep you updated with any new developments.
For the time being, 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.
Let me know the update. I will be happy to help if you need further assistance in this matter.
Hi Prosenjit, we have not yet upgraded to the checkout block, will do after the Christmas shopping spree 🙂
I've found that if I do not translate the order completed endpoint, the user get redirected to the wrong language, but at least will not get a 404 error.
Our development team is currently investigating the issue. Meanwhile, we've discovered that downgrading either the String Translation Plugin to version 3.2.6 or WCML to version 5.2.1 can resolve the problem.
If you need the order-received page to appear in a different language, consider downgrading either the String Translation plugin or the WCML plugin to the specified versions. These previous versions can be downloaded from your WPML account(Screenshot: hidden link).
I will surely let you know as soon as I have more information on this issue.
I have another update for you. Our development team has explored the issue and identified a Workaround. Please implement the workaround detailed in the Errata provided below and see if you're getting the desired outcome. However, before proceeding, ensure that WooCommerce Multilingual is updated to the latest version.
Hi There,
I hope you're doing well. Sorry for the delay in responding due to the weekend.
Glad to hear that the workaround works!
We are trying our best to include the fix in the next update of the WooCommerce Multilingual plugin. Till then, please continue using this workaround.
Feel free to let me know if you need further assistance in this matter. I will be happy to help.
Best regards,
Prosenjit
Manage Cookie Consent
We use cookies to optimize our website and services. Your consent allows us to process data such as browsing behavior. Not consenting may affect some features.
Functional
Always active
Required for our website to operate and communicate correctly.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
We use these to analyze the statistics of our site. Collected information is completely anonymous.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
These cookies track your browsing to provide ads relevant to you.
