Version 5.10.16 – 2025-11-05 not working with WPML sites

Support Meta Box AIO Version 5.10.16 – 2025-11-05 not working with WPML sites

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #49284
    TobiasTobias
    Participant

    The version 5.10.16 – 2025-11-05 does not work with WPML sites and bricksbuilder.

    [06-Nov-2025 10:51:24 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the meta-box-aio domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information.

    "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."

    Going back to version 5.10.15 solved the issue.

    #49287
    PeterPeter
    Moderator

    Hello Tobias,

    Thanks for the feedback.

    Do you know steps to reproduce the issue from scratch? I test with some fields but don't see the error on my site.

    #49288
    TobiasTobias
    Participant

    Just after the update to version 5.10.16 – 2025-11-05 some parts like a CPT template in Bricksbuilder didn't work. And you could not access the parts of the website that used this template. I could not open the template in the bricksbuilder as well. https://share.zight.com/rRuxX9w4

    #49289
    Key_WebdesignKey_Webdesign
    Participant

    Yes, I got the same problem and error with Meta Box AIO.
    I just went back to a previous version because of this.

    #49297
    PeterPeter
    Moderator

    Hello,

    Please update Meta Box AIO to the new version 3.3.1 to fix the issue.

    Thank you.

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