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.
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.