That’s a known issue with opcache and is not related to the plugin. Fixed it by adding to the pho.ini file:
opcache.interned_strings_buffer = 8
opcache.memory_consumption = 128
Everything works fine now.
I’m still seeing this as an issue. We added that to the php.ini file and it still breaks the site.
Hi @imarkinteractive
I’ve checked your site and I cannot find the notices you have mentioned.
Would it be possible to provide more details how we can reproduce the issue and where do you see the errors?
Regards,
Stanimir
Which site are you checking?
The site we were working on had the php.ini file removed so it wouldn’t break.
Which one would you like me to check? 🙂
We were working on this site for a customer – https://detailedwifeorganizedlife.com
Just ran across another one with the same issue. Once I removed SG Optimizer, it works just fine.
This is not a regular behaviour. Please, open a ticket in your Help Desk. Our support team will assist you further. We need the propper access and agreement from the customer to debug this.
We have encountered it in at least 30 sites already and it seems to be the OPCache not clearing on your end. Each time we have to contact upper level support and they clear the OPCache. That never used to be a problem nor is it a viable solution.
Did you bring this to the attention of WordFence? Opcache is enabled for every PHP 7+ we have on our server and the SG Optimizer plugin has nothing to do with it. We do not manipulate Opcache from the plugin in any way.