#91914Nested filemounts wrongly expand/collapse
Description
I have the following filemount structure:
+ rootlevel (readonly for all groups) + shared dir (writeable for all) + group 1 (writable for the according group) + group 2 (like group 1) + etc.
This results in 3 mounts for each group:
rootlevel, shared dir, “write protected” mount
Imagine this as some kind of simple shared directory layout, so files can be made available read only for other groups and to have a shared working directory. They are all set up in a non-public storage and not accessible from the outside.
We could of course add all group level directories as seperate mounts, but this kind of blows up the list of mounts in the file module with a growing number of groups.
+ shared dir + group 1 + rootlevel
The tree already recognizes the write possibility for subfolders and does not add the lock icon to subfolders in rootlevel. But when folders are clicked to expand, not the ones that were clicked are expanded, but the first ones in the whole tree, same goes for collapsing.
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
History 1
-
Benni Mack commented and changed status
NewClosed 01/18/26, 10:12
Hey Andreas,
thanks for the report. We’ve rebuilt the tree (again) in v11 and v13 – I cannot reproduce this in v14 anymore, and I’m very confident this has been solved – if not, reach out to me and I will re-open the issue.