Storing the Changes ¶
There are various ways to store changes to
depend - partly - on what you are trying to achieve and - a lot -
on the version of TYPO3 CMS which you are targeting.
There are two main ways to store your changes to the TCA: inside an extension
or straight in the
folder. Both are described below in
Storing in Extensions ¶
The advantage of putting your changes inside an extension is that they are nicely packaged in a self-contained entity which can be easily deployed on multiple servers.
The drawback is that the extension loading order must be finely controlled. Indeed if your extension modifies another extension, your extension must be loaded after the extension you are modifying. This can be achieved by registering that other extension as a dependency of yours. See the description of constraints in Core APIs .
For more information about an extension’s structure, please refer to the extension architecture chapter in Core APIs.
Storing in the Overrides Folder ¶
Since TYPO3 CMS 6.2 (6.2.1 to be precise) changes to
must be stored inside a folder called
with one file per modified table. These files are named along the pattern
Thus if you want to customize the TCA of
you’d create the file
The advantage of this method is that all such changes are incorporated into
it is cached. This is thus far more efficient.
Be aware that you cannot extend the TCA of extensions if it was configured within
file, usually containing the “ctrl” section
referencing a “dynamicConfigFile”. Please ask the extension author to switch
Only TCA-related changes should go into
files. Some API calls may be okay as long as they also manipulate only
. For example, it is fine to register a plugin with
because that API call only
for table “tt_content”.
Storing in ext_tables.php Files ¶
Until TYPO3 CMS 6.1 (still supported for 6.2) changes to
into an extension’s
file. This is strongly discouraged in more recent
versions of TYPO3 CMS.
Nowadays the only usecase for TCA changes in
is to override TCA definitions
done in the
of a legacy extension. TCA overrides cannot be used in this case
until the author of the legacy extension migrates his code.
Changing the TCA “on the Fly” ¶
It is also possible to perform some special manipulations on
right before it is stored into cache, thanks to the
signal. This signal was introduced in
TYPO3 CMS 6.2.1.