6.3.x sorting hierarchy
14 views
Skip to first unread message
Patrik Savior
Aug 29, 2025, 8:45:48 AMAug 29
to Magnolia User Mailing List
I am trying to update to the latest 6.3 versions (currently using 6.2.63). I've noticed one issue when using the JCR browser app/any app in general.
In the 6.2.x versions, when I sort a workspace, eg. by Last change -> the nodes are rendered and sorted as a hierarchy. Nodes remain unfolded, unfolding them allows actions on nodes and child nodes.
With the 6.3.x (tried 6.3.0 and the latest 6.3.14 version) this no longer works. If i sort a workspace, then the nodes are no longer rendered as a hierarchy and instead it just renders all nodes. The nodes are sorted. When trying to perform actions on a selected node when sorting is applied it does not exactly work - the node remains unfolded, so for example adding a property is not possible. If I reset the sorting and I find the node, actions are possible without any issues.
Is this the new behaviour, or can this be configured somehow? Thanks
In the 6.2.x versions, when I sort a workspace, eg. by Last change -> the nodes are rendered and sorted as a hierarchy. Nodes remain unfolded, unfolding them allows actions on nodes and child nodes.
With the 6.3.x (tried 6.3.0 and the latest 6.3.14 version) this no longer works. If i sort a workspace, then the nodes are no longer rendered as a hierarchy and instead it just renders all nodes. The nodes are sorted. When trying to perform actions on a selected node when sorting is applied it does not exactly work - the node remains unfolded, so for example adding a property is not possible. If I reset the sorting and I find the node, actions are possible without any issues.
Is this the new behaviour, or can this be configured somehow? Thanks
Reply all
Reply to author
Forward
0 new messages