Feature #16554

Workspace DB / filemounts should narrow down the users' mounts

Added by Martin Kutschker almost 13 years ago. Updated 11 months ago.

Status:
Closed
Priority:
Should have
Assignee:
Category:
Workspaces
Target version:
-
Start date:
2006-09-12
Due date:
% Done:

0%

PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

Currently there is only an option to add specific filemounts to the WS. This breaks all user/usergroup based filemount permissions.

So I suggest three options:

a) only WS filemounts
b) intersection of WS filemounts and user filemounts
c) only user filmounts

a) is the current state, b) is a meaningful extension that takes user filmounts into account but adds WS restrictions and c) is simply the state without any WS options which may come in handy.

(issue imported from #M4203)

bug4203.diff View (4.17 KB) Administrator Admin, 2008-04-07 21:57

bug4203.txt View (1.04 KB) Administrator Admin, 2008-04-07 23:12

ws_userauth_45.patch View (11.7 KB) Administrator Admin, 2010-09-17 17:47

ws_userauth_44.patch View (11.7 KB) Administrator Admin, 2010-09-17 17:48

ws_userauth_43.patch View (11.8 KB) Administrator Admin, 2010-09-17 17:48


Related issues

Related to TYPO3 Core - Bug #24098: Workspaces: Admin users don't have filemounts in workspace, if they haven't chosen one Closed 2010-11-17
Duplicated by TYPO3 Core - Bug #22097: Workspace filemounts don't respect user filemounts Closed 2010-02-10
Duplicated by TYPO3 Core - Feature #22249: Custom Workspaces allow users file mounts Closed 2010-03-07

History

#1 Updated by Andreas Wolf almost 13 years ago

I would also add an option d) Combine workspace- and user-filemounts - so if you have filemounts A and B in the workspace and B and C in the user's options, the user would have access to A, B and C in the workspace.

The only problem arising could be that no filemounts can be set for the live-workspace, so you would have to add the filemounts to the user's options to have them in the live-workspace.

Edit: And I would also do something similar to this for the DB-mounts - as far as I know, their current behaviour is the same as with filemounts.

#2 Updated by Christian Hennecke almost 12 years ago

I would also like to have an option to access user and group home directories.that are automatically mounted in the Live workspace.

#3 Updated by Cedric Spindler over 11 years ago

The current concept seems to be like this:
Every group has its own workspace and within the workspace the file and page mounts are defined. The file an page mounts of the group (user) itself is just recognized within the "live system".

The problem with this concept is, that you will get multiple workspaces for the same page if you have a more complex restrictive group setup.

Imagine you have the section "Solations" with a subsection "Open Source", Further you have users which have to access the whole solutions tree, and some users which should only see the "Open Source" tree.

You don't want to manage two workspaces for these sections (Solutions and Open Source) only for denying the Open Source guys to access the whole "Solution" tree, because there is a Section "Microsoft" within it ;-).

The concept should be like this:
The workspace should recognize the page and filemounts as well as the group and user permissions that are configured for the "live system". It would allow to simplify more complex restrictive group setup.

#4 Updated by Alexey Boriskin over 11 years ago

I have added the patch. Patch do the following.
At first, it saves default old behaviour if other is not explicitly set.
Then, it introduce new user TS Config option "options.folderTree.WSFilemountsMode".
That option can be one of 4 values:
1) ignoreUser. the same behaviour as before and as option is not set at all: user filemounts are ignored.
2) ignoreWS: new feature. In that case, workspace settings are ignored and filemounts come from user and group permissions.
3) combine: new feature. In that case, workspace filemounts are combined with user filemounts.
4) intersect: new feature. In that case, user have access only for those filemounts, that are selected in workspace settings AND also accessible for that user in user settings.

#5 Updated by Alexey Boriskin over 11 years ago

I've also added .txt file which describes new TSConfig option.

#6 Updated by Benni Mack almost 9 years ago

According to the workspaces team, this feature will be implemented without an option:

http://news.typo3.org/news/article/bringing-workspaces-up-to-speed/

This means, that selecting a filemount / db mount in a workspace will narrow down the existing list of a users' mount.

#7 Updated by Benni Mack almost 9 years ago

Also see http://forge.typo3.org/issues/2971

The attached patches solve the issues, and are sent to the core list.

#8 Updated by Benni Mack over 8 years ago

committed v2 to trunk (rev. 9427)

#9 Updated by Michael Stucki over 5 years ago

  • Category changed from Miscellaneous to Workspaces

#10 Updated by Michael Stucki over 5 years ago

  • Project changed from Workspaces & Versioning to TYPO3 Core
  • Category changed from Workspaces to Workspaces
  • Target version deleted (0)

#11 Updated by Benni Mack 11 months ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF