Plugin Support
Adrian
(@adrianrus)
Hello @thehinesgaphideaway ,
Thank you for reporting this! Could you please confirm where you encountered this error, is it appearing in your website’s error_log, or did you find it elsewhere?
Also, were you performing any specific actions in the plugin when the error occurred, or was it simply active?
PHP 8.5 is extremely new, and we haven’t had the opportunity to test compatibility yet. We’ll prioritize fixing this as soon as possible!
All the best,
Thread Starter
Thomas
(@thehinesgaphideaway)
Apologies, the warning is encountered in WordPress admin within the dashboard. No actions, just with PHP8.5 enabled.
-
This reply was modified 6 months, 1 week ago by
Thomas.
Plugin Support
Adrian
(@adrianrus)
Hi again, @thehinesgaphideaway ,
Could you please attach a screenshot of where exactly you’re seeing this notice?
I’m asking because I’ve run some tests on PHP 8.5, optimized a few images and so far I’m unable to reproduce the notice.
All the best,
Thread Starter
Thomas
(@thehinesgaphideaway)
Adrian,
You are correct. I no longer see this warning. There had to be a specific case but I cannot recreate it. Should I see it again, I will resubmit it, along with a robust test case.
Thank you!
I was able to recreate it using CLI cron command (I can not share it), and looks like fix is simple:
find:
$old_value = (boolean)$old_value;
$value = (boolean)$value;
replace to:
$old_value = (bool)$old_value;
$value = (bool)$value;
-
This reply was modified 1 month ago by
viliusl.
Plugin Support
Adrian
(@adrianrus)
Hello @viliusl ,
Could you please tell us what CLI command did you run and maybe change/obfuscate some private areas within it?
We would like to see in which cases would this error appear and where exactly does it appear, as we’re unable to reproduce it on a normal WordPress installation with PHP 8.5
All the best,
Actually i can see same error when running this CLI command, but I have customized project with many plugins (with your latest plugin).
php wp-cron.php
-
This reply was modified 1 month ago by
viliusl.
Plugin Support
Adrian
(@adrianrus)
Thank you for letting us know about this guys!
The fix for this will be coming with the next plugin update! 🙂