PHP Warnings

Hello @awol,

We couldn’t replicate these warnings so far.

Could you please check if the issue persists after resetting (Beehive >> Settings >> Data & Settings >> Reset Settings), and re-installing the latest Beehive version.

If it still happens, please let us know more details:

– your PHP version;

– what exactly has been configured in Beehive before the warnings start appearing in the logs (or does it happen right away, after the installation);

– please run a conflict test as explained here and let us know the result.

Best Regards,
Dmytro

Hi @awol

I hope you are doing well and safe!

We haven’t heard from you in a while, I’ll mark this thread as resolved.
Feel free to let us know if you have any additional questions or problems.

Best Regards
Patrick Freitas

I’ve been bogged down trying to resolve the problem that led me to find the warnings (as well as some car trouble!) so haven’t had a chance to do anything, but thank you for your suggestion and I will look further into it once the other issues are resolved. The only thing that concerns me is that what you suggest looks like it would result in me losing my existing statistics – is there any way around that?

Hi @awol

Behive doesn’t “do” statistics – it integrates with Google Analytics which actually does that and stores data. Whatever Beehive would be showing you, it would be fetched (real-time) form connected Googel Analytics profile.

Disconnecting Beehive would, indeed, remove GA code from site and stop counting traffic for the time being – but if you do that operation relatively fast, it shouldn’t cause significant “gap” in stats.

Resetting Beehive plugin will not reset/delete data in Google Analytics – it will reset plugin configuration.

Best regards,
Adam

Hi Adam @wpmudev-support8,

I did the reset and reinstallation, and relinked my Google account, and the same errors appear. PHP version is 8.1. Nothing else has been configured. I have not run the conflict test as it is a live site and many of the plugins are crucial to it’s operation; however I have tried turning off the ones I can and it makes no difference. Would it be possible for you to examine the file and line in question (autoloader.php line 70) to see if there is some error in the code that would lead to this error? It seems to me that this is an entirely internal to the plugin function that wouldn’t be impacted by another plugin. Having looked at the file, with my patchy knowledge of PHP code I think lines 58 and 61 might be the issue:

Line 58

$file_name = "interface-$interface_name.php";

Line 61

$file_name = "class-$current.php";

I would have thought that these should be

$file_name = "interface-".$interface_name.".php";

and

$file_name = "class-".$current.".php";

respectively. I’m pretty sure you can’t include a variable in another variable that includes strings in the way they are on those lines.

I am not aware of any actual affects with regards to what the plugin does, but it might be that it is not doing something that it should be that I am not aware of. I also don’t know if it is having any negative effect on my site generally, but I don’t think it is, particularly as it is only a warning, but presumably at some point it might be a bigger issue.

Just as a further update – I tried replacing the code highlighted above, but the errors remain.

Hi @awol,

I tested in my system with PHP 8.1 but wasn’t able to replicate any such warnings in the log file.

Since it’s a live site, could we know whether you are able to replicate the same warning logs on a staging with all the plugins disabled or on a different test site?

I’m forwarding the reported logs to our developers attention to check what might be causing the logs and if there are any improvements required in the plugin side regarding this.

Will keep you posted once we get further feedback asap.

Best Regards,

Nithin

Hi @awol,

I would like to update you that we’ve identified opportunities for enhancing the plugin to better deal with these warning logs. Our Beehive team will be working on implementing these improvements in future updates.

Please keep in mind that these warnings should not impact your website or the plugin’s functionality in any way.

We will ensure to keep you updated with any further feedback or progress. Thank you for your patience and understanding.

Kind Regards,

Nithin

Hi @wpmudevsupport11,

I have been updating whenever a new version is released, but I am still getting these errors; is there any further update on this?

Hi @awol,

I’m afraid, the latest updates of Beehives were more about critical bug fixes. The improvement regarding the mentioned warning messages is still under development.

As stated before, these warnings shouldn’t affect the workflow of the plugin or the website.

Would recommend you to subscribe to our roadmaps page for any notifications regarding upcoming updates regarding Beehive once the Roadsmaps page is updated.

https://wpmudev.com/roadmap/

Kind Regards,

Nithin

Hi @wpmudevsupport11,

Someone marked this as resolved, but it’s not, so I have adjusted that. The warnings are still clogging up my debug log whenever I try to fix another issue and to be honest it is quite an irritation now, so much so that I am considering finding another plugin; however if there is any chance that these warnings are going to be fixed any time soon, I will wait. I thought a couple of months should have been enough time for that to happen by now. I know it is a free plugin, and appreciate it being available, but it is hardly great enticement for anyone to spend their hard earned money if it takes this long to fix something.

Hi @awol

I understand that this is a long time but our developers also need to sort of “prioritize” issues they are dealing with.

This particular one is about warnings only – that should not affect site/plugin features in other ways than just “clogging” logs possibly. This surely is not a desired outcome but is relatively minor issue.

Furthermore, it is not happening always for everyone – in fact we didn’t really have multiple reports about it.

However, I actually do have some good news: I checked and I see that fix for this particular issue is scheduled to be included in 3.4.10 release of the plugin. I don’t have ETA but it’s nearest upcoming update.

Kind regards,
Adam

Hi @awol,

I hope you are doing well today!

We totally understand your concern. However, since the bug was acknowledged, reported and planned to be fixed on v3.4.10, we are marking this as resolved.

You will be able to find the changelogs in https://www.ads-software.com/plugins/beehive-analytics/#developers on each update and marking this as resolved for now is totally fine.

Please note that, marking as resolved doesn’t close comments. Thanks for your understanding and if you have any further questions about this issue feel free to let us know.

Kind regards,
Zafer