Skip to content Skip to sidebar

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

Problem:
If you're experiencing a 'page not found' error when using the language switcher on your 'About Us' page, even though the backend indicates that the page is translated into all target languages, the issue might be related to permalink settings or cache.
Solution:
1. Navigate to Pages in your WordPress dashboard and find your 'About Us' page in English.
2. Check the translation icons for each language. If you see a 'page not found' error for a specific language, click the pencil icon to edit that translation.
3. Ensure the translation is published and not in draft or pending review.
4. Verify the page's permalink/slug in each language to ensure it isn't empty or conflicting. Adjust if necessary and update the page.
5. Go to Settings → Permalinks and click Save Changes to refresh WordPress permalinks, which can often resolve 404 issues.
6. If using Elementor templates, make sure the translated templates are published and correctly assigned.
7. After following these steps, use the language switcher on the frontend to check if the issue is resolved. If the problem persists, try clearing your site's cache and browser cache.

If these steps do not resolve the issue, it may be helpful to deactivate any caching plugins temporarily, such as the "Redis Object Cache" plugin, as this has been found to resolve similar issues for other clients.

Please note that this solution might be outdated or not applicable to your specific case. We highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the problem persists, please open a new support ticket.

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 1 voice.

Last updated by Johannes Rohr 7 months ago.

Assisted by: Kor.

Author Posts
October 3, 2025 at 3:25 pm #17454893

Johannes Rohr

Background of the issue:
I am trying to switch from English to any other language on our 'about' page using the language switcher. The issue can be seen at this link: hidden link

Symptoms:
When I use the language switcher, I get 'page not found' instead of the translated page.

Questions:
Why does the language switcher lead to a 'page not found' error, even though the backend says that the page is translated to all target languages?
How can I ensure the translated page is displayed correctly?

October 3, 2025 at 3:30 pm #17454906

Johannes Rohr

as said above: I can't access the translated about page, neither in the backend nor in the frontend. The language switcher leads to page not found, so does clicking the eye icon for the translations in the pages overview.

October 6, 2025 at 1:10 am #17457898

Kor

Thanks for your reply.

I've checked your Website and I can see the issue you had there. I will need to closely examine your website. Therefore, I will require temporary access (WP-Admin and FTP) to a test site where the problem has been replicated, if possible. This will enable me to provide better assistance and determine if any configurations need to be modified.

Please note that it is important to have a backup for security purposes and to prevent any potential data loss. You can use the UpdraftPlus plugin (https://wordpress.org/plugins/updraftplus/) to fulfill your backup requirements.

Your upcoming reply will be treated with confidentiality and will only be visible to you and me.

✙ To resolve the issue, I may need your consent to deactivate and reactivate plugins and the theme, as well as make configuration changes on the site if necessary. This emphasizes the significance of having a backup.

October 6, 2025 at 9:37 am #17459171

Kor

Thanks for your reply. It seems to work fine after deactivating the "Redis Object Cache" plugin. Could you check?

October 6, 2025 at 9:49 am #17459245

Johannes Rohr

OK, flushing the redis cache seems to solve it. But this shouldn't happen.