User tests: Successful: Unsuccessful:
The new field groups (#13019) are created globally per component. It means when a component has more than one context, it is not possible to create groups per context. This pr solves that and allows to create groups per context of fields. A field belongs to a context and with this pr the group as well.
It fixes also an issue where a second asset per group is created when a permission has changed.
After a fresh installation, create groups, assign fields to them. All should work as before.
A fresh installation is needed as the database schema has changed..
Status | New | ⇒ | Pending |
Category | ⇒ | SQL Administration com_admin Postgresql com_contact com_content com_fields com_users Modules Installation JavaScript |
Labels |
Added:
?
|
I have tested this item
I have tested this item
Test OK.
Amazing progress!
Status | Pending | ⇒ | Ready to Commit |
RTC based on 2 successful tests
Milestone |
Added: |
Thanks to the testers!
Status | Ready to Commit | ⇒ | Fixed in Code Base |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2016-12-18 20:18:01 |
Closed_By | ⇒ | rdeutz | |
Labels |
Added:
?
|
Some background to explain why I chose "extension" instead of "context" for the groups:
So imho we should change all "context" to "extension" but Allon disagrees with me here?