Home›Support›English Support›[Resolved] There is an issue with the endpoint slugs of order-received in Woocommerce
[Resolved] There is an issue with the endpoint slugs of order-received in Woocommerce
This thread is resolved. Here is a description of the problem and solution.
Problem: The client is experiencing an issue where the WooCommerce 'order-received' page only displays correctly in the default language. In other languages, it shows a single sentence instead of the translated thank you page. Solution: We have resolved this issue, and it will be included in the upcoming WCML v5.5.3.1 release. We recommend updating all WPML plugins once the update is available to ensure that the 'order-received' endpoint functions correctly in all languages. Before proceeding with the update, please ensure to take a full site backup.
If this solution does not apply to your case, or if it seems outdated, we highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. Should you need further assistance, please do not hesitate to open a new support ticket.
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.
Background of the issue:
I am trying to have a nice page when orders are received in WooCommerce. The only language that is working is the default language. As soon as I default the slugs of all languages, it works fine.
Symptoms:
Instead of a translated thank you page, I get a page with just one plain WooCommerce sentence: 'Thank you for your order.' In German, Dutch, and French, I only see one sentence like 'Vielen Dank. Ihre Bestellung ist eingegangen.'
Questions:
How can I ensure the endpoint slugs for 'order-received' are translated correctly in all languages?
Why does the thank you page only display correctly in the default language?
I was able to reproduce the issue on a fresh WP setup and confirmed that the translated endpoint works correctly in the previous WCML version, so I’m going to escalate this to our 2nd-tier team for deeper analysis.
