[TYPO3-core] FAL: get rid of fileadmin/_processed_ and use typo3temp instead?
klein.t3 at reelworx.at
Mon Sep 22 01:08:47 CEST 2014
I didn't read the whole thread here, but after reading your answer one thing comes immediately to my mind:
What about read-only storages?
I agree that processed files are only variants, but I disagree that those have to be stored in the same storage.
I even ask the general question: Why would I store a processed file in the storage of the original file, if I had no usage of this file in the storage?
A processed file is only relevant to the CMS, but usually not for the editor, the storage or anyone else.
Example: I don't want the processed files to be stored on my dropbox account, but I want to use my images from the cloud storage.
TYPO3 CMS Active Contributors Team Member
> -----Original Message-----
> From: typo3-team-core-bounces at lists.typo3.org [mailto:typo3-team-core-
> bounces at lists.typo3.org] On Behalf Of Helmut Hummel
> Sent: Sunday, September 21, 2014 11:10 PM
> To: typo3-team-core at lists.typo3.org
> Subject: Re: [TYPO3-core] FAL: get rid of fileadmin/_processed_ and use
> typo3temp instead?
> On 21.09.14 20:24, Frans Saris wrote:
> > I use for secured storages a folder outside of the document root. It
> > makes sense to also have the procesed files there.
> I want to stress this. All files belong to a storage. A storage can
> (conceptually) be located anywhere (e.g. a CDN). Processed files are just file
> variants and thus must also be located on the storage where they are
> derived from. That you can delete the _processed_ folder and files are then
> recreated is an implementation detail which (is not subject to but) might
> Kind regards,
> Helmut Hummel
> Release Manager TYPO3 6.0
> TYPO3 CMS Active Contributor, TYPO3 Security Team Member
> TYPO3 .... inspiring people to share!
> Get involved: typo3.org
> Before posting to this list, please have a look to the posting rules on the
> following websites:
> TYPO3-team-core mailing list
> TYPO3-team-core at lists.typo3.org
More information about the TYPO3-team-core