Feature #16146
closed
Add fileadmin in Element Browser in general DRAFT workspace
Added by ben van over 18 years ago.
Updated almost 11 years ago.
Description
- When you log in as an admin "fileadmin/" is not available, because file operations are not permitted. When an admin wants to use DRAFT worksoace to add or edit an article he cannot add images because the filemount "fileadmin" is not available.
- Fileadmin should be available in the element browser to add files. Situations where an admin uses the DRAFT workspace to add or edit content are quite common.
<quote kasper>
Fileadmin should be available as read-only in draft workspaces (which basically means in the Element Browser).
</quote kasper>
(issue imported from #M3486)
The fileadmin (that is the specif mount points) should be available for ALL users in DRAFT not only admins. If not DRAFT is unusable.
it is currently not possible to add filemounts to the default draft workspace. that means: yes, the draft ws is quite unusable for normal users (and access to the draft ws should not be allowed for normal users). But I see no problem with this.
I see a big problem with this. And I don't ask for a fileadmin *module". But I think - and Kasper's quote doen't talk about admins - that the fileadmin should be read-only for ALL users (which have a filemount setting).
You cannot do any reasonable workflow without read-only access to the fileadmin. How is anybody supposed to work in it if she cannot add images and other file resources?!?!?
Right now, preparing content elements with images or other files isn't possible because the fileadmin-tree isn't visible. As Martin already proposed, it should be available but read-only.
A basic read-only file admin could be a hidden File>List but an active Element Browser.
In the Element Browser the "Overwrite existing files" options must be disabled! Uploading of files and creating of folders may be disabled.
This basically makes workspaces unusable for us.
The whole point is to be able to create new collecitons of pages, including images. Even if we had to upload new images / etc. to live workspace (typically these are "new" and have different names..) with RO access inside of a workspace we could at least create the elements.
Essentially, at this point in time, Typo3 workspaces only allow for modifying text content in existing pages!
bump
Just upgraded a TYPO3 installation and came across this bug. I would consider this a major bug, because whats the benefit of workspaces if I can only use it for text only elements???
Martin, are you working on this? Otherwise please unassign the record from you, so we need to find someone else who solves the problem.
It may be important to mention that this does only affect the DRAFT workspace. It's no problem to add filemounts for custom workspaces!
However, you still need to consider that files are not versioned at all!
Fixed with 4.5.0 where the draft workspace will be gone (migrated to a real workspace!)
- Target version deleted (
4.5.0)
- Category changed from Miscellaneous to Workspaces
- Project changed from 624 to TYPO3 Core
- Category changed from Workspaces to Workspaces
Also available in: Atom
PDF