Meta Box

Hi Jay,

There's a bug in AIO. I'll update it tomorrow.

Hi Dragan,

Thanks a lot for your feedback and your suggested fix. I really appreciate that.

The latest version of Tabs had some updates for User profile and Settings page. Perhaps that break the code for the Term page. I'll check that again with my team mate and update the plugin asap.

Hi Lucjan,

We've just finished the feature and the code is available on Github. Please download and try it.

In a couple of days, I'll release a new version of Meta Box and write a tutorial about that.

To upload to custom folder, please use file field and set a new attribute upload_dir to the path of the new folder, like this:

array(
    'type' => 'file',
    'id' => 'f',
    'name' => 'File',
    'upload_dir' => '/path/to/your/folder/', // You can use ABSPATH . '/downloads/'
)

Hi Mark,

1) I started to do an extension for the Customizer 2 years ago. But the more developing, the more I realized that I had to rewrite the whole plugin to port it to JavaScript. So, I stopped. At the moment, the MB Settings Page only supports back end pages, not in the Customizer.

2) To make it compatible with Customizer, you need to set 'option_name' => "theme_mods_$themeslug" in your settings page. Then the MB Settings Page will save data into theme mods, which are used by the Customizer.

Hi David,

No, the plugin use $wpdb directly to add/update the data. Please use this:

global $wpdb;
$data = [
    'ID'      => $post_id,
    'field_1' => 'value_1',
    'field_2' => 'value_2',
];
$wpdb->insert( 'your_table', $data );

Please use this function:

$meta_box = rwmb_get_registry( 'meta_box' )->get( 'YOUR_META_BOX_ID' );
$fields = $meta_box->fields;

Hi, thanks a lot for your feedback and debug. I'll check the bundled version in AIO and fix it asap.

Hmm, couldn't find anywhere the JSON value is stored.

However, I found something confusing in your code:

This part:

if( is_string($field['value']) && is_array(json_decode($field['value'], true)) ) {
        $array = json_decode( $field['value'] );
        $i = 0;
        foreach( $array as $value) {
          update_post_meta($post_id, '_property_' . $new_level . '_' . $field['key'], $value[$i]);
          $i++;
        }
      } else {...}

Here you check if $field['value'] is a json-string. But when you decode it with $array = json_decode( $field['value'] );, then $array will be an object! Not sure why the next foreach loop work.