We haven’t had a fix for this, other than a suggestion from WP-Optimize to update our PHP version, however as you say it’s affecting PHP 8.3/8.4 as reported by other users.
We have just disabled the browser caching feature by going into Static File Headers and setting the Browser static file caching headers Expiration time to 0 which disables it. You may need to also clear the cache in WP-Optimize and on your browser and restart to make sure the new cache settings are picked up. Make sure that the website can update .htaccess and any Cache-Control settings are no longer there.
In reality this only has a minor impact on performance in the real world, but in our opinion this is a major bug that should be fixed in the plugin. Backend pages should never be cached.
-
This reply was modified 2 months, 4 weeks ago by
digikb.
Hi @jjb100 and @digikb,
Thanks for bringing this back up! I’m going to report this to our development team to see if they are able to reproduce the issue.
On all of my test sites I haven’t been able to reproduce it yet but I’ll see if a developer can take a look at it, because you’re right the backend pages should not be cached or have new posts overwrite previous posts because of cache !
Thread Starter
jjb100
(@jjb100)
Hello,
Yes, that’s indeed a problem that should be fixed. It makes the work very tedious; before every post-processing, you have to remember to update the post first. And it’s also a security issue.
Okay, now I’m wondering what other causes there could be—apart from WP Optimize. Could it somehow be related to an update on WordPress? Could there be interferences?
I don’t think its a core issue. Disabling Cache-Control (Static File Headers) stops the issue. It’s not been a problem before.
To do this, browser cache should:
- Exclude
.php, or
- Exclude
/wp-admin/, or
- Apply only to static assets (CSS, JS, images).
Hi all,
Just wanted to send out a quick update that our developers have been looking into the issue and working to resolve it in a future release. I’m not sure if they have been able to reproduce the problem yet but they’ve been actively investigating since I reported it to them.
Thanks for your patience as we get this sorted!