The Look and Feel category is supposed to be displayed before the category `content`. My guess is that when there's every single category, the `content` category is placed relative to the L&F category. When we're administrating a page, there is no entry in the look and feel category. Therefore, it's removed from the adminmenu and its 'displayBeforeCategory' is ignored. Therefore the `content` category is displayed in the order it comes in the tree by default, which happens to be AFTER the `other` category which is already in the tree by default.
The problem is with the fact that empty category are completely skipped AND they contain information to reorder the tree.
IMO this `displayBeforeCategory` category organization variable looks quite awful. If we did it today we probably would have used an order number for those.
Charpentier Lucas on 03/Nov/25 16:25
The Look and Feel category is supposed to be displayed before the category `content`. My guess is that when there's every single category, the `content` category is placed relative to the L&F category. When we're administrating a page, there is no entry in the look and feel category. Therefore, it's removed from the adminmenu and its 'displayBeforeCategory' is ignored. Therefore the `content` category is displayed in the order it comes in the tree by default, which happens to be AFTER the `other` category which is already in the tree by default.
The problem is with the fact that empty category are completely skipped AND they contain information to reorder the tree.
IMO this `displayBeforeCategory` category organization variable looks quite awful. If we did it today we probably would have used an order number for those just like it's done for the sections...
Charpentier Lucas on 03/Nov/25 16:33
In a word, we order categories in a linkedList. This data structure does not handle well being filtered :/
This message was sent by Atlassian Jira (v9.3.0#930000-sha1:287aeb6)
If image attachments aren't displayed, see this article.
