#106024For usergroups with page permission "show" the option "Mount as treeroot" is still available
Description
When I set the page permissions for a usergroup to only “show” there is still the option “Mount as treeroot” under “more options…” available. This is not good as normally the permission for a page is set to just “show” because you don’t want the user to change anything about the page. Especially the option “Mount as treeroot” can have fatal results.
I tried to disable this option via TS but I did not find anything neither in the documentation nor by Googling.
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
History 7
-
Garvin Hicking commented and changed status
NewNeeds Feedback <span data-processor="relativetime" data-value="2025-01-30T07:26:14+00:00" > 01/30/25, 07:26 </span> -
Michael Perlbach commented <span data-processor="relativetime" data-value="2025-01-30T10:05:54+00:00" > 01/30/25, 10:05 </span>
When a non-admin user changes the page he is allowed to only show to tree root it can destroy your navigation structure.
However, I could solve this problem with setting the user tsconfig:
options.contextMenu.table.pages.tree.disableItems = newWizard, pagesSort, pagesNewMultiple, openListModule, mountAsTreeRoot, exportT3d, importT3d, hideInMenus, showInMenus, permissionsBut I think the option “Mount as treeroot” should by default not be available for users who only have show permission on a page.
-
Garvin Hicking commented <span data-processor="relativetime" data-value="2025-01-30T10:56:15+00:00" > 01/30/25, 10:56 </span>
Since front end navigation should not be coupled to mount options from a backend user (only specific to himself.) This should not be a real issue, did you check if your front end navigation is really affected by this?
-
Michael Perlbach commented <span data-processor="relativetime" data-value="2025-01-30T11:01:29+00:00" > 01/30/25, 11:01 </span>
To my shame I must admit: I did not.
But I read in some forum that someone destroyed his navigation structure by inadvertently setting the wrong page as tree root.
And I found this plausible. I am in stress currently – but if I have a little more peace and I still remember this problem I might test it. -
Garvin Hicking commented <span data-processor="relativetime" data-value="2025-01-30T11:06:21+00:00" > 01/30/25, 11:06 </span>
Sure! I believe, this should likely only happen, if a tree is really mounted, and not via your backend users preferences. Would you be fine with closing this issue so far?
-
Michael Perlbach commented <span data-processor="relativetime" data-value="2025-01-30T11:58:07+00:00" > 01/30/25, 11:58 </span>
yes, close it.
-
Garvin Hicking changed status
Needs FeedbackClosed <span data-processor="relativetime" data-value="2025-01-30T13:15:22+00:00" > 01/30/25, 13:15 </span>
Thanks for your report – could you maybe elaborate on the fatal results this causes? As I understand, this option should only apply user-specific and temporary?