Actions
Feature #2971
closedWorkspace should use DB/file mount of BE user/group
Start date:
2009-03-25
Due date:
% Done:
100%
Estimated time:
PHP Version:
Tags:
Complexity:
Sprint Focus:
Description
It should be possible to configure the workspace, so not the DB mount from the sys_workspace configuration is used. Instead of this, the DB mount of user/group should be used.
This make it possible to have several backend user and groups with different DB mounts, which uses the same workspace. This prevent a lot of workspace configurations for a difficult permission structure.
Solution:
Two new checkboxes in the sys_workspace configuration form to decide if the user/group DB / file mount should be used
Files
Updated by Sonja Schubert over 15 years ago
- File patch-2971.txt patch-2971.txt added
Updated by Sonja Schubert over 15 years ago
- File patch-2971-2.txt patch-2971-2.txt added
Updated by Sonja Schubert almost 15 years ago
- Category changed from 408 to 447
- Status changed from New to Accepted
Updated by Sonja Schubert over 14 years ago
- Category changed from 447 to New Features
Updated by Benni Mack about 14 years ago
I put it in the core list.
Mantis #4203: http://bugs.typo3.org/view.php?id=4203
Updated by Sonja Schubert about 14 years ago
Behaviour without patch:
- create a normal backend user with a filemount and dbmount assigned
- create a workspace and add the created backend user as member and DO NOT add any dbmount or filemount to workspace record
- switch to workspace with the backend user logged in
- Problem: you have no filemounts
- Problem: you have no db mounts
Behaviour with patch:
- create a normal backend user with a filemount and dbmount assigned
- create a workspace and add the created backend user as member and DO NOT add any dbmount or filemount to workspace record
- switch to workspace with the backend user logged in
- Solution: you have your filemounts from be_user or be_group
- Solution: you have your db mounts from be_user or be_group
- if you DO add a filemount or dbmount to workspace record, then they'r merged with your permissions set in be_user or be_group, if you have rights you see them in workspace mode, if not you see them not
Updated by Steffen Ritter about 14 years ago
- Status changed from Accepted to Needs Feedback
i think this one is done with rfc 4302 committed? Right?
Updated by Sonja Schubert almost 14 years ago
- Status changed from Needs Feedback to Resolved
Updated by Michael Stucki almost 11 years ago
- Category changed from New Features to Workspaces
Updated by Michael Stucki almost 11 years ago
- Project changed from 624 to TYPO3 Core
- Category changed from Workspaces to Workspaces
Actions