Strange issue with tabs + columns

Hi Jackky,

Your idea about column class is nice. Will think about it. The suggested syntax I think will be problematic if we use with groups. So let’s just keep it as it is.

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.

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
            )
        ),
    ),
),