Meta Box

Fatal Error after update AIO can't access Plugins

Support › Meta Box AIO › Fatal Error after update AIO can't access Plugins

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • November 27, 2019 at 9:27 AM #17164
    lighterdayzlighterdayz
    Participant

    Metabox AIO was creating a script error with another app (aMember Pro). Since we needed immediate access to aMember for registrations and could not access the plugins page, we deleted Metabox AIO fromt he the server. We are still getting this error

    Cannot declare class ComposerAutoloaderInit01076bd0d5d103ef6f95e7ea59379848, because the name is already in use in xxxxx/wp-content/plugins/meta-box-aio/vendor/meta-box/meta-box-beaver-themer-integrator/vendor/composer/autoload_real.php on line 5

    There was an instance of metabox beaver themer integrated, but that was deleted before deleting AIO. Still not able to access the plugin panel.

    Please help me get the plugin panel back.

    November 27, 2019 at 11:00 AM #17168
    Anh TranAnh Tran
    Keymaster

    Hi,

    Can you please confirm which plugins are activated? Are Meta Box AIO and/or the individual Meta Box Beaver Themer Integrator activated?

    I've just tried on my localhost with Meta Box AIO activated and Meta Box Beaver Themer extension enabled in the AIO (not the individual plugin) and don't see the error.

    November 28, 2019 at 12:52 AM #17197
    lighterdayzlighterdayz
    Participant

    I believe I activated AIO instead of updating the plugin. That crashed the site since AIO is not compatible with aMember Pro. That also caused the MB Beaver Themer error.

    I had to delete both the AIO and meta box themer plugins to gain access to the site and to enable aMember Pro to work for registration purposes. I could not access plugins. I have access to the dashboard, but now I can't access the plugins page at all. I tried to deactivate all plugins via database. That took the site down. That error is over riding the plugins and it shows when I deactivate all plugins.

    What can I do to remove this error?

    Thanks

    November 28, 2019 at 1:08 AM #17198
    lighterdayzlighterdayz
    Participant

    I was able to get rid of the notice by clearing every cache available. I will be back in touch about the aMember Pro.

    Thanks!

  • Author
    Posts
Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.