how long have you been using the plugin, and how long has this error appeared?
Thread Starter
sc1961
(@sc1961)
I’ve been using version 3.0.1 for many months and it still works fine in our development site which has not been updated to 3.0.3.
The error has only appeared since the update to 3.0.3.
Can I get a download of 3.0.1 from somewhere and try installing that on our live site?
yes please
go to
https://ww.wp.xz.cn/plugins/bbp-private-groups/developers/
and at the bottom you will see all the previous versions
nothing further heard – marking as resolved
Thread Starter
sc1961
(@sc1961)
Hi Robin
Sorry for the delay in getting back. I installed the previous version of bbp Private Groups now but I’m still getting the errors in the back end and also when I click the Forums link in the front end.
Would it be possible for you go in and have a look if I get you login details?
It only happens on our live site which is running WordPress 4.2.3
Our development site is fine but it’s running 4.2.2
Thanking you
S
I’ve now had a chance to do some in depth investigation.
These errors are technical, and you seeing them will probably be down to either having debug switched in in one site (live) and not the other (dev), or having different database software (php) versions.
In essence the error is saying that it can’t find a value on the database – this is because that value isn’t set. It is a semantic difference between a value existing in the database and being set to nothing, or it not existing.
I need to fix the code, but it will not affect how the plugin works.
My code should do a double check, first to see if the value exists, and then to see if it is set to something. I have by mistake omitted the first check in some places.
I will fix this soonish, but I have some paid work to complete first.
In the meantime, can you tell me if you have debug switched on in live? If you need help on how to check this, please come back. If so then you can change that, and the errors will not show.
should all be fixed in 3.0.5
Thread Starter
sc1961
(@sc1961)
Thanks Robin 🙂
I checked the config file as you suggested and debug was, in fact, turned on in the live site. Changing that to false fixed the issue.
Thank you for your help.
S
Great – thanks for letting me know