Last updated December 5th, 2023 23:09
Last week, the long-awaited new version of WordPress 6.4 was released. Shortly thereafter, within a 24-hour window, developers released another update in the form of version 6.4.1. WordPress itself encountered significant issues with this update, affecting tools like Oxygen Builder, among others. Many WordPress users, including myself, started experiencing a 404 error on every page and post, rendering the content inaccessible. The common denominator was the PolyLang plugin for multilingual websites. In this article, I will show two options how to resolve the 404 errorin WordPress 6.4 with PolyLang. Sometimes, the first option alone works, but if you have an older version of PolyLang, you may need to apply both. However, it won’t be complicated.
How To Resolve The 404 Error In WordPress 6.4 With PolyLang
The first thing you’ll need to do is regenerate the permalinks. WordPress has its own structure for pretty URLs, and in this case, it’s having trouble with it. Regenerating permalinks will refresh WordPress’s URL structure. You can regenerate permalinks as follows:
- In the left menu, go to the ‘Settings’ section.
- In the submenu, select ‘Permalinks.’
- Set the permalink structure to ‘Plain’ and save the settings.
- Once the settings are saved, revert the permalink structure back to its original value and save the settings again.
- By changing the permalink settings to ‘Plain’ and then back to the original, WordPress regenerates the entire URL structure.
If you have a caching plugin on your website, please clear this cache. If the website still doesn’t work, go back to the administration panel and navigate to the plugins section. Here, first deactivate the PolyLang plugin and then reactivate it. Again, clear the cache of the caching plugin.
If you have the latest version of PolyLang on your website, it should now function correctly.
I regenerated the permalinks, but the website still shows a 404 error, or it returns to it after a few hours.
If you have regenerated the permalinks, and the error persists or returns after a few hours, you probably have an issue with an old version of the PolyLang plugin. Follow these steps:
- In the menu, click on the “Plugins” link.
- In the list of plugins, find PolyLang, and if it requires an update, update it to the new version.
- If you also use the Polylang Connect for Elementor extension along with Elementor, update this extension as well.
- For reassurance, you can repeat the permalink regeneration.
- If you use a cache plugin, clear the cache.
At the moment when the website doesn’t load even after you regenerated the permalinks, the issue usually arises because you were using an old version of PolyLang, and it struggles with the new WordPress. If you update it, the problem with the 404 error will likely be permanently resolved.
How To Resolve The 404 Error In WordPress 6.4 With PolyLang
Conclusion
This example clearly shows, as experienced by many WordPress users, that updating the core, theme, and plugins is indeed not unnecessary. Do not underestimate it; you will avoid many problems this way. Thanks to the procedure outlined above, I have fixed three WordPress sites that had the exact same issue after updating to version 6.4. Many online discussions can be found where PolyLang users are addressing the identical problem. If this procedure also helped resolve your issue, I would appreciate a comment below the article.
The website is created with care for the included information. I strive to provide high-quality and useful content that helps or inspires others. If you are satisfied with my work and would like to support me, you can do so through simple options.
Subscribe to the Newsletter
Stay informed! Join our newsletter subscription and be the first to receive the latest information directly to your email inbox. Follow updates, exclusive events, and inspiring content, all delivered straight to your email.
Thank you for your useful article! My problem that 404 error on Polylang has been solved. I appreciate it!
Hello,
I’m glad to hear that my article helped you solve the problem.
Super, dieser Beitrag hat mir geholfen. Bei mir lag es auch am Polylang und den Permalinks. Vielen Dank.