[TYPO3-hci] [TYPO3-dev] RFC: file mounts and work spaces

[Martin Kutschker]

Hi!

After some thought on file mounts and their limited usability with 
workspaces I have come to this conclusion:

A file mount may be in the state "read-only" during a BE session.

A read-only file mount is not visible in the directory tree of File>Filelist. *

A read-only file mount will appear in the element browser, but the upload 
and new file/folder options in the pop-up are hidden.

A file mount will become read-only when it is present in the user's file 
mounts (incl. file mounts inherited from user groups), but not listed in 
the file mounts of the workspace.

In DRAFT all file mounts (of the user) are read-only.

Reasoning:

I have played with the idea of adding complicated options ot mere or 
intersec user and WS file mounts with further options to mark some of them 
as read-only. The scheme mentionied above is easier to maintain and yet it 
is a logical extension of the current permission system. File mounts are 
defined by user and user group permission, but the actual write-permissions 
are configured in the workspace.

Further options:

It might be desirable to add a read-only check box to the file mounts 
themselves. So you could add a read-only archive to TYPO3 without relying 
on the file system permissions.

Masi

* Technically it could, but then it has to be taken care that non of the 
editing options of the context menu are shown, ie all except "copy" as 
"info" is non functional anyway (why?).