Hi Meta Box Team,
I am reaching out to report a fatal error that crashed one of our production sites after a recent update. The issue appears to be a compatibility conflict or a missing class check between the core Meta Box plugin and Meta Box AIO (specifically the MB Settings Page module).
When the site loads, it throws a Fatal Error, bringing down the entire frontend and backend. It seems the mb-settings-page extension is trying to invoke rwmb_get_registry(), which relies on the RWMB_Block_Bindings_Registry class that is either missing or not yet loaded at that specific action hook.
Here is the exact error log and stack trace:
PHP Fatal error: Uncaught Error: Class "RWMB_Block_Bindings_Registry" not found in /wp-content/plugins/meta-box/inc/functions.php:292
Stack trace:
#0 /wp-content/plugins/meta-box-aio/vendor/meta-box/mb-settings-page/mb-settings-page.php(62): rwmb_get_registry()
#1 /wp-includes/class-wp-hook.php(353): mb_settings_page_load()
#2 /wp-includes/class-wp-hook.php(377): WP_Hook->apply_filters()
#3 /wp-includes/plugin.php(523): WP_Hook->do_action()
#4 /wp-settings.php(779): do_action()
#5 /wp-config.php(100): require_once('...')
#6 /wp-load.php(50): require_once('...')
#7 /wp-blog-header.php(13): require_once('...')
#8 /index.php(17): require('...')
#9 {main}
thrown in /wp-content/plugins/meta-box/inc/functions.php on line 292
Additional Context:
WordPress Version: 6.7.x
The crash occurred immediately following an update. For now, we had to disable the plugin via FTP to regain access to the WordPress admin dashboard.
It would be highly appreciated if a class_exists() check or a version compatibility fallback could be implemented to prevent the core plugin from throwing a fatal error when a premium extension falls slightly out of sync.
Could you please look into this and let me know when a fix is expected?
Thank you for your time and assistance!
Best regards,
Péter
.
