TYPO3 Core

If we see a storage as a definition to connect a folder of the physical file system with the TYPO3 file abstraction layer, then we still might allow to remove the storage definition, however should catch the exceptions - or add an option to the install tool to remove a storage, it's sys_file records (not the actual files), sys_file_references and processed files.

I think, we should left the possibility to delete storages, for example if you moved from a local to a remote storage (or vice versa). Maybe first we need to define scenarios.

But maybe this scenarios lead to a "FAL Management Extension" which is more for admins and not editors (like media).

I also think that deleting orphaned storages should be possible.

Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/36456