In umbraco 8, we have a doctype setup where Homepage,GeneralPage etc inherits from Page in the hierarchy. This is so the Page doctype can have groups/properties specified that all child doctypes automatically have.
However, despite the order of the groups being A->B->C on Homepage doctype, the content node accordions shows the Page groups first and then the Homepage groups i.e. it doesn’t honour the group order specified/displayed on the Homepage doctype (which is Homepage groups and then the inherited groups from Page).
does anyone know if this is planned to be core functionality? it seems like a regression to now show everything to a content editor rather than in tabs (logical groupings) like umbraco 7could, or at least as collapsed accordians/groups in umbraco 8. thanks
a package is good but it becomes just another external factor to consider during upgrades etc so always good to avoid if possible :)
accordion order problem in umbraco 8?
Hi
In umbraco 8, we have a doctype setup where Homepage,GeneralPage etc inherits from Page in the hierarchy. This is so the Page doctype can have groups/properties specified that all child doctypes automatically have. However, despite the order of the groups being A->B->C on Homepage doctype, the content node accordions shows the Page groups first and then the Homepage groups i.e. it doesn’t honour the group order specified/displayed on the Homepage doctype (which is Homepage groups and then the inherited groups from Page).
Is this a known bug?
thanks
Fixed by changing the group sort order from the default i.e. 10 instead of 0
btw any way to collapse the accordions/groups?
There is a community package to collapse - https://our.umbraco.com/packages/backoffice-extensions/u8-collapse/
thanks Matthew :)
does anyone know if this is planned to be core functionality? it seems like a regression to now show everything to a content editor rather than in tabs (logical groupings) like umbraco 7could, or at least as collapsed accordians/groups in umbraco 8. thanks
a package is good but it becomes just another external factor to consider during upgrades etc so always good to avoid if possible :)
is working on a reply...