Project

General

Profile

Actions
Copy link

Bug #83502

closed

YAML files not managed through FAL - can be deleted via file list

Added by Christian Rieke almost 7 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Should have
Assignee:
Ralf Zimmermann
Category:
Form Framework
Target version:
-
Start date:
2018-01-07
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
8
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:
Remote Sprint

Description

One of the main advantages of FAL is that files that are in use in the FE are protected against accidental deletion by BE users. This is not true for form.yaml files.

This is a bug, not a feature request.

If a user has the right to create/edit forms, the corresponding .yaml file is created in the file storage, to which the user must by definition have read/write access. Since .yaml files are not controlled through FAL, the user can delete these files without the typical FAL protection (e.g. "The file cannot be deleted since it is still used at the following places: [record:tt_content:XYZ]" error). In addition, files with/without FAL management are now stored in the same storage structure. Users used to FAL will not think twice about deleting files without FAL references, as those apparently are not used in the FE.

Related issues 1 (0 open — 1 closed)

Related to TYPO3 Core - Bug #83991: Deletion test in form module is case insensitiveClosed2018-02-21

Actions
Actions
Copy link

Also available in: Atom PDF