New to the community? Start here

[Beehive Pro] Conflict with BackupBuddy (iThemes) & Beehive Pro

I noticed something recently – when I have BackupBuddy & Beehive Pro activated, I can’t access or send backups to my Google Drive destination. When I deactivate Beehive Pro, I can see and send backups to that destination with no issue. I realize this is a conflict with another plugin that isn’t under your purview, but I’m sending a message to both help centers in the hope that it can be resolved.

Mon, 11 Nov 2019 23:34:29
More Beehive Pro discussions
Beehive Pro
  • jkyoung08
    • Flash Drive

    A response from iThemes support that might shed some more light on the issue:

    More than likely the Beehive Pro plugin is indiscriminately loading 3rd party library code (Google Drive in this case) and this is causing a conflict with the legitimate actions of BackupBuddy. And it looks like it’s causing issues with other plugins as well:
    https://vvpmudev.com/forums/topic/beehive-pro-potential-conflict-between-beehive-pro-and-updraftplus-premium/

    Unfortunately WordPress (well PHP really) doesn’t have a mechanism for supporting the loading of multiple versions of 3rd party libraries and so in the context of WordPress this means that plugins/themes have to be good WordPress citizens and not do these sort of things that will interfere with the operation of other plugins.

    It’s possible that the developers of that other plugin are misunderstanding in their code and that they believe that such 3rd party libraries can be “shared” on the basis that something is already loaded that “looks like” it may be the expected library but really this is not the case and in fact is unsafe. The only 3rd party libraries that can be reliably and safely “shared” are those provided by WordPress – trying to share any other library is inherently unsafe.

    In order to resolve this issue the other plugin developers need to update their design such that their plugin only loads such libraries when it has determined that it is being called upon to do some action that requires the library. This may be as simple as not doing anything unless the page being loaded belongs to it or only loading as much as is required for basic plugin initialization normally and then only loading additional stuff such as 3rd party libraries when something invokes that functionality. This of course has the side benefit that if a plugin only does the minimum it has to do under and given circumstances than the more efficient things are because no unnecessary code is being loaded and so the faster the site is.

  • Predrag Dubajic
    • Support

    Hi jkyoung08 ,

    Our devs have a patch ready for next release of the plugin, it’s not still fully tested by QA but I gave it try on my installation and it worked fine for me.
    I have attached the fix below in case that you want to apply it prior to full release, all you need to do is unzip the file and place it inside wp-content/plugins/google-analytics-async/core/modules/google-auth/ folder.

    As I mentioned above, it’s not fully tested by QA yet so I would suggest creating a backup before applying the fix, just to stay on the safe side.

    Best regards,
    Predrag