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 5.39 hours from now. Thank you for your understanding.
This thread is resolved. Here is a description of the problem and solution.
Problem: Using the "next_posts_link" secondary language link is not correct, throws the page 404 error not found.
Solution: If you are using a custom post type, you must translate the slugs of the page.
- On the WPML > Translation Management > Multilingual Content Setup - Click on the "Custom posts slug translation options" - Select the "Translate custom posts slugs (via WPML String Translation)." option - Scroll down and look for the "Custom posts" - Check the "Use different slugs in different languages for ..." - Translate the slug of the URL