ResourceStorage->getProcessingFolder() won't create processing folder inside folder that does not have "Is Writable"
It's not obvious whether this is a bug or if it's by design, but TYPO3 will generate the processed folder for a file mount in the root of the website rather than when "Is writable" is false for the storage folder.
This poses a problem, for example, we have a project with a folder (legacy/) full of imported media from a previous site, which we don't want editors to be able to augment/modify. It means the web root needs to be writable by the web server/TYPO3. It would be nice to keep the processed ("processing folder") folder inside legacy/, despite the "is writable" setting, rather than having it get plopped into the web root.
Updated by Frans Saris over 6 years ago
- Category set to File Abstraction Layer (FAL)
- Status changed from New to Needs Feedback
- Sprint Focus set to On Location Sprint
isn't it possible/enough to set the "is writable" of the storage but create a readonly filemount for the editors? See https://forge.typo3.org/issues/49391
As of TYPO3 CMS 7 you can set a filemount to readonly direct in the filemount record.
Updated by Alexander Opitz over 6 years ago
- Status changed from Needs Feedback to Closed
No feedback within the last 90 days => closing this issue.
If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.