Love all the progress I’m seeing so far, especially with the recent style updates in DP4.
I got my hopes up momentarily when I went to create a new field group and saw that there was a list of fields I could pick from when creating or editing it. Momentarily I hoped that this new interface meant that I could in fact assign the same field to multiple field groups.
Alas, once a field is assigned in one field group, it’s still unavailable to select for others. So, this behaviour is unchanged.
But whereas previously I would create a field group and then immediately start adding fields which would automatically be assigned to that field group, I now need to reverse my process and first create all of my fields, and then go back and create my field group and assign all those fields to it. Then later, if I need to add more fields, I need do the same thing again, all involving several steps and interface navigation.
This to me is more clicks for no gain. The process makes sense if field which can live inside multiple field groups, but not if things are status quo.
Hi Derek,
Thanks for the feedback, I recognized this in DP3, and updated the UI, but the changes didn’t make it into DP4.
An issue has be filed to make it work more like it did before in 2.x.
I original designed the UI for having custom fields independent of groups, and being able to be put into multiple groups or tied directly to a channel, however the underlying functionality isn’t going to be in 3, so I pulled the UI back.
An issue has be filed to make it work more like it did before in 2.x.
That’s a shame as I was looking forward to the prospect of sharing custom fields across groups. Helps reduce the number of custom fields to maintain and having 6 descriptions fields that essentially do the same thing has always seemed a bit messy in EE.
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.