Tet banner

Custom Fields
Support Meta Box AIO 500 Error after Checking Boxes in All in One Tab

  • Creator
  • #13584
    Jamie Jelly


    I'm new to WP and just downloaded the developer bundle. Last night I uploaded and activated all of the premium plugins that came with the bundle.

    This morning I clicked on the "All in One" tab. To be honest I'm not sure what this is for but was clicking around to learn...

    I thought there was an opportunity to update these plugins, so I clicked them all and clicked save. Then, my screen went immediately to a 500 Error.

    I called my host (Go Daddy) and they believe it was due to a theme or plugin. I'm assuming it's due to clicking every check box next to each premium plugin, but not sure why...

    Any ideas?

    Now I have a ticket open with GoDaddy but I intend to reinstall the plugins, so any advice for not having this happen again would be appreciated.

    Thank you,

Viewing 4 replies - 1 through 4 (of 4 total)
  • Author
  • #13604
    Anh Tran

    Hi Jamie,

    Would you mind enabling the debug mode and see what's the error? We have tested the plugins with all recent WordPress versions and they work without any problem. Perhaps it's PHP version or some PHP extensions missing.


    I have what may be the same issue. Only purchased today and testing on local server.

    The only difference is that I first only installed a few and then did not install any of the premium plugins except AIO.

    Fatal error: Cannot redeclare mb_cpt_load() (previously declared in C:\Users\Name\Documents\Websites\www.site.dev.cc\wp-content\plugins\mb-custom-post-type\mb-custom-post-type.php:30) in C:\Users\Name\Documents\Websites\www.site.dev.cc\wp-content\plugins\meta-box-aio\extensions\mb-custom-post-type\mb-custom-post-type.php on line 71

    MB_AIO_Loader->load_premium_extensions( ) ...\class-wp-hook.php:286


    Uninstalling all the free & premium plugins as per https://metabox.io/meta-box-aio-now-includes-free-extensions/ then reinstalling AIO and Metabox fixed it.

    Anh Tran

    Hi Galen, this error is caused when you have both AIO and MB Custom Post Type plugin enabled. I'll update the MB Custom Post Type to make a better check.

    Thanks for your feedback!

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