Project

General

Profile

Actions
Copy link

Bug #83501

closed

Non-existing file storage ID 1 breaks BaseSetup => "No accessible form storage folders"

Added by Christian Rieke over 6 years ago. Updated 10 months ago.

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

0%

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

Description

Flie mount ID 1 is hardcoded in BaseSetup.yaml

allowedFileMounts:
   10: 1:/user_upload/

If a file mount ID 1 does not exist, form fails with "No accessible form storage folders" message.

Although, according to the core AccessControl documentation, hardcoding the file mount ID looks like the official way to do it, this is the first time that I experience a TYPO3 function to actually break by doing it.

Actions
Copy link
 #1

Updated by Christian Rieke over 6 years ago

  • Subject changed from Non-existing file mount ID 1 breaks BaseStup => "No accessible form storage folders" to Non-existing file storage ID 1 breaks BaseStup => "No accessible form storage folders"

CORRECTION:
file storage with ID 1 must exist (not file mount)

Actions
Copy link
 #2

Updated by Björn Jacob about 6 years ago

  • Sprint Focus set to Remote Sprint
Actions
Copy link
 #3

Updated by Björn Jacob about 6 years ago

  • Subject changed from Non-existing file storage ID 1 breaks BaseStup => "No accessible form storage folders" to Non-existing file storage ID 1 breaks BaseSetup => "No accessible form storage folders"
Actions
Copy link
 #4

Updated by Björn Jacob about 6 years ago

  • Status changed from New to Closed

If a file mount ID 1 does not exist, form fails with "No accessible form storage folders" message.

Normally, this is not the case. In a fresh TYPO3 installation, there is always a file storage with uid 1. The storage is auto-created. Please make sure that the storage 1 exists in your installation.

Actions
Copy link
 #5

Updated by Oliver joppnet almost 5 years ago

Bjoern Jacob wrote:

Normally, this is not the case. In a fresh TYPO3 installation, there is always a file storage with uid 1. The storage is auto-created. Please make sure that the storage 1 exists in your installation.

The "bug" still exists in TYPO3 9.x and, frankly, this answer is quite unsatisfying as it's easily possible to delete the default storage in the backend which leads to the issue mentioned in this ticket.
We just solved the issue by overrdiding the default form's baseSetup.yaml with Typoscript:

module.tx_form.settings.yamlConfigurations {
    1699088 = fileadmin/Yaml/FormSetup.yaml
}

with the following content changing the default storage UID to 2:

TYPO3:
  CMS:
    Form:
      persistenceManager:
        allowedFileMounts:
          10: 2:/form_definitions/
          20: 2:/user_upload/

Actions
Copy link

Also available in: Atom PDF