Meta Box

It's been a long time, but just want to let you know that the search functionality is done. Please just update the plugin.

Hi, is that really admin-columns or you mistyped? It should be admin_columns, underscore.

Yes, you can always do that with class attribute of the field. Just add a custom CSS class to the "5-columns" field and change its width with CSS. It's kind of a hack while waiting for a better solution that we're working on.

We just updated the Columns extension yesterday with a better check for total columns (less than or greater than 12, it will close the div). But if you use with tabs, you still need to make sure total columns in each row equals to 12. Please update.

Regarding the new syntax, I was thinking about something advanced that can offer you more flexibility. But after looking at that, I see the change is only the fields parameter (the class as I replied can be achieved via class attribute). And with the support of Group extension, you can do that easily, including the nested columns.

Here is what you can do with Groups (the syntax is very similar):

'fields' => array(
    array(
        'type' => 'group', // A wrapper group
        'id' => 'wrapper',
        'fields' => array(
            array(
                'id' => 'name',
                'type' => 'text',
                'columns' => 4
            ),
            array(
                'id' => 'subgroup',
                'type' => 'group',
                'columns' => 8,
                'fields' => array(), // Array of other sub-sub fields
            )
        ),
    ),
),

Hi, I don't want to much nested arrays. In case sub-fields in groups are organized in columns, there will be a nightmare of nested nested arrays.

After reviewing the code, I think we can still achieve everything by this code:

fields => array(
    array(
        'columns' => 4,
        'class'   => 'custom-column-class',
    ),
),

We have class attribute for fields, so let's use it instead of creating another attribute.

Thanks a lot. Just fixed the bug with the editor!

Cheers
Anh

Hi,

I guess the problem is when you hook send_mails_on_publish. Probably it's hook too soon, sooner when Meta Box updates post meta.

Currently Meta Box uses save_post_{$post_type} with priority = 10 to save post meta. You should hook after that (at save_post or at the same hook with higher priority).

Looking at the function params, I think you're using transition_post_status. It's fired in wp_transition_post_status function that runs before save_post_* hook.