Skip Navigation

Home › Support › English Support › [Resolved] Site critical 404 errors after WPML 4.7.2

[Resolved] Site critical 404 errors after WPML 4.7.2

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.

This topic contains 0 reply, has 1 voice.

Last updated by mateuszG-14 2 months ago.

Author Posts
April 8, 2025 at 9:57 am #16908206

mateuszG-14

Background of the issue:
Since around 20 March, my client has been experiencing significant financial losses due to 404 errors when adding products to the basket. The issue is more frequent when accessing the site via a link with parameters from an advert. Our investigation suggests the problem started after updating WPML to version 4.7.2, which included changes for WooCommerce Performance. We need urgent information on how to disable these changes to prevent further losses. Link to a page where the issue can be seen: hidden link

Symptoms:
Site is experiencing critical 404 errors without any composition, especially when adding products to the basket or accessing via links with parameters.

Questions:
How can we disable the changes made in WPML 4.7.2 to stop the 404 errors?
April 11, 2025 at 11:30 am #16922442

Marcel
Supporter

Languages: English (English ) Spanish (Español ) German (Deutsch )

Timezone: Europe/Madrid (GMT+02:00)

Hi,

before your ticket is assigned to one of my colleagues, please allow me to walk you through some initial debugging steps. This will help speed up the support process.

Please let us know once this got checked so we can continue.

Best Regards
Marcel
April 14, 2025 at 9:42 am #16928077

mateuszG-14

We have not found the exact cause, but previously we were using links in various places in a form without a domain like '/de/sample'. After changing the links to 'example.com/de/sample' the problems were solved. This also applies to attribute action in forms. It certainly has something to do with the new google attributes like gad_source, gclid and _gl, but in our case the solution with the domain in the link took care of it.