Please make sure to update to WPML 4.3.6 and check our list of Known Issues before reporting

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.

Our next available supporter will start replying to tickets in about 11.10 hours from now. Thank you for your understanding.

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

Problem: Slug for a custom post type is translated, however in the front-end the links are still leading to the other (non translated) slug / or the page produces error 404.

Solution: It is always a good idea, first to delete the old slug from WPML -> String Translation. Then you can always go to WPML -> Translation Management -> Multilingual Content Setup -> Custom Posts - and re-translate your slug for the custom post type that you want to have translated.

This topic contains 16 replies, has 3 voices.

Last updated by George Botsev 3 years, 9 months ago.

Assigned support staff: George Botsev.

Author Posts
April 18, 2016 at 9:53 am #863208


Hello George,

You just gave me a great start to the week. Worked like a charm.

Thank you very much!

April 18, 2016 at 10:01 am #863216

George Botsev

Languages: English (English )

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

Thank you for confirming that it works!
I am very happy that your issue is resolved.