Meta Box

Thats great news!

Thanks for letting me know 🙂

Hi Peter,
thanks for keeping me updated. I look forward to the fix ASAP... getting far more bot registrations than I would like!

Cheers 🙂

Hi Peter,
thanks for getting back to me. So what are the existing "script handle names" then? These...

function metabox_remove_styles() {

  wp_dequeue_style( 'rwmb' );
  wp_dequeue_style( 'rwmb-input' );
  wp_dequeue_style( 'rwmb-input-list' );
  wp_dequeue_style( 'rwmb-select' );

}
add_action( 'rwmb_enqueue_scripts', 'metabox_remove_styles', 99 );

Hi there,
is there any news on this fix? Or when this is likely to be addressed?

Cheers 🙂

Hi Peter,
perfect! Not sure how I missed that...doh!

Thanks.

Hi Peter,
thanks for getting back to me. After further investigation and testing, It looks like this issue was a false positive and related to a transient. The switch works as expected with the 'std' => true, attribute. My bad! This can be closed.

Hi Peter,
appreciate the image reference, but I don't use the Metabox builder UI. I create my custom fields with PHP. I assume that the equivalent in my custom field declaration is simply 'required' => true? Which is what I am using an the file_upload custom field like this:

[
'name'             => __( 'Image', 'text_domain' ),
'id'               => '_thumbnail_id',
'type'             => 'file_upload',
'max_file_size'    => '2mb',
'max_file_uploads' => 1,
'required'         => true,
],

This does not work as I have previously described? Or have I misunderstood your explanation?

Hi Peter,
thanks for the guidance. After some further debugging, turns out the unserialize() issue I was experiencing originated from a completely unrelated function. My apologies.