WPML redirects GET var to 404 page

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.

Tagged: Exception

This topic contains 0 replies, has 0 voices.

Last updated by aigarsM 3 days, 20 hours ago.

Assisted by: Christopher Amirian.

Author	Posts
February 4, 2025 at 1:23 pm
aigarsM	Background of the issue: I am trying to access hidden link, but WPML redirects me to a 404 page. The original website is hidden link. I have created a test site hidden link. I have deactivated all plugins and changed the theme to default WordPress. Symptoms: WPML redirects me to a 404 page only when the GET variable is 'projects'. With any other variable name, everything works correctly. Questions: Why does WPML redirect to a 404 page when the GET variable is 'projects'? How can I prevent WPML from redirecting to a 404 page with the 'projects' GET variable?
February 4, 2025 at 1:43 pm
February 4, 2025 at 2:28 pm #16667324
Christopher Amirian Supporter Languages: English (English ) Timezone: Asia/Yerevan (GMT+04:00)	Hi, I wanted to inform you that I asked for a second opinion and I will get back to you as soon as I have an update. Thank you for your patience.
February 5, 2025 at 1:32 pm #16671292
Christopher Amirian Supporter Languages: English (English ) Timezone: Asia/Yerevan (GMT+04:00)	Hi, The second tier support also agrees that there might be a post type, taxonomy, or some element that had the projects slug and WPML had to manage those. That is the reason of the problem. You will need to check the database of your website to find out what that might be. Thanks.
February 6, 2025 at 8:14 am #16673830
aigarsM	The main issue here is that everything was working fine, and then, seemingly out of nowhere, WPML started conflicting with the post type slugs. Another confusing aspect was that WPML conflicted with a GET variable rather than a post slug. I would have appreciated a bit more detail on the issue, such as where in the database I should look for the conflict or why WPML behaves this way. That said, I have found a workaround, and my issue is now resolved.