Bug #96000

Match behaviour of folderTree.altElementBrowserMountPoints to pageTree

Added by Marco H 6 months ago.

Status:
New
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2021-11-16
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
10
PHP Version:
Tags:
foldertree pagetree mountpoint
Complexity:
Is Regression:
Sprint Focus:

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.

No data to display

Also available in: Atom PDF