Metabox v3.3.0 crash my site
Support › Meta Box AIO › Metabox v3.3.0 crash my siteResolved
- This topic has 12 replies, 8 voices, and was last updated 3 weeks, 2 days ago by
Galen.
-
AuthorPosts
-
November 6, 2025 at 1:57 PM #49277
Marco
ParticipantHello.
I've just updateds to MB 3.3.0 from 3.2.0 and my site on the forntend have this php fatal error."EXCEPTION Fatal Error
MetaBox\Integrations\WPML:: get_translated_value(): Argument #2 ($field) must be of type array, bool given, called in /home/y50I0f3wBG3c9QBM/paellasEnCasa/ public_html/wp-includes/class-wp-hook.php on line 326
Occurred in file: /home/y5010f3wBG3c9QBM/paellasEnCasa/public_html/wp-
content/plugins/meta-box-aio/vendor/meta-box/meta-box/src/Integrations/
WPML.php on line 110
No backup available. Please fix the error manually."Thanks
November 6, 2025 at 2:28 PM #49278[email protected]
ParticipantSame problem here. Two websites offline due to a fatal error after Metabox AIO plugin update. Is there a way to download the previous version of Metabox AIO ?
November 6, 2025 at 2:36 PM #49279[email protected]
Participant[06-Nov-2025 07:08:26 UTC] PHP Parse error: syntax error, unexpected 'static' (T_STATIC) in /htdocs/wp-content/plugins/meta-box-aio/vendor/wpmetabox/mbb-parser/src/Unparsers/MetaBox.php on line 273
November 6, 2025 at 6:19 PM #49281Tobias
ParticipantSame here. The update crashed my site. Some conflict with WPML.
November 6, 2025 at 6:24 PM #49282Tobias
ParticipantWhere to get the v.3.2.0 version?
November 6, 2025 at 6:39 PM #49283Tobias
Participanthttps://wordpress.org/plugins/meta-box/advanced/.
The version: 5.10.15 – 2025-10-06 works. The version 5.10.16 – 2025-11-05 introduced an error.
[06-Nov-2025 10:51:41 UTC] PHP Fatal error: Uncaught TypeError: MetaBox\Integrations\WPML::get_translated_value(): Argument #2 ($field) must be of type array, bool given, called in /home/xxx/webapps/xxx/wp-includes/class-wp-hook.php on line 326 and defined in /home/xxx/webapps/xxx/wp-content/plugins/meta-box/src/Integrations/WPML.php:110
November 6, 2025 at 8:11 PM #49285Christopher Hornick
ParticipantSame issue with me.
November 6, 2025 at 10:10 PM #49286Peter
ModeratorHello,
I'm sorry about this experience. You can downgrade the plugin Meta Box AIO to 3.2.0 by using this file
https://www.dropbox.com/scl/fi/n1tcqeut0pa6f7cu5g0d7/meta-box-aio-3.2.0.zip?rlkey=9m6hdhyawkfjx95fk0g38av31&st=w55j6eoe&dl=0We will fix the issues as soon as possible. Thank you.
November 7, 2025 at 12:21 PM #49291Paul Hogden
ParticipantHello - I am waking up to multiple sites down. I don't use the AIO the issue seems to be with core:
In this case, WordPress caught an error with one of your plugins, MB Core.
First, visit your website (https://ecta.co.uk/) and check for any visible issues. Next, visit the page where the error was caught (https://ecta.co.uk/wp-login.php) and check for any visible issues.
Please contact your host for assistance with investigating this issue further.
If your site appears broken and you can't access your dashboard normally, WordPress now has a special "recovery mode". This lets you safely login to your dashboard and investigate further.
To keep your site safe, this link will expire in 1 day. Don't worry about that, though: a new link will be emailed to you if the error occurs again after it expires.
When seeking help with this issue, you may be asked for some of the following information:
WordPress version 6.8.3
Active theme: Bricks Child Theme (version 1.1)
Current plugin: MB Core (version 2.3.0)
PHP version 7.4.33Error Details
=============
An error of type E_PARSE was caused in line 273 of the file /home/ectaco/public_html/wp-content/plugins/mb-core/vendor/wpmetabox/mbb-parser/src/Unparsers/MetaBox.php. Error message: syntax error, unexpected 'static' (T_STATIC)Please advise what to do URGENTLY
November 7, 2025 at 1:30 PM #49292Marco
ParticipantTo add more information, I'm also using bricks, in case it might be related to that.
November 7, 2025 at 3:09 PM #49293Key_Webdesign
ParticipantI'm pretty sure it has to do with the combination of Meta Box MB Blocks and WPML. This is the stack trace I got:
[06-Nov-2025 15:23:49 UTC] PHP Fatal error: Uncaught TypeError: MetaBox\Integrations\WPML::get_translated_value(): Argument #2 ($field) must be of type array, false given, called in *path*/public_html/wp-includes/class-wp-hook.php on line 326 and defined in *path*/public_html/wp-content/plugins/meta-box-aio/vendor/meta-box/meta-box/src/Integrations/WPML.php:110 Stack trace: #0 *path*/public_html/wp-includes/class-wp-hook.php(326): MetaBox\Integrations\WPML->get_translated_value() #1 *path*/public_html/wp-includes/plugin.php(205): WP_Hook->apply_filters() #2 *path*/public_html/wp-content/plugins/meta-box-aio/vendor/meta-box/meta-box/inc/functions.php(162): apply_filters() #3 *path*/public_html/wp-content/plugins/meta-box-aio/vendor/meta-box/mb-blocks/src/functions.php(6): rwmb_get_value() #4 *path*/public_html/wp-content/plugins/meta-box-aio/vendor/meta-box/mb-blocks/src/Loader.php(119): mb_get_block_field() #5 *path*/public_html/wp-content/plugins/meta-box-aio/vendor/meta-box/mb-blocks/src/Loader.php(92): MBBlocks\Loader::prepare_render_callback_data() #6 *path*/public_html/wp-includes/class-wp-block.php(586): MBBlocks\Loader->MBBlocks\{closure}() #7 *path*/public_html/wp-includes/blocks.php(2359): WP_Block->render() #8 *path*/public_html/wp-includes/blocks.php(2431): render_block() #9 *path*/public_html/wp-includes/class-wp-hook.php(324): do_blocks() #10 *path*/public_html/wp-includes/plugin.php(205): WP_Hook->apply_filters() #11 *path*/public_html/wp-includes/post-template.php(256): apply_filters() #12 *path*/public_html/wp-content/themes/giethoornvillage/page.php(16): the_content() #13 *path*/public_html/wp-includes/template-loader.php(106): include('*homepath*/d...') #14 *path*/public_html/wp-blog-header.php(19): require_once('*homepath*/d...') #15 *path*/public_html/index.php(17): require('*homepath*/d...')November 7, 2025 at 3:13 PM #49294Key_Webdesign
ParticipantUpdate: with Meta Box AIO 3.3.1, the issue seems to be fixed!
November 11, 2025 at 3:17 AM #49311Galen
ParticipantUpdate to 3.3.1 broke it for me!
Also on Bricks but using MaxMegaMenu as well.
<div>An error of type E_ERROR was caused in line 110 of the file /home/webaccount/site.co.uk/wp-content/plugins/meta-box-aio/vendor/meta-box/meta-box-builder/src/ToggleStatusColumn.php. Error message: Uncaught TypeError: MBB\ToggleStatusColumn::remove_draft_state_label(): Argument #2 ($post) must be of type WP_Post, null given, called in /home/webaccount/site.co.uk/wp-includes/class-wp-hook.php on line 324 and defined in /home/webaccount/site.co.uk/wp-content/plugins/meta-box-aio/vendor/meta-box/meta-box-builder/src/ToggleStatusColumn.php:110 Stack trace: #0 /home/webaccount/site.co.uk/wp-includes/class-wp-hook.php(324): MBB\ToggleStatusColumn->remove_draft_state_label(Array, NULL) #1 /home/webaccount/site.co.uk/wp-includes/plugin.php(205): WP_Hook->apply_filters(Array, Array) #2 /home/webaccount/site.co.uk/wp-admin/includes/template.php(2350): apply_filters('display_post_st...', Array, NULL) #3 /home/webaccount/site.co.uk/wp-includes/nav-menu.php(879): get_post_states(NULL) #4 [internal function]: wp_setup_nav_menu_item(Object(WP_Post)) #5 /home/webaccount/site.co.uk/wp-includes/nav-menu.php(750): array_map('wp_setup_nav_me...', Array) #6 /home/webaccount/site.co.uk/wp-admin/nav-menus.php(670): wp_get_nav_menu_items(Object(WP_Term), Array) #7 {main} thrown</div> -
AuthorPosts
- You must be logged in to reply to this topic.