Actions
Feature #50828
closedFallback storage "zero" shall be read-only
Status:
Rejected
Priority:
Should have
Assignee:
-
Category:
File Abstraction Layer (FAL)
Target version:
Start date:
2013-08-06
Due date:
% Done:
0%
Estimated time:
PHP Version:
5.3
Tags:
Complexity:
medium
Sprint Focus:
Description
The fallback storage "zero" (uid:0) shall be read-only since it is used as fallback for /uploads/* and /typo3conf/ext/* resources.
Updated by Ernesto Baschny over 10 years ago
- Category set to File Abstraction Layer (FAL)
- Status changed from New to Accepted
Updated by Mathias Schreiber about 9 years ago
- Is Regression set to No
- Sprint Focus set to On Location Sprint
Updated by Ingo Schmitt about 9 years ago
If you set Storage Zero to readOnly, no processed files will be created.
Updated by Ingo Schmitt about 9 years ago
After Discussion at T3Sprint in Essen:
- There are use cases where a write of files in storage zero is needed
- Storage zero is only useable via API, if a developer wants to write files to typo3temp, this could be done
- When a storage is not writeable, no processed files are written (61463#)
So, currently no possibility to set storage zero to writeable = false.
See also: http://wiki.typo3.org/Blueprints/FAL-StaticResources
Updated by Ingo Schmitt about 9 years ago
- Tracker changed from Bug to Feature
- Status changed from Accepted to On Hold
- Target version set to 8 LTS
- Sprint Focus deleted (
On Location Sprint)
If the FAL Concept changes for 8, this issue should be reevaluated.
Updated by Riccardo De Contardi about 7 years ago
- Target version changed from 8 LTS to 9.0
Updated by Benni Mack over 6 years ago
- Status changed from On Hold to Rejected
Won't be possible in v9, until uploads/ is gone, also it has to be investigated how FAL handles processed images (writable) for "zero" - which is not possible conceptually
Actions