Project

General

Profile

Actions

Feature #2971

closed

Workspace should use DB/file mount of BE user/group

Added by Sonja Schubert over 15 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Should have
Category:
Workspaces
Target version:
-
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

patch-2971.txt (6.04 KB) patch-2971.txt Sonja Schubert, 2009-03-25 15:31
patch-2971-2.txt (3.06 KB) patch-2971-2.txt Sonja Schubert, 2009-03-30 14:54
patch-2971-2.txt (3.06 KB) patch-2971-2.txt Sonja Schubert, 2009-03-30 14:54
Actions #3

Updated by Sonja Schubert over 14 years ago

  • Category changed from 408 to 447
  • Status changed from New to Accepted
Actions #4

Updated by Sonja Schubert over 14 years ago

  • Category changed from 447 to New Features
Actions #5

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

Actions #6

Updated by Sonja Schubert about 14 years ago

Behaviour without patch:

  1. create a normal backend user with a filemount and dbmount assigned
  2. create a workspace and add the created backend user as member and DO NOT add any dbmount or filemount to workspace record
  3. switch to workspace with the backend user logged in
  4. Problem: you have no filemounts
  5. Problem: you have no db mounts

Behaviour with patch:

  1. create a normal backend user with a filemount and dbmount assigned
  2. create a workspace and add the created backend user as member and DO NOT add any dbmount or filemount to workspace record
  3. switch to workspace with the backend user logged in
  4. Solution: you have your filemounts from be_user or be_group
  5. Solution: you have your db mounts from be_user or be_group
  6. 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
Actions #7

Updated by Steffen Ritter almost 14 years ago

  • Status changed from Accepted to Needs Feedback

i think this one is done with rfc 4302 committed? Right?

Actions #8

Updated by Sonja Schubert almost 14 years ago

  • Status changed from Needs Feedback to Resolved
Actions #9

Updated by Michael Stucki almost 11 years ago

  • Category changed from New Features to Workspaces
Actions #10

Updated by Michael Stucki almost 11 years ago

  • Project changed from 624 to TYPO3 Core
  • Category changed from Workspaces to Workspaces
Actions #11

Updated by Benni Mack about 6 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF