Custom Metaboxes and Fields 0.9 released

Custom metaboxes and fields for WordPress

After a few months in the works I’m happy to announce Custom Metaboxes and Fields for WordPress version 0.9 is out and ready for consumption.

This is probably one of the large updates we have put out as it contains a lot¬†of fixes, tweaks, and even a few nice additions. Taken straight from the readme, here’s a list of what new with 0.9!

  • Cleaned up scripts being queued
  • Cleaned up and reorganized jQuery
  • Use $pagenow instead of custom $current_page
  • Fixed CSS, removed inline styles, now all in style.css
  • Fixed multicheck issues (issue #48)
  • Fixed jQuery UI datepicker CSS conflicting with WordPress UI elements
  • Fixed zeros not saving in fields
  • Fixed improper labels on radio and multicheck fields
  • Fixed fields not rendering properly when in sidebar
  • Fixed bug where datepicker triggers extra space after footer in Firefox
  • Added jQuery UI datepicker packaged with 3.3 core
  • Added date time combo picker
  • Added color picker
  • Added markdown file

Bill and Norcross have put in a lot of time for past releases, so in this release I tried to pick up the slack as I hadn’t been as active.

If you are using 0.8 you should be able to upgrade without any issues. However it’s worth noting this release is for WordPress 3.3+ – if you have not upgraded to 3.3 do not use 0.9.

What’s next

The next version is going to be a good one, so definitely keep an eye out. You can take a peak at the To-do in the readme to get an idea of what’s on our radar. Specifically here’s a few things that are a priority in 1.0:

  • Code cleanup. Since CMB has a rather large user base now, I figure we owe it to them to tidy up the code. This is going to be the #1 goal (but not the only) for 1.0.
  • Improve inline documentation. This goes hand-in-hand with the first point.
  • Move the jQuery datepicker and timepicker code inline and make each instance configurable with options passed through the array. This will allow multiple timepickers with different ranges, etc.
  • Add array option for placeholder value. Now that most modern browsers support this (html5) it should be a no-brainer.
  • Add array option for required elements. Like the previous point, this should be easy thanks to HTML5.
There are a few other features, if time permits, we are going to try to squeeze in as well – but the ones above will be the focus.

Special thanks to Gary Jones for some great feedback as well as tweaks, Bill for squashing a few bugs, and everyone who has been reporting bugs on GitHub.


  1. Moshe says

    Hi there,

    I was wondering if there is any update on version 1.0? In particular, i was wondering if you plan to include repeatable fields in 1.0. And even more particularly, I wanted to know if one could create repeatable groups of fields.

    Thanks and be well,


  2. says

    Hi Jared,
    first, congratulations you and your friend’s create a best plugin.

    When I created for my Custom Post Metaboxes types I call the function this way:

    register_post_type( ‘athletes’,
    ‘labels’ => array(
    ‘name’ => __(‘Athletes’,’rbmt’),
    ‘singular_name’ => __(‘Athlete’,’rbmt’),
    ‘add_new’ => __(‘New Athlete’,’rbmt’),
    ‘add_new_item’ => __(‘Add new Athlete’,’rbmt’),
    ‘edit_item’ => __(‘Edit athlete’,’rbmt’)
    ‘public’ => true,
    ‘publicly_queryable’ => true,
    ‘show_ui’ => true,
    ‘show_in_menu’ => true,
    ‘show_in_admin_bar’ => ”,
    ‘hierarchical’ => false,
    ‘supports’ => array( ‘title’, ‘editor’, ‘excerpt’, ‘thumbnail’ ),
    ‘rewrite’ => array( ‘slug’ => __(‘athlete’,’rbmt’), ‘with_front’ => true ),
    ‘menu_icon’ => get_stylesheet_directory_uri() . ‘/css/images/ico-athlete.png’,
    ‘menu_position’ => 6,
    ‘can_export’ => true,
    ‘has_archive’ => true
    ‘register_meta_box_cb’ => ‘esa_atlhete_metabox’

    But with your plugin I’m cannot do this same way because not working, how do I do to work your plugin with my CPT?

Leave A Reply