[Warten auf das Feedback der Benutzer] 404 error with custom order received page
Dies ist das technische Support-Forum für WPML – das mehrsprachige WordPress-Plugin.
Mitlesen können alle, doch nur WPML-Kunden können hier Fragen veröffentlichen. Das WPML-Team antwortet im Forum an 6 Tagen pro Woche, 22 Stunden am Tag.
Hintergrund des Themas:
I am trying to use a redirect to a custom WooCommerce order received page. However, when WPML is activated, users encounter an issue. The problem can be observed at the following URL: versteckter Link
Die Symptome:
Users receive a 404 error when redirected to a custom WooCommerce order received page while WPML is activated. The redirect works correctly when WPML is disabled.
Fragen:
Why does the redirect to the custom order received page result in a 404 error when WPML is activated?
How can I resolve the 404 error while keeping WPML activated?
thanks for granting me access! The 404 occurs on the English version of the order confirmation page: /en/order-received/thank-you-for-your-order/?key=wc_order_3IoyfFiKsLxpL&order_id=235950
while in German it resolves to: /bestellung-erhalten/vielen-dank/?key=wc_order_kDtjkL0Ha7fn9&order_id=235951
The parent and child pages are translated correctly, but the parent page was marked as a Duplicate. When I opened the translation editor, I noticed that the permalink was still in German on both parent and child pages. I’ve updated them to English.
Now the order is being active, but the checkout page still returns previous step. I can see that you configured the page in the WooCommerce settings. However, the 404 occurred because only the endpoints were translated in WPML → String Translation, while the actual page was not defined for English under:
versteckter Link
Please assign the English page here and test again.
Hi Marcel, I tried to implement the solution established on my staging site with your help on my production site. However, there is something wrong with the thank you page - can you tell me what you meant exactly with "but the parent page was marked as a Duplicate. When I opened the translation editor, I noticed that the permalink was still in German on both parent and child pages. I’ve updated them to English." Can you tell me exactly what you did? What do I have to do to unmark the page as Duplicate? I notice that WPML is creating two/duplicate endpoint string translations for the thank you page and thus my custom thank you page doesn't work on my live site. Thanks for help. Frank
Hi Marcel - I did as suggested by you (setting the English version of the thank you page to "translate indeopendantly") but I still get a 404 error in the checkout (I had tried to implement the custom thank you page on my live site but it didn't work - so now I copied my live site again to my staging environment). Can you please take a look at my set up? The credentials are still valid. If you change anything, please tell me exactly what you did to make it working. Otherwise I won't be able to reproduce it on my live site. Thank you! Frank
I’m still investigating the issue. Unfortunately, I wasn’t able to resolve it on Friday, as the current behavior doesn’t allow me to test it properly.
At the moment, once I confirm the order, it gets added to the system, but the user remains stuck on the Checkout page (e.g., versteckter Link.">example link
). So instead of a 404, the page doesn’t proceed anymore and stays on Checkout. What now is different is that /en/order-received doesn't have the "thank you" child page included.
Did you change something more on the URL structure? Because the page "Vielen Dank für Ihre Bestellung" has as permalink versteckter Link, which is not the child page as before.
Hi - before, my thank you page URL was "thank-you". So now I've changed it back to "thank-you" and also set the order received end point to "thank-you". Yet, I'm still getting the 404 error instead of the thank you page - but if I delete "checkout" from the URL, it shows the thank you page. Does it help you for finding the error? Thx, Frank
thanks for the information, that’s helpful. I get the 404 again when placing an order in English, so I can continue the investigation.
If I delete "checkout" from the URL, it shows the thank you page. Does this help in finding the error?
That’s expected, as you’re just calling a regular page. I tried to isolate possible error sources on staging, but the site ran into a 500 error after deactivating unnecessary plugins.
Could you please provide FTP credentials so I can bring the site back online and continue debugging?
it's not just opening a regular page as the Woocommerce variables such as order number etc. are all filled out. So Woocommerce is passing data to the page but the page doesn't show as it should.
Yes, that's correct. What I mean is that the /thank-you page will always load properly if accessed directly, just like any regular page (e.g., Imprint or 'All Products'), even if no form fields have been filled out. WooCommerce loads that via URL parameters.
Once I isolated the issue, the 404 error disappeared. Orders now open with the correct page URL structure, for example: versteckter Link.
For now, I can confirm that the 404 was caused by a third-party plugin. My next step is to reactivate the other plugins one by one to identify exactly when the URL changes.
Can you clarify where exactly you’re assigning the “Thank You” page? If I set it here:
versteckter Link
…it doesn’t seem to have any effect. I also don’t see any other location where this could have been added, since all custom modifications are currently deactivated.
At the moment, after changing the defined page, even the default language returns a 404. This happens because it now loads from /kasse/vielen-dank, which is actually the correct permalink. Previously, it skipped the /kasse part and loaded from /de/vielen-dank, which wasn’t correct but still worked for the original language.
Technically, the correct endpoints are:
- .de/kasse/vielen-dank
- /en/checkout-thank-you
…and not .de/vielen-dank or /en/checkout/thank-you as before.
It seems the plugin you used may have stored the location in a cache or transient. If that’s the case, and you haven’t set it anywhere else, I’d recommend reaching out to the plugin authors. They handle WPML compatibility inside their own codebase, so this would likely need to be fixed on their side.
