Meta Box

AIO 3.13.1: MB Term Meta triggers HTTP 500 with an older bundled core

Support › Meta Box AIO › AIO 3.13.1: MB Term Meta triggers HTTP 500 with an older bundled core

Viewing 1 post (of 1 total)
  • Author
    Posts
  • October 23, 2026 at 2:18 AM #50238
    contact@cesarpinto.com[email protected]
    Participant

    Hi guys,

    Meta Box AIO 3.13.1 causes an HTTP 500 on our membership with ActiveMember360 4.3.9 and PHP 8.3.36.

    The captured error is:
    Class RWMB_Block_Bindings_Registry not found

    It starts here:
    wp-content/plugins/meta-box-aio/vendor/meta-box/mb-term-meta/mb-term-meta.php:46

    The class_exists check for MetaBox\Integrations\BlockBindings\Source succeeds through AIO's autoloader. However, the active core is Meta Box 5.9.1, loaded by ActiveMember360.

    The resulting rwmb_get_registry('block_bindings') call reaches:
    wp-content/plugins/activemember360/libs/meta-box/framework/inc/functions.php:291

    That older function constructs the missing legacy class name instead of using the newer registry mapping.

    Could you make the Block Bindings check account for the core actually running, and advise on a compatible fix?

    I'm also asking ActiveMember360 to review its bundled core. AIO is disabled for now, and I have the captured trace available.

    Thanks,
    Cesar

  • Author
    Posts
Viewing 1 post (of 1 total)
  • You must be logged in to reply to this topic.