Meta Box

Seeming the same issue with MetaBox 5.10.0 and Meta Box AIO 1.30.0. Tried using MB Group 1.4.0, but still same error with when updating group field via rwmb_set_meta(), which has been running flawlessly for well over a year until 5.10.0 update. It just wipes out the group field entirely anytime try to update via rwmb_set_meta()

Rolled back to 5.9.10 solves the problem.

I second this, @netalys. Being able to do something like this would be very helpful:

$result = rwmb_set_meta( $post_id, $field_id, $value );

if ($result === true) {
    // update successfully
} else {
    // update failed
}

Yes, having the same problem, but relatively new to MB so haven't ever upgraded. Posting with Postman shows updated info in the response, but updates aren't written to DB when using REST.

Original value:

{
    "meta_box": {
        "file_key": "123123",
        "file_name": "Basement"
    }
}

What I'm posting to CPT endpoint: domain.local/wp-json/wp/v2/cpt_slug/428

{
    "meta_box": {
        "file_key": "123123",
        "file_name": "Basement NEW"
    }
}

What POST response shows: (abbreviated for clarity)

{
    "meta_box": {
        "file_key": "123123",
        "file_name": "Basement NEW"
    }
}

What a GET request to same endpoint shows (domain.local/wp-json/wp/v2/cpt_slug/428)

{
    "meta_box": {
        "file_key": "123123",
        "file_name": "Basement"
    }
}

Changes aren't being stored when using custom table. If I switch to just using default storage these EXACT same REST calls work exactly as expected. This is causing all kinds of heartburn. Is this a bug or is there some other setting that needs to be set? Making changes through WP admin works fine and data is written to custom table just fine. Problem is my use case relies HEAVILY on REST.