Actions
Feature #5175
closed
config.qfq.ini via ExtManager
Start date:
06.01.2018
Due date:
% Done:
0%
Estimated time:
Discuss:
Prio Planung:
Vote:
Related issues
Updated by Carsten Rose about 6 years ago
- Status changed from New to In Progress
Es gibt mehrere Varianten:
- Konfiguration im Installtool.
- Konfiguration via eigenem BackendModul - vermutlich aufwendig.
- Via ExtensionManager: dort gibt es ein Settings gear.
Die Variante via ExtensionManager sieht nach sehr wenig Aufwand aus.
- Doc: https://docs.typo3.org/typo3cms/CoreApiReference/ExtensionArchitecture/ConfigurationOptions/Index.html#extension-options
- Beschreibung der Optionen via: `ext_conf_template.txt`
- Unter https://docs.typo3.org/typo3cms/CoreApiReference/ExtensionArchitecture/FilesAndLocations/Index.html steht:
The result is written as an array to LocalConfiguration.php in the variable $GLOBALS['TYPO3_CONF_VARS']['EXTENSIONS'][*extension_key* ]
- Tips fuer den Zugriff:
- https://stackoverflow.com/questions/43537748/how-to-access-the-ext-conf-template-txt-extension-configuration-in-typoscript#43539723
- Zugriff via PHP: unserialize($GLOBALS['TYPO3_CONF_VARS']['EXT']['extConf']['myExt'])
The result is written as an array to LocalConfiguration.php in the variable $GLOBALS['TYPO3_CONF_VARS']['EXTENSIONS'][*extension_key* ]
- Einlesen eines PHP wie LocalConfiguration.php (Array mit Return Statement): http://php.net/manual/en/function.include.php#example-126
Updated by Carsten Rose about 6 years ago
- Tracker changed from Support to Feature
- Subject changed from config.qfq.ini ins Backend ziehen to config.qfq.ini via ExtManager
Updated by Carsten Rose about 6 years ago
- Related to Bug #5890: File 'config.qfq.ini' by default public - protect against access added
Updated by Carsten Rose about 6 years ago
- Status changed from In Progress to Closed
- Target version changed from 55 to 18.6.0
Updated by Elias Villiger almost 6 years ago
- Related to Feature #3663: Configuration 'config.ini.qfq': move it to regular Typo3 configuration added
Actions