Bug #13910
closed
DB mounts not checked recursively for BE user
Added by Malte Koitka over 13 years ago.
Updated almost 11 years ago.
Description
The root page is selected as DB mount for the workspace. But there also exists a restricted user, who must not operate on root level. Thus this user gets a subpage of root as its own DB mount.
Although with the root page set as starting point for the workspace, the restricted user is not able to see the subpage tree in the workspace.
It only does work when you add the subpage to the workspaces DB mounts.
Great work so far. Keep it up!
- Status changed from New to Needs Feedback
Dear Malte,
Thank you for this issue. I think it's not a bug, but a configuration failure. Why do you set the root page as DB mount in the workspace configuration? I think, this is not needed. As described in the documentation the field DB mount in the workspace configuration is only needed if you want to reduce the DB mounts for the workspace. If you leave this field empty it automatically uses the DB mount permissions of the logged in be_user/be_group.
Could you try it and give feedback if this works for you?
Kind regards,
Sonja
Hi Sonja,
I'm sorry. You're indeed right.
In my case there's no need to set a mountpoint for the workspace. In general I think documentations are a nice thing to have and a must-read.
Thanks for your fast answer.
Best regards
Malte
- Status changed from Needs Feedback to Closed
- Target version changed from 4.5.3 to 4.5.3
- Target version changed from 4.5.3 to 4.5.3
- Category changed from Bugs to Workspaces
- Project changed from 624 to TYPO3 Core
- Category changed from Workspaces to Workspaces
- Target version deleted (
4.5.3)
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by