Skip Navigation

This thread is resolved. Here is a description of the problem and solution.

Problem: The client has a CPT, and he gets 404 error when trying to visit the translated posts on the front-end.

Solution: The issue has been fixed by resaving the permalinks, Go to Settings -> Permalinks and click the "Save " button.

Relevant Documentation: https://codex.wordpress.org/Settings_Permalinks_Screen

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 3 replies, has 2 voices.

Last updated by Kristof 3 years, 11 months ago.

Assigned support staff: Ahmed Ibrahim.

Author Posts
October 19, 2017 at 10:26 am #1405729

Kristof

I am trying to: view the French translation of this book

Link to a page where the issue can be seen: hidden link is ok, but French is a 404

I expected to see: the translated book

Instead, I got: a 404

This issue has been reported 3 times now and yet again, we are facing many 404's.
https://wpml.org/forums/topic/cfr-our-previous-support-ticket-this-now-happens-to-books-as-well/

October 19, 2017 at 10:41 am #1405743

Kristof

We had a look at our previous support article https://toolset.com/forums/topic/translated-url-slugs-now-all-throw-a-404-not-found-for-cpt-books/ and resaved the permalinks, this fixed the issue. But now, we need to know 100% why this is happening and how to prevent this in the future! We need to get to the bottom of this for once and for all.

October 20, 2017 at 1:54 pm #1407158

Ahmed Ibrahim
Supporter

Languages: English (English ) Arabic (العربية )

Timezone: Africa/Cairo (GMT+02:00)

Hi, and thanks for contacting our support forum.

We don't have any specific situation the could be the reason for that, but as long as the issue has been resolved when re-saving the permalinks then we are good, so please just observe this and let me know if it comes back again, also, please try to see if this happened after any specific action, like adding a new post for example or any action like that, and also let me know about it.

Best Regards.

October 23, 2017 at 8:12 am #1408328

Kristof

Resaving the Permalinks indeed fixed the issue (this time), but as we cannot guess the reason why the Permalinks got broken, we cannot inform our client what he is doing wrong, in the case that this is in fact a human error and not a system error.
We have now set up a 404 alert in Google Analytics so at least we will be informed earlier and maybe we can connect the issue to a recent activity by our client.