Bug #56990
closed
- Status changed from New to Needs Feedback
- Assignee set to Mathias Schreiber
Not sure if this behavior is intended.
It will for sure lead to some nasty JS issues.
What's the state of this issue?
- Status changed from Needs Feedback to Rejected
We discussed that in a group with UX people and also techs and architects and decided to not allow, nor "fix" this.
The issue is still valid.
I could not really follow the UX guys.
To know your user uid and to know the uids of the groups you are in and for what they are as an admin is IMO not usefull.
To not show normal mountpoints is okay, because you have normally speaking folder names, but user/group dirs are only numbers.
University sites have normally more than a handful groups. And for sure this could be optional.
I wonder if we all get your description wrong.
So I am an admin user and for whatever reason I also have BE groups.
You then want the FILE mounts of these groups to show up in filelist although you have full access already.
That's how we all understood the report.
The report is about this feature:
$GLOBALS['TYPO3_CONF_VARS']['BE']['userHomePath']
$GLOBALS['TYPO3_CONF_VARS']['BE']['groupHomePath']
Autom. mount points for users and groups matching an folder by uid.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by