cache.lat
On October 21, 2026, the PHP project released PHP 8.5.12, marked as a security version on the official php.net releases page, which lists branches 8.2, 8.3, 8.4, and 8.5 as supported. If you manage a WordPress, this affects you even if you don't touch a single line of code: the PHP version lives on your hosting, and if no one updates it, your site keeps running on the previous one.
What changes for your site
A security version doesn't bring new features: it fixes bugs. That's why the risk of updating is usually low compared to the risk of not doing it. The details of each fix are in the official php.net changelog; it's worth reading it before deciding how urgently to update, and not trusting third-party summaries.
Keep in mind that the supported branches include 8.2, 8.3, 8.4, and 8.5. If your hosting is still on a branch that no longer appears as supported (for example 8.1 or earlier), it doesn't receive these fixes and the problem isn't solved with a minor patch: you have to migrate branches.
How to know which PHP your WordPress runs
- In the WordPress dashboard, go to Tools > Site Health > Info and open the Server section.
- In your hosting panel (cPanel, Plesk, or another) there's usually a PHP version selector.
- If you can't find either of the two, ask your provider which exact version it uses and when it applies the patches.
Simple plan to update without scares
1. Make a backup
Files and database, and check that it can be restored. It's the cheapest insurance there is.
2. Test first in staging
If you can, clone the site to a test environment, change the PHP version there, and browse the key pages: home, a post, the cart or contact form, and the admin. Look at the PHP error log for new notices.
3. Update in production during quiet hours
A minor version update within the same branch is normally quick. Afterwards, verify that the site responds and that no errors appear.
4. Check your cache
Changing PHP shouldn't break a static page cache, but it's the moment to confirm it's still serving what it should. With cache.lat, the HTML is served as a static file and PHP only intervenes when regenerating a page; you can review the mechanism in how cache.lat works. After updating, open a page in a private window and check in the source code that it's still marked as served from the cache.
Why the cache helps these days
While you update, restart services, or test changes, the server works harder than normal. If most visits are answered with static files, a PHP-FPM restart or a couple of minutes of maintenance affect those browsing much less. It doesn't replace the patch, but it reduces the impact of applying it.
If you want to see the technical details of how regenerations and the queue are handled, the documentation explains them step by step.
Common mistakes when updating PHP
- Updating without looking at the plugins. An abandoned plugin can give notices or fatal errors with new branches. Check which ones have gone months without an update.
- Leaving debug mode enabled in production. New notices shouldn't be shown to visitors; send them to the log.
- Forgetting the CLI version. Sometimes the website uses one version and the command-line scheduled tasks another.
- Not testing again after the change. A site that loads the homepage can fail at checkout or in the members area.
Summary
PHP 8.5.12 is a security version confirmed on php.net, with support for branches 8.2 to 8.5. Verify your version, read the official changelog, test in staging, and apply the update with a backup. If you have doubts about how this fits with your cache, you can write to the TuNegocioEnLinea.net team.