Project

General

Profile

Actions

Bug #98363

open

EXT:form - Deletion of forms created in allowedExtensionPaths not possible

Added by Kevin Ditscheid about 2 years ago. Updated 5 months ago.

Status:
New
Priority:
Should have
Assignee:
-
Category:
Form Framework
Target version:
-
Start date:
2022-09-16
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
11
PHP Version:
8.1
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

The deletion of forms that are placed in a path configured under TYPO3.CMS.Form.persistenceManager.allowedExtensionPaths is not possible, although the creation in these locations works without an error message.
The delete function of FormManagerController is using the ResourceFactory wich checks, if the YAML file of the form is placed in a public location. If this isn't the case (which isn't checked on creation), the PathUtility throws a InvalidFileException which the ResourceFactory interprets as ResourceDoesNotExistException with the message

Tried to access a private resource file "EXT:my_ext/Resources/Private/Forms/test1.form.yaml" from fallback compatibility storage. This storage only handles public files.

Since we can configure a private path for YAML storage and the fact that YAML files aren't public resources in the first place, I suggest removing the check for public locations when saving and deleting forms in the backend.

Example configuration in BaseSetup.yaml

TYPO3:
  CMS:
    Form:
      persistenceManager:
        allowedExtensionPaths:
          10: EXT:my_ext/Resources/Private/Forms/
        allowSaveToExtensionPaths: true
        allowDeleteFromExtensionPaths: true


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #101457: Deletion of forms saved within a sitepackage crashesClosed2023-07-27

Actions
Actions

Also available in: Atom PDF