Symphony.

As I said here, it would be useful to be able to expand/collapse fields in the section editor. There are already two extensions providing this feature, but none of them actually makes use of the collapsible plugin.

In my own fork of Symphony, I committed a patch that lets you expand/collapse instances of the fields duplicator without interfere with the orderable plugin.

This is done by assigning two different handles values at the above plugins. Collapsible uses “.header span” (i.e. the field type), while orderable uses “.header” (the whole bar). An alternative solution could be to invert the handles, but it would break backward compatibility with releases lower than 2.2, thus I thought it was better to act discreet.

This problem is solved quite elegantly in Symphony 3. If we have two workng extensions providing the needed feature, why should it be implemented into the 2.x branch?

The question is: are we just fixing up the last shortcomings of 2.x to switch to 3.x development as soon as possible or are we working on a long term transition from the 2.x to the 3.x code base?

This problem is solved quite elegantly in Symphony 3. If we have two workng extensions providing the needed feature, why should it be implemented into the 2.x branch?

Well… perhaps I swim against the stream, but I think that an extension should extend the system with features that you can live without. After two years I still see people scrolling the mouse whell to re-order fields, which is not good from an usability point of view. To me this is not an extra feature, but a lack in the interface. That’s why I think it should not be provided with an extension.

Moreover, there is a collapsible plugin that doesn’t seem to be used anywhere in the interface (but perhaps I’m wrong). Plus, extensions can’t make use of that plugin to modify duplicators that are already initialized because it’s something that happens at instantiation time.

Given that this change is unobtrusive and doesn’t alter the duplicator’s behaviour, I suggest to make it a core features. If you don’t need it, you won’t even see it.