Bug #50871: Remove option to delete a File Storage - TYPO3 Core - TYPO3 Forge

Custom queries

Accessibility
Easy tasks
Forge Triage
JavaScript issues
JavaScript Issues (w/o Epics/Stories)
My open issues
No feedback within 90 days
Open Bugs
Open issues of 10
Recently modified
Regressions
Stabilization Issues
Usability or UX

Watchers (3)

Alexander Opitz
Felix Nagel
Ralf Merz

Actions

Copy link

Bug #50871

open

Remove option to delete a File Storage

Added by Frans Saris over 11 years ago. Updated over 8 years ago.

Status:

New

Priority:

Should have

Assignee:

Category:

Backend User Interface

Target version:

Candidate for Major Version

Start date:

2013-08-07

Due date:

% Done:

Estimated time:

TYPO3 Version:

6.2

PHP Version:

Tags:

Complexity:

medium

Is Regression:

Sprint Focus:

Remote Sprint

Description

Currently it doesn't make sense you can delete a storage.
When you delete a storage there is no check if there are still files in uses of this storage.
So everywhere where a reference to a sys_file of the deleted storage is present you get a Exception.

Related issues 4 (0 open — 4 closed)

Related to TYPO3 Core - Task #64617: Don' change configuration of filestorage if files are present

Closed

2015-01-29

Actions

Related to TYPO3 Core - Bug #64631: Relations between files(sys_file) and file storage(sys_file_storage) are not recoreded in sys_refindex

Closed

2015-01-30

Actions

Related to TYPO3 Core - Bug #55714: Not available storages assigned to user shouldn't cause "hard failure"

Closed

Georg Ringer

2014-02-06

Actions

Has duplicate TYPO3 Core - Bug #62489: FE : “Desired storage is not in the list of available storages”

Closed

2014-10-27

Actions

Issue # Delay: days Cancel

History
Notes
Property changes
Associated revisions

Actions

Copy link

Updated by Oliver Hader over 11 years ago

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.

Actions

Copy link

Updated by Andreas Wolf over 10 years ago

Status changed from New to Accepted
Is Regression set to No

I just had this case while debugging a broken installation. I think the DataMapper should check in a hook that no files are still in use from that storage (or we disallow deletion completely if that's possible).

Actions

Copy link

Updated by Frans Saris almost 10 years ago

Sprint Focus set to On Location Sprint

Actions

Copy link

Updated by Ingo Schmitt almost 10 years ago

Complexity set to medium

Actions

Copy link

Updated by Philipp Gampe almost 10 years ago

Status changed from Accepted to In Progress

Actions

Copy link

Updated by Alexander Opitz almost 10 years ago

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).

Actions

Copy link

Updated by Philipp Gampe almost 10 years ago

I also think that deleting orphaned storages should be possible.

Actions

Copy link

Updated by Gerrit Code Review almost 10 years ago

Status changed from In Progress to Under Review

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

Actions

Copy link

Updated by Gerrit Code Review almost 10 years ago

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

Actions

Copy link

#10