Plugin Author
bnfw
(@voltronik)
Hi @f14m07,
Thanks for your message.
A deprecated message shouldn’t prevent your site, or the plugin, from working.
Can you confirm you’re running the latest version of WordPress (6.3), BNFW (1.9.3), and PHP 7.4 or PHP 8.0?
Thread Starter
Fred17
(@f14m07)
Hi,
You’re quite right. I’ve since reactivated the plugin and everything seems to be working normally.
Plugin Author
bnfw
(@voltronik)
Hi @f14m07,
No problem. Glad you have it working.
I would like to fix that deprecated message, if possible.
If you’re able to let me know the versions from my last reply, please do so I can investigate.
Thread Starter
Fred17
(@f14m07)
I am uptodate for all my plugin and WP versions. This plugin is 1.9.3
Plugin Author
bnfw
(@voltronik)
Hi @f14m07,
Ah, I think you’re running PHP 8.2, which BNFW isn’t tested with yet. Anything from PHP 7.4 to PHP 8.1 you should be fine with though. I’ll add this to my list of things to test for PHP 8.2.
Thread Starter
Fred17
(@f14m07)
Many thanks for your help
Adding a Me Too here. If I may … an issue is not resolved when you confirm that it’s an issue. It’s resolved when the problem being reported is no longer a problem. Please Uncheck the resolved status here so that we know when it’s actually addressed in an update. Thanks!
Plugin Author
bnfw
(@voltronik)
Hi @starbuck,
Thanks for your message.
In this scenario, @f14m07 highlighted an issue with PHP 8.2 which BNFW doesn’t claim compatibility with yet. I feel this is the same as if someone reported an issue with PHP 5.4 – another version of PHP that BNFW doesn’t claim compatibility with. I have added it to my roadmap but felt the issue was resolved by explaining this and suggesting downgrading to PHP 8.1. As WordPress Core itself doesn’t claim full PHP 8.2 compatibility yet, I felt this was fair.
Hi, is there a timeline for when the issue would be solved?.
It’s been over 3 months, since it was first reported. I agree lack of support shouldn’t result in an unresolved issue but noting that the issue also helps those interested know that it’s been reported and that it’s actively being worked on. Thanks for your work on this much appreciated.
Plugin Author
bnfw
(@voltronik)
Hi @tonyejack,
PHP 8.2 compatibility is slated for the next point release which I’m currently working on. I have no timeframe for this at present however. My recommendation is to stay on PHP 8.1 for the time being, where possible.
@voltronik – Thank you for your cordial response. I have to agree.
For anyone else who is concerned about these messages, they are warnings, not errors. If you disable debugging you will not see the errors anymore. As a technician of over 40 years I can’t tell you how much it pains me to say something like that, but in this case …it’s OK. Really. Let’s not sweat the small stuff. If you need the debugger active and you don’t like these warnings in your log(s), filter them out …it’s OK. Really.
To be clear, the definition of the word “deprecated” is that the feature Will, In The Future, not be supported. It does work Now. These warnings (not Errors) are for developers, to let them know they need to do something before the next release … or two … or three … or something will break Then, not Now.
I hope that helps.
Plugin Author
bnfw
(@voltronik)
Thanks for clarifying @starbuck – a good explanation 🙂
