Project

General

Profile

Actions

Bug #82370

closed

Change Configuration key for extensions from EXTCONF to extensions to prevent conflicts

Added by Matthias Vogel over 6 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Should have
Category:
-
Target version:
-
Start date:
2017-09-08
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
9
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:
On Location Sprint

Description

Original Comment from https://review.typo3.org/#/c/53657/ :
Helmut Hummel
Sep 7 7:40 PM

Patch Set 8:
post -1 on using $GLOBALS['TYPO3_CONF_VARS']['EXTCONF']
because it makes this (useful) change unnecessarily breaking
$GLOBALS['TYPO3_CONF_VARS']['EXTCONF'] is used by extensions already since years (e.g. realurl) and was (despite being documented) considered as "safe space" for custom extension configuration.
When writing the extConf things there too, there will be conflicts.


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Feature #82254: Store extension configuration as plain arrayClosedSusanne Moog2017-08-31

Actions
Actions

Also available in: Atom PDF