Issue Bug New Orphaned

#96000Match behaviour of folderTree.altElementBrowserMountPoints to pageTree

Marco H 11/16/21, 17:17 updated 11/16/21, 17:17

Description

So I’ve run into the case that a user with access to a restricted pagetree wants to link to a page outside of his area.
I happily discovered that the option
@options.pageTree.altElementBrowserMountPoints@
lets me replace the defined dbmount with whatever I want.

If I don’t want to replace my defined dbmounts but instead want to append some, I can enable the following option
@options.pageTree.altElementBrowserMountPoints.append@

Both of this is great!

I then checked if the same exists for the foldertree (if someone wants to link to a file outside of his assigned file folder).

The option
@options.folderTree.altElementBrowserMountPoints@
exists! Great!
However, unlike the pageTree version, this one only appends filemounts, it doesn’t replace them.
The append option doesn’t exist (I tried to set options.folderTree.altElementBrowserMountPoints.append = 0)

What is the reasoning for this different behaviour?
I feel like the default behaviour for folderTree.altElementBrowserMountPoints should be “replace” and “folderTree.altElementBrowserMountPoints.append” should be added for those who want it.

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.

Fix this issue

Start the commit message of your patch with this. Add what the patch does, and the versions it goes to in "Releases:". How to create a patch

Commit message
[BUGFIX] Match behaviour of folderTree.altElementBrowserMountPoints to pageTree Resolves: #96000 Releases: main