Project

General

Profile

Actions

Bug #58691

closed

ResourceStorage->getProcessingFolder() won't create processing folder inside folder that does not have "Is Writable"

Added by Gabe Blair about 10 years ago. Updated over 8 years ago.

Status:
Closed
Priority:
Could have
Assignee:
-
Category:
File Abstraction Layer (FAL)
Target version:
-
Start date:
2014-05-09
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
6.2
PHP Version:
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

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.


Related issues 2 (0 open2 closed)

Related to TYPO3 Core - Bug #49391: options.folderTree.altElementBrowserMountPoints (readonly filemounts) not working with FALClosed2013-06-24

Actions
Related to TYPO3 Core - Feature #59830: Add a read_only column to the filemount tableClosed2014-06-23

Actions
Actions

Also available in: Atom PDF