Meta Box

Hello Yasmine,

Yes, we change post_id to object_id for the frontend form from Meta Box AIO 1.31.0 to support the compatibility between the custom model and frontend form. That means you can submit a custom model entry from frontend.
You can read more about this update in the changelog https://metabox.io/plugins/meta-box-aio/changelog/
and documentation https://docs.metabox.io/extensions/mb-frontend-submission/#adding-the-submission-form

Hello,

If you have two or more custom tables for each field group, you can add all field group IDs to the frontend shortcode and save the field values to all custom tables when submitting or editing the post.

Hello,

Is there any chance you read my request above? Please export the field group to a JSON file and share it here, I will help you check the field settings.

Hello Nick,

I'm afraid that it isn't possible. As I mentioned above, the column name in the custom table must match the field ID when you register/create the custom field. If you want to save data to separate custom table tables with one frontend form, you can create more field groups and add their IDs to the frontend shortcode.

[mb_frontend_form id='field-group_id_1,field-group_id_2,field-group_id_3' post_fields='title,content']

Hello,

I understand the issue. It is related to this topic https://support.metabox.io/topic/dynamically-populate-the-options-of-a-select-custom-field-base-on-global-cf/

you need to use the WordPress function get_option() to get the settings page value (like the theme option) when creating the custom field. At this point, the helper function rwmb_meta() doesn't work.

Here is an example

function test_function() {
    $options = get_option( 'custom-options' );
    $value_a = $options['test_a'];

    $optionsA = array(
        '1' => 'Apple',
        '2' => 'Orange'
    );

    $optionsB = array(
        '3' => 'Cat',
        '4' => 'Dog'
    );

    return $value_a ? $optionsA : $optionsB;
}

If you use the builder, you will need to re-update the field group to update the choice for the field test_b.

Hello,

Please ensure the option name is added to the helper function, and the separator should be underscore instead of dash. For example custom_options

$value_a = rwmb_meta( 'test_A', array( 'object_type' => 'setting' ), 'custom_options' );

Following the documentation https://docs.metabox.io/extensions/mb-settings-page/#using-code

After you save the field test_a value, the $optionsA will be returned.

Hello Nick,

I create a custom field type following the documentation https://docs.metabox.io/creating-new-field-types/

and I can use the jQuery validation, frontend filter validation properly. Here is the example code:

add_filter( 'rwmb_meta_boxes', function ( $meta_boxes ) {
    $meta_boxes[] = [
        'title'      => 'Profile',
        'id'         => 'post-profile',
        'post_types' => 'post',
        'fields'     => [
            [
                'name' => 'Hotline',
                'id'   => 'hotline',
                'type' => 'phone',
                
            ],
        ],
        'validation' => [
            'rules'  => [
                'hotline' => [
                    'required'  => true,
                    'minlength' => 7,
                ],
                // Rules for other fields
            ],
            'messages' => [
                'hotline' => [
                    'required'  => 'hotline is required',
                    'minlength' => 'hotline must be at least 7 characters',
                ],
                // Error messages for other fields
            ],
        ],
    ];

    return $meta_boxes;
} );

add_filter( 'rwmb_frontend_validate', function( $validate, $config ) {
    // Check if users have selected files for an image upload field.
    if ( empty( $_POST['hotline'] ) ) {
        $validate = 'Please add a phone number';
    }
    return $validate;
}, 10, 2 );