Hi @ocio132 ,
Do you still experience the issue? I can see that the error is screened with @, so it shouldn’t appear. If you can confirm you still see it, most probably your error_reporting level is higher, so please let me know, I’d rather fix it for more strict error_reporting levels!
Best,
Alex
@ocio132 , it is not clear from your screenshot, when did this error happen. I would suspect it is from an 1 year old version of the plugin. Can you please double check it is actually a fresh one?
I just looked at it with the latest update today
@ocio132 I see. I can see litespeed cache enabled. Where are you hosted? Are you on litespeed lite or full blown litespeed?
server level is set in cPanel and in WP with the plugin
@ocio132 – I can confirm the issue with custom error_handler, the fix is on the way. Thank you for your patience!
Hi @ocio132 ,
The issue should be addressed in 3.1.7, please check
Best,
Alex
@ocio132 , that something litespeed cache plugin wants, unfortunately I don’t have control over it. I haven’t got any conflict notifications from Litespeed Cache, so I don’t think I can help with that. If you don’t experience any errors / warnings in the console or in Google Analytics – you should be good to go!
