Meta Box

Hello,

I understand that you want to display the question value in the group title. Please check if you have added the field ID prefix in the field group settings.

If you want to display question value in the frontend, please follow the documentation https://docs.metabox.io/extensions/meta-box-group/#getting-sub-field-values

Hello,

In the case of using Bricks Builder, please reach out to them if you have any issues with installation, configuration, compatibility, or usage.
Refer to our support policy https://metabox.io/support/topic/support-policy/

Hello,

The default meta box Category of WordPress doesn't have that option. You can use the field taxonomy, it sets the post term like the meta box Category.

Hello,

There is an issue with the plugin MB Revisions and the development team is working on it. It will be fixed in the next update of the plugin.

Thank you.

Hello Mauro,

This issue has been added to our development queue and will be fixed in future updates of the plugin. Thank you.

Hello Luca,

If you want to translate the custom field value with WPML, please follow the documentation https://metabox.io/translate-custom-fields-with-wpml/

If you edit the page in the second language and do not see the custom field, I think you can try to set the post type meta-box in WPML > Settings to Not translatable to fix the issue. If it doesn't work, I recommend contacting WPML support to get more information.

Hello,

You might need to use the code to check the block or classic editor is available when editing the post and registering the meta box. For example:

if( code_check_editor_here ) {
    add_filter( 'rwmb_meta_boxes', 'your_prefix_function_name' );
}

function your_prefix_function_name( $meta_boxes ) {
    $prefix = '';

    $meta_boxes[] = [
        ...
    ];

    return $meta_boxes;
}

Hello,

You are correct, I can reproduce the issue 2 meta boxes with two plugins Meta Box and MB Relationships. But not the error message. It works if you use the plugin Meta Box AIO.
I've escalated this issue to the development team to fix it in the next update.

Thank you.