[TYPO3-dev] What shouldn't exist in TCA/Overrides?

Viktor Livakivskyi invisible.kinder at gmail.com
Thu Feb 26 14:32:37 CET 2015


Hi, list.

Since 6.2.1 there is a nice feature, which allows to cache TCA overrides and do not do the overlay in a runtime [1]. However, after reading Anja's post [2], I have a feeling, that not just addTCAcolumns() and addToAllTCAtypes() can be put there.

E.g. Can I move \TYPO3\CMS\Extbase\Utility\ExtensionUtility::registerPlugin() calls there as well? I need plugin be registred only once and cahced - not executed every time at runtime.
Same for:
\TYPO3\CMS\Core\Utility\ExtensionManagementUtility::addLLrefForTCAdescr();
\TYPO3\CMS\Core\Utility\ExtensionManagementUtility::allowTableOnStandardPages();
\TYPO3\CMS\Core\Utility\ExtensionManagementUtility::makeCategorizable();
\TYPO3\CMS\Core\Utility\ExtensionManagementUtility::addStaticFile();
etc.

In other words: can ext_tables.php be safely moved to TCA/Overrides folder?
If not - what shouldn't exist in Overrides? Anja mentioned flags for sys_languages. Anything else?

[1]: http://docs.typo3.org/typo3cms/TCAReference/6.2/ExtendingTca/StoringChanges/Index.html#storing-changes-extension-overrides
[2]: http://ab-softlab.tumblr.com/post/90851249969/tca-manipulation-in-typo3-6-2



More information about the TYPO3-dev mailing list