TYPO3 Core

Hi Stan,

some additional ideas to this, some are written in core list as well.

What is the idea of read-only? They are Mountpoints where user have no right to add/change anything.

Now, using this Mountpoints in Element Browser, i see only one issue where a user could change something - that is in file browser and it's upload a file.

So IMHO the flag readOnly is not necessary at all, only in file browser, where the original and the temporary filemounts are mixed, it has to be determined if the selected folder is part of the temporary mount. if yes, don't show upload form.

Beside that i feel that the user-ftp-icon is the wrong icon for such folders, the right one would be icon with a lock symbol, but i didn't investigated, where the user-ftp-icon is used at other places, if not i'm for replacing this icon.

vg Steffen

Hi Steffen,

I would like to reach a stable state first using the read-only flag, because there are still issues with the feature in link wizard mode and in DAM. But I think that you are right and that the read-only flag is not needed in the case of altMounts on the pageTree. I will remove that at least.

Stan

Attaching new versions of the patch for TYPO3_4-2 and trunk respectively.

In wizard and RTE mode, both webmounts and filemounts need to be checked because links may be to both pages and files. When dam_ttcontent is installed, then both webmounts and filemounts need to be checked also because the element browsers is then in db mode, not in file mode, for media/image insertion. So I removed the break after the webmounts check and let execution flow through.

Also, I leave the readOnly flag to false, if only alternate webmounts are configured because the user cannot change/update while selecting a link in the page tree.

The TYPO3 element browser uses additional form fields for upload, but DAM uses an additional tab. In this context, it would be sufficient not to show the alternate mounts on the DAM upload tab.

Closing this issue as it has become a duplicate of #19310.