Uncaught TypeError: stripslashes()

Support Meta Box AIO Uncaught TypeError: stripslashes()

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #49370
    FizzPop MediaFizzPop Media
    Participant

    I am running AIO 3.3.2 on two instances.
    When I imported field groups, posts and settings pages it appears to work correctly.
    However, now when I make changes to the custom fields on the site where I imported the data, I get a modal that says:

    <p>There has been a critical error on this website. </p> <p> <a
    href="https://wordpress.org/documentation/article/faq-
    troubleshooting/">Learn more about troubleshooting WordPress. </
    a></p>

    When I review the debug log, I receive this error:
    `
    [18-Nov-2025 15:46:47 UTC] PHP Fatal error: Uncaught TypeError: stripslashes(): Argument #1 ($string) must be of type string, array given in /var/www/public_html/wp-content/plugins/meta-box-aio/vendor/wpmetabox/mbb-parser/src/Parsers/Base.php:195
    Stack trace:
    #0 /var/www/public_html/wp-content/plugins/meta-box-aio/vendor/wpmetabox/mbb-parser/src/Parsers/Base.php(195): stripslashes(Array)
    #1 /var/www/public_html/wp-content/plugins/meta-box-aio/vendor/wpmetabox/mbb-parser/src/Parsers/Base.php(120): MBBParser\Parsers\Base->parse_json_dot_notations(Array)
    #2 /var/www/public_html/wp-content/plugins/meta-box-aio/vendor/wpmetabox/mbb-parser/src/Parsers/Field.php(78): MBBParser\Parsers\Base->parse_array_attributes('options')
    #3 /var/www/public_html/wp-content/plugins/meta-box-aio/vendor/wpmetabox/mbb-parser/src/Parsers/MetaBox.php(69): MBBParser\Parsers\Field->parse()
    #4 [internal function]: MBBParser\Parsers\MetaBox->parse_field(Array, 1)
    #5 /var/www/public_html/wp-content/plugins/meta-box-aio/vendor/wpmetabox/mbb-parser/src/Parsers/MetaBox.php(63): array_walk(Array, Array)
    #6 /var/www/public_html/wp-content/plugins/meta-box-aio/vendor/wpmetabox/mbb-parser/src/Parsers/MetaBox.php(79): MBBParser\Parsers\MetaBox->parse_fields(Array)
    #7 [internal function]: MBBParser\Parsers\MetaBox->parse_field(Array, 0)
    #8 /var/www/public_html/wp-content/plugins/meta-box-aio/vendor/wpmetabox/mbb-parser/src/Parsers/MetaBox.php(63): array_walk(Array, Array)
    #9 /var/www/public_html/wp-content/plugins/meta-box-aio/vendor/wpmetabox/mbb-parser/src/Parsers/MetaBox.php(23): MBBParser\Parsers\MetaBox->parse_fields(Array)
    #10 /var/www/public_html/wp-content/plugins/meta-box-aio/vendor/meta-box/meta-box-builder/src/RestApi/Save.php(99): MBBParser\Parsers\MetaBox->parse()
    #11 /var/www/public_html/wp-includes/rest-api/class-wp-rest-server.php(1292): MBB\RestApi\Save->save(Object(WP_REST_Request))
    #12 /var/www/public_html/wp-includes/rest-api/class-wp-rest-server.php(1125): WP_REST_Server->respond_to_request(Object(WP_REST_Request), '/mbb/save', Array, NULL)
    #13 /var/www/public_html/wp-includes/rest-api/class-wp-rest-server.php(439): WP_REST_Server->dispatch(Object(WP_REST_Request))
    #14 /var/www/public_html/wp-includes/rest-api.php(459): WP_REST_Server->serve_request('/mbb/save')
    #15 /var/www/public_html/wp-includes/class-wp-hook.php(324): rest_api_loaded(Object(WP))
    #16 /var/www/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters('', Array)
    #17 /var/www/public_html/wp-includes/plugin.php(565): WP_Hook->do_action(Array)
    #18 /var/www/public_html/wp-includes/class-wp.php(418): do_action_ref_array('parse_request', Array)
    #19 /var/www/public_html/wp-includes/class-wp.php(818): WP->parse_request('')
    #20 /var/www/public_html/wp-includes/functions.php(1342): WP->main('')
    #21 /var/www/public_html/wp-blog-header.php(16): wp()
    #22 /var/www/public_html/index.php(17): require('/var/www/c6fe5d...')
    #23 {main}
    thrown in /var/www/public_html/wp-content/plugins/meta-box-aio/vendor/wpmetabox/mbb-parser/src/Parsers/Base.php on line 195
    `

    Note that I can make the same changes on the original instance and it works fine.

    #49378
    PeterPeter
    Moderator

    Hello,

    Thanks for reaching out.

    It appears to be an issue with PHP 8+. Can you please downgrade the PHP version to 7.4 as a workaround to resolve the fatal error?

    #49380
    FizzPop MediaFizzPop Media
    Participant

    Reverting to PHP 7.4 does resolve the issue.
    However, the original site was built in PHP 8.3 and I can make the same changes on that site with no problem.

    Please advise.

    #49395
    PeterPeter
    Moderator

    Hello,

    I've escalated this issue to the development team to fix as soon as possible. You can keep using PHP 7.4 as a workaround in the meantime.

    Thank you.

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