Bug #88873: ext: form hangs (run into 500 error) when a lot of files are in the fileadmin - TYPO3 Core - TYPO3 Forge

Actions

Copy link

Bug #88873

closed

ext: form hangs (run into 500 error) when a lot of files are in the fileadmin

Added by Christian Hackl over 4 years ago. Updated over 2 years ago.

Status:

Closed

Priority:

Should have

Assignee:

Category:

Form Framework

Target version:

Start date:

2019-11-05

Due date:

% Done:

Estimated time:

TYPO3 Version:

PHP Version:

7.2

Tags:

performance

Complexity:

Is Regression:

Sprint Focus:

Description

TYPO3 9.5.8 with many many many files in the fileadmin directory.

if you click on the modul form in the backend, the form module loads dead - until it runs into the php_exectuion_time or produces 500 errors - "Premature end of script headers: index.php". (the SQL process that is started is sleeping and will not be aborted)

This only happens if there are 100d of files in the fileadmin. Although the allowed "allowedFileMounts" or "allowedExtensionPaths" are explicitly specified in custom BaseSetup.yaml.
If you move the files from fileadmin to a parent dir / outside of fileadmin - all works fine.

Related issues 2 (2 open — 0 closed)

Actions

Copy link

Updated by Susanne Moog over 4 years ago

Tags changed from form to form CodingNight

Actions

Copy link

Updated by Christian Hackl over 4 years ago

I think this is the same problem like this: https://forge.typo3.org/issues/88913

Actions

Copy link

Updated by Christian Hackl over 4 years ago

Related to Bug #88913: link wizard - error 500 - many files directly fileadmin/user_upload/ added

Actions

Copy link

Updated by Riccardo De Contardi over 4 years ago

Are we talking here about EXT:form or the backend interface (so Formengine, I guess)?

Actions

Copy link

Updated by Christian Hackl over 4 years ago

don't no exactly, i think the problem is that the ext:form is searching for the config yaml files and it searches in the complete fileadmin directory insteed of the given "allowedFileMounts" or "allowedExtensionPaths". (looks like)

The link handler from linked issue 88913 above works fine.

Actions

Copy link