[Resolved] 404 not found at translated page (specific page)
This thread is resolved. Here is a description of the problem and solution.
Problem: The client's site is experiencing '404 not found' errors on the 'LNG System' and 'Consulting' child pages in the English version, while the Chinese version and other English pages work normally. Solution: We identified the root cause as the slug configuration of the parent page. We recommend changing the slug for the English version of the 'LNG System' page from 'lng-system' to 'lng_system'. This modification should resolve the issue with the child pages. Additionally, we have replicated a similar issue in our development environment and provided a workaround in our Errata page. For more details and the steps we took, please check the following link:
Our site uses WPML for English and Chinese translations.
There is a main menu and several submenus, but the '404 not found' error occurs only in the 'LNG System' and 'Consulting' childpage on the English version.
It works normally on Chinese pages and other English pages, and I tried other solutions (related to WPML Troubleshooting) and increasing the memory to 256MB, but it did not work.
On the translated pages, the 404 error usually appears due to a corrupted permalink structure or if the page/post is saved in draft. Please try the following steps and check if that helps to solve the issue.
- Please go to "Settings > Permalinks" from your WordPress Dashboard
- Resave the structure without making any changes
- Now, go to "Pages > All Pages" and switch to the English language.[Using the language switcher on topbar of Admin]
- Locate the page that shows a 404 error and click on "Quick edit".
- Make sure that the 'Status' is set to 'Published'
- Clear the caches from the site.
I would like to inform you that upon reviewing the site, I did not experience any 404 errors on the English versions of the "LNG System" and "Consulting" pages. Should you encounter this issue in the future, please follow the provided instructions. Don't hesitate to reach out if you require further assistance, as I am more than willing to help.
I tried the method you suggested, but the problem still occurs.
The three links below are all on the same page and are divided according to translation.
Only see the problem occurring in the English translation. Please confirm.
Korean - hidden link
English - hidden link
Chinese - hidden link
Hi There,
Thank you for trying out the suggestions.
Sometimes, using the same slug for multiple posts can lead to issues like this. Could you please check and confirm that the slug "purchase-information" has not been used for more than one page/post/taxonomy in the English language?
If you have identified any instances where the same slug is used more than once, please modify the slug of this page or wherever it has been used, ensuring that each slug is unique. WordPress does not support identical slugs, and for this reason, it's important NOT to use the same slug on more than one posts, pages, or taxonomies.
If the slug is configured correctly, a closer inspection will be required to understand the root cause of the issue.
I would like to request temporary access (wp-admin and FTP) to your site to take a better look at the issue. It would be better to have a testing site where the issue is replicated.
You will find the needed fields below the comment area when you log in to leave your next reply. The information you will enter is private which means only you and I can see and have access to it.
Maybe I'll need to replicate your site locally. For this, I’ll need to temporarily install a plugin called “Duplicator” or "All in One WP Migration" on your site. This will allow me to create a copy of your site and your content. Once the problem is resolved I will delete the local site. Let me know if this is ok with you.
IMPORTANT
-Please backup site files and database before providing us access.
-If you do not see the wp-admin/FTP fields this means your post & website login details will be made PUBLIC. DO NOT post your website details unless you see the required wp-admin/FTP fields. If you do not, please ask me to enable the private box. The private box looks like this: hidden link
Hi There,
thank you for sharing the access information.
After carefully investigating your site, I found a significant error in the Settings > Permalink section. Please check this screenshot: hidden link. This is a crucial issue as the .htaccess file plays a vital role in managing the permalink structure of your website. Its current non-writable state is likely contributing to the 404 error on the English version of your site and could potentially impact other language versions as well.
To resolve this issue, it's essential to ensure that the .htaccess file not only exists but is also writable. This adjustment will allow WordPress to automatically update permalink settings as needed. Given the technical nature of this change, I recommend reaching out to your hosting provider for assistance. They can guide you on how to modify the file permissions to make .htaccess writable or might be able to make the changes for you.
Once the .htaccess file is writable, and the error is resolved, please make a small update in the default language of your site, save these changes, and then update the English translation. This action should help in rectifying the permalink issues and resolving the 404 error for the English page.
Please do not hesitate to reach out if you need further assistance or if there are any other issues. I'll be happy to help.
As you mentioned, I changed the permissions of the htaccess file, modified some of the page content, and synchronized it, but the problem still occurs.
Is there another way? In the translated version, you cannot edit the page, and even if you click the 'view' button, a message is displayed saying that it cannot be found.
Hi There,
Thank you for patiently trying out the suggestions.
I've taken another closer look and successfully identified the root cause of the issue. The primary cause was identified as the slug configuration of the parent page. By modifying the slug for the English version of the "LNG System" page from 'lng-system' to 'lng_system', the child pages have begun to operate as expected.
Furthermore, I wanted to inform you that we were able to replicate a similar issue in our development environment. Please check the Errata below for more details about the issue and the current workaround I implemented:
Thank you for your patience and understanding throughout this process. Please do not hesitate to reach out if you have any questions or require further assistance.
