Bug #87951

Silent configuration upgrade removes existing entries in $GLOBALS[EXTENSIONS]

Added by Stefan P 4 months ago. Updated 4 months ago.

Status:
New
Priority:
Must have
Assignee:
-
Category:
-
Target version:
-
Start date:
2019-03-19
Due date:
% Done:

0%

TYPO3 Version:
9
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

We already used $GLOBALS[EXTENSIONS] in a TYPO3 8 project to be prepared for TYPO3 9. We accessed them "by hand" (reading from $GLOBALS[EXTEMSIONS][our_ext]@ directly), and wanted to convert to the new API.

When installing TYPO3 9 the silent configuration upgrade removed these entries and we had to re-add them manually.

All our projects are versioned, so we could easily restore everything, but the core should not silently just drop existing entries in LocalConfiguration.php, it should rather only add them.

History

#1 Updated by Stefan P 4 months ago

I just found out that the problem is even worse. All custom entries are dropped always.

Is it mandatory to have the settings also in ext_conf_template.txt starting with TYPO3 9? This is not documented as far as I can see.

We always stored settings in LocalConfiguration.php at the extensions, even if not editable in backend (i.e. having no explicit ext_conf_template.txt). Is the only way to creatre one?

Also available in: Atom PDF