Hello @galapogos01,
Thank you for reaching!
So that we can understand your site setup better, could please share with us your System Status Report?
You can get it by navigating to the WooCommerce / Status section of your site. Once there, click on the Get system report button and then copy it by clicking on the Copy for support button, then paste it here.
Please feel free to redact any information from your System Status Report that you think should not be shared publicly. 🙂
Thank you!
Thread Starter
Jason
(@galapogos01)
To avoid wasting my time, can you answer when you will test your plugin against PHP 8.2 as I asked in my first post?
Thank you!
Hello @galapogos01,
The plugin will work as expected with PHP 8.2, this is just a deprecation notice, it won’t break anything. :)
I asked the team to log this as an issue so it can be fixed in the future. You can simply ignore it for now.
Let us know if you have any other questions!
Thread Starter
Jason
(@galapogos01)
Hi Saif,
It is not simply a deprecation notice on a developers console. On a high traffic site, this issue causes massive amounts of logs – there are 10+ deprecation messages from this plugin on every page load. Multiply that by the number of visits per day and you have a recipe for catastrophe.
It also has severe performance implications when the PHP engine has to log these messages.
Can you please make sure this backlog item has sufficient severity to indicate the significance of the problem as simply “ignoring it” is not an option.
Thanks,
Jason
Hey @galapogos01,
Our development team is already aware of this issue. At the time being, we can’t give you an estimate for when the team will look into or fix the issue, as bug reports are prioritized based on a few criteria.
Your contribution to improving our plugin is greatly appreciated, and we thank you for your patience as we work on this.
The plugin will work as expected with PHP 8.2, this is just a deprecation notice, it won’t break anything. :)
This type of response doesn’t understand how log spam affects professional grade error collection tools that professional grade WP apps are highly likely to use. With Sentry, you would trigger critical alert thersholds, cause overage charges, generate annoyment against your product because now admins have to manually patch / silence your specific notices out, etc etc.
@galapogos01 is absolutely right with asking this to be patched up by now.
Plugins should be dead quiet with WP_DEBUG enabled on all PHP production releases.
Hello @lkraav,
We appreciate your feedback. We’re fully aware of the importance of maintaining a quiet environment when WP_DEBUG is enabled on PHP production releases. Furthermore, we’re committed to ensuring that our plugins are as user-friendly and efficient as possible.
Please be assured that we’re actively working on this issue and are striving to implement improvements to minimize log spam.
In the meantime, if you are also facing a similar issue, I suggest that you start a new thread with your case, so that we don’t mix several troubleshooting sessions in one thread. Even if the symptoms are the same, perhaps the underlying problem is different in your case.
Cheers!
I reported this issue three months ago (see https://wordpress.org/support/topic/deprecation-notice-in-php8-1/), it’s a shame that it still hasn’t been addressed as the fixes involved are not complicated and as mentioned above are very annoying to developers working with the logfiles, as this plugin is adding so much noise to them.
Other plugins I have reported the same issue to have responded and fixed the issue within days/weeks.
Hello @lumpysimon,
I reported this issue three months ago (see https://wordpress.org/support/topic/deprecation-notice-in-php8-1/), it’s a shame that it still hasn’t been addressed as the fixes involved are not complicated and as mentioned above are very annoying to developers working with the logfiles, as this plugin is adding so much noise to them.
I completely understand your frustration. I wish I could share the issue report with you to track the progress, but the development repository for this plugin is private.
I’ve informed the team about all the feedback mentioned here. However, at the moment, we still don’t have an estimate of when it will be addressed.
Apologies for any inconvenience this notice may have caused!
After discussing this with the team, it turns out a fix is already in the making. If everything goes as planned, it will be included in the next release. :)
Thank you for the update Saif, much appreciated.
