http://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692019-03-19T14:02:59ZTYPO3 ForgeTYPO3 Core - Bug #87951: Silent configuration upgrade removes existing entries in $GLOBALS[EXTENSIONS]http://forge.typo3.org/issues/87951?journal_id=3969042019-03-19T14:02:59ZStefan P
<ul></ul><p>I just found out that the problem is even worse. All custom entries are dropped always.</p>
<p>Is it mandatory to have the settings also in <code>ext_conf_template.txt</code> starting with TYPO3 9? This is not documented as far as I can see.</p>
<p>We always stored settings in LocalConfiguration.php at the extensions, even if not editable in backend (i.e. having no explicit <code>ext_conf_template.txt</code>). Is the only way to creatre one?</p> TYPO3 Core - Bug #87951: Silent configuration upgrade removes existing entries in $GLOBALS[EXTENSIONS]http://forge.typo3.org/issues/87951?journal_id=4198012020-03-20T21:10:48ZGeorg Ringer
<ul><li><strong>Sprint Focus</strong> set to <i>PRC</i></li></ul> TYPO3 Core - Bug #87951: Silent configuration upgrade removes existing entries in $GLOBALS[EXTENSIONS]http://forge.typo3.org/issues/87951?journal_id=4198152020-03-21T08:11:53ZSusanne Moogsusanne.moog@typo3.org
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Rejected</i></li></ul><p>$GLOBALS['EXTENSIONS'] is TYPO3s reserved space for extension configuration. The configuration there needs to be defined in ext_conf_template, to allow TYPO3 to keep the configuration in sync (and react to changing configuration options on ext upgrades). The synchronize feature means that if an extension removes or adds options in its configuration definition, TYPO3 automatically takes care of updating the settings avoiding missing or superfluous configuration.</p>
<p>ext_conf_template provides the schema for the configuration, ExtensionConfiguration class provides the API.</p>
<p>If you want a simple global space without an API available, you should use something more unique to your own project / namespace, if you want the benefit of using TYPO3s intended API you need to use the defined schema file.</p>
<p>Further notes: One thing that the API should achieve would be to make future migration to different configuration storages easier. If accessing extension configuration is done via the API one could think of further features like moving the configuration away from the globals space, overlaying extension and site configuration etc.</p> TYPO3 Core - Bug #87951: Silent configuration upgrade removes existing entries in $GLOBALS[EXTENSIONS]http://forge.typo3.org/issues/87951?journal_id=4203422020-03-24T17:52:42ZBenni Mackbenni@typo3.org
<ul><li><strong>Sprint Focus</strong> changed from <i>PRC</i> to <i>Needs Decision</i></li></ul>