Feature #20325
closed
function module can be configurred only in ext_tables.php
Added by Franz Holzinger about 15 years ago.
Updated almost 9 years ago.
Description
If you want to add an addition to the function module, you must do this in the file ext_tables.php of your extension. However this is not usefull, because this file is intended to make changes to the $TCA and not for the module configuration. This forces you to have the file ext_tables.php in your backend extension. But normally a backend extension does not modify the $TCA.
This strange behaviour happens only because the $TBE_MODULES_EXT is unset in config_default.php . This should not be unset here.
(issue imported from #M10931)
Files
- Status changed from New to Needs Feedback
- Target version deleted (
0)
As this report is very old, is the handling in newer TYPO3 CMS Versions (like 6.0/6.1) more like you expect it?
The problem seems to still exist in TYPO3 6.0.
The file is now called
./typo3/sysext/core/Classes/Core/Bootstrap.php
Everything is unset in
protected function unsetReservedGlobalVariables() {
This is weired. You should not unset it.
- Status changed from Needs Feedback to New
- Target version set to 7.1 (Cleanup)
- Target version changed from 7.1 (Cleanup) to 7.4 (Backend)
- Status changed from New to Closed
The intended behaviour is indeed to define this in ext_tables.php as long as we don't have the new Backend Module API in place.
TCA changes should nowadays go into Configuration/TCA/ or Configuration/TCA/Overrides and backend module API registrations need to go into ext_tables.php due to the nature of the bootstrap. The core modules are registered through ext_tables.php as well currently, so this is fine.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by