Hi @josklever,
If you enable cache, there won’t be any log messages. If you don’t want to use caching feature, we will fix this in the next release.
But it is not recommended to turn on WP_DEBUG_LOG in production site.
I don’t use cache and I don’t want to enable it.
WP_DEBUG_LOG is not enabled. This is the PHP error log on the server, that should be empty and is actively monitored to detect errors on live sites.
Same error with version 3.2.5 (PHP 8.0):
[ERROR] : WPO_ADVANCED_CACHE constant is not present in advanced-cache.php
@roundaboutweb That’s a different error, so please create your own topic.
Exo
(@richardshea)
I think they’re both related.
And I see now in version 3.2.5 my server logs are filling up fast too:
[ERROR] : WP_CACHE constant is not present in wp-config.php
This seems to happen when you don’t want to use the cache feature, it’s a new bug.
And please don’t tell me NOT to have logs active on a production site – that’s a farcical statement, it’s NOT a WordPress feature but server based and SHOULD BE USED on live sites to monitor potential problems and should be empty at all times.
Hopefully 3.2.6 will fix this.
@richardshea @roundaboutweb @josklever We are soon going to release a new version, until then please rollback the version to previous working version 3.2.3.
Once the new version is released, we will update you soon.
Same issue here. Just wanted to comment so I’m notified when update released, thanks! Will roll back for now.
Hi,
We have just finished testing on a fix so a release should be available imminently.
Hello @vupdraft,
Were you referring to release 3.2.6 with release date June 15th 2022 on ww.wp.xz.cn?
If so, then I am sorry to say that it looks like the fix has not worked, or at least not completely. I get four messages
Backend log: [ERROR] : WP_CACHE constant is not present in wp-config.php
every time I activate WP-Optimize.
Best regards,
Henk Barreveld
Hi @henk-barreveld,
Please create your own topic, because mine was solved with the 3.2.6 update.
Thanks,
Jos
Hi @henk-barreveld and others who experience the same,
As @josklever told the issue was fixed, but if you still experience it, please try to do a clean installation of WP Optimzie
Regards,
Venkat