[TYPO3-english] Extending TCA the 6.1 way

[Stephan Schuler]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hey there.

Well, in terms of caching, additional non-returning configuration mechanisms that only affect the environment are even more a no-go. So I feel really sorry for having even tried that, since it's really obvious to be strictly forbidden.
The specific example of addToAllTcaTypes could have worked just by accident. But I'm actually glad it hasn't, since this prevented me from creating a regression which would be very hard to debug.

Regards,


Stephan Schuler
Web-Entwickler

Telefon: +49 (911) 539909 - 0
E-Mail: Stephan.Schuler at netlogix.de
Website: media.netlogix.de



- --
netlogix GmbH & Co. KG
IT-Services | IT-Training | Media
Neuwieder Straße 10 | 90411 Nürnberg
Telefon: +49 (911) 539909 - 0 | Fax: +49 (911) 539909 - 99
E-Mail: info at netlogix.de | Internet: http://www.netlogix.de

netlogix GmbH & Co. KG ist eingetragen am Amtsgericht Nürnberg (HRA 13338)
Persönlich haftende Gesellschafterin: netlogix Verwaltungs GmbH (HRB 20634)
Umsatzsteuer-Identifikationsnummer: DE 233472254
Geschäftsführer: Stefan Buchta, Matthias Schmidt



- -----Ursprüngliche Nachricht-----
Von: typo3-english-bounces at lists.typo3.org [mailto:typo3-english-bounces at lists.typo3.org] Im Auftrag von Christian Kuhn
Gesendet: Dienstag, 1. Oktober 2013 16:14
An: TYPO3 English
Betreff: Re: [TYPO3-english] Extending TCA the 6.1 way

On 10/01/2013 02:39 PM, Markus Klein wrote:
> Still one could do other stuff before returning the array in the end.

Please don't! Core does not support any code magic within those TCA files. If you still do that it may break any time.

Simple rule:
* Full new table definitions go to Configuration/TCA/{tablename}.php
* Extending existing tables is done within ext_tables.php with API calls.


Actually all this stuff (LocalConfiguration, TCA table definition, ext_autoload, ...) *should* be not be PHP but YAML to prohibit "code"
and enforce "configuration" only, but we do not have such a layer ...
Flow is way more clever in this area and secures the flow core code from the packages much better this way.


Regards
Christian
_______________________________________________
TYPO3-english mailing list
TYPO3-english at lists.typo3.org
http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english

-----BEGIN PGP SIGNATURE-----
Version: PGP Universal 3.3.0 (Build 9307)
Charset: utf-8

wpUDBQFSSvO0pp0IwsibV8MBCJjQA/0UXn9tc5GbaWhLhuSzRBJl0phDAv1LCtdm
TN2dEXsBBET5DFYStpGs880ygXXoDgB4VhOf3J6eYlxV4dXJrbIdNjmhGwnVD481
C8nNQpvpBRmFTtB1kMnDEupz+Y6vY8SwFuyYEX0s+sJz0WpDaU/dKpl55eoNnhgH
DZ2f6/SoaA==
=RVcD
-----END PGP SIGNATURE-----