warning - Message
TYPO3 4.6 was the last version for which the changes were temporarily documented here. From now on the relevant bug trackers of each core manual must be used. Please refer to the instructions below.
Any change to the TYPO3 CMS Core that requires documentation or has an impact on existing documentation must be accompanied by the relevant changes to the proper manual. This is especially true for new or modified features, in particular APIs, TypoScript or TSconfig properties.
When you push such a change to Gerrit, you are requested to take the following steps:
- Open an issue in the manual(s) that is(are) impacted (if unsure which, look at the list below for help).
- In this issue set a relation to the Core issue using the Related issues field
- Set the Target Version to the one corresponding to the TYPO3 CMS Core (if it's missing, please content the Documentation Team, we will add it).
- Document the change in the Description of the issue. If it's lengthy, feel free to set up a wiki page and point to it. If you don't feel at ease writing about the change, don't worry, go ahead and the Documentation Team will improve on it. On the contrary, if you're fine writing, you're welcome to go the whole way and push a patch to the corresponding Git repository (see the section about contributing to the documentation).
Should the Core patch be dropped after all, please also mention this in the issue. This saves the Documentation Team quite a bit of looking things up.
Choosing a bug tracker
There exists one bug tracker per core manual. Use the chart below to help you choose which bug tracker to use in case you are unsure:
|Type of change||Bug tracker|
|TypoScript property or condition||TypoScript Reference (TSref): https://forge.typo3.org/projects/typo3cms-doc-typoscript/issues|
|TSconfig property or condition||TSconfig: https://forge.typo3.org/projects/typo3cms-doc-tsconfig/issues|
|TCA property||TCA Reference: https://forge.typo3.org/projects/typo3cms-doc-tca/issues|
|API or other way of interacting with TYPO3, information for extension developers (but see below for more specific topics)||Core APIs: https://forge.typo3.org/projects/typo3cms-doc-core-api/issues|
|Changes relating specifically to TYPO3 services||TYPO3 Services: https://forge.typo3.org/projects/typo3cms-doc-typo3-services/issues|
|Changes or improvements related to security||Security Guide: https://forge.typo3.org/projects/typo3cms-doc-security/issues|
|Skinning API||Skinning Reference: https://forge.typo3.org/projects/typo3cms-doc-skinning/issues|
|General information about the inner working of TYPO3||Inside TYPO3: https://forge.typo3.org/projects/typo3cms-doc-inside-typo3/issues|
|Introduction Package: any change to the IP has an impact on the Getting Started tutorial||Getting Started: https://forge.typo3.org/projects/typo3cms-doc-getting-started/issues|
Pending documentation (4.4)
Skinning Reference (4.4)
2010-02-19 by Benjamin Mack (on behalf of Steffen Gebert) (I think this can be removed again, as this functionality was changed, haven't checked though) to be placed in the table of chapt. 6 in TYPO3 APIs
stylesheetDirectories Add all *.css files of a directory. Example: $TBE_STYLES['stylesheetDirectories'][$_EXTKEY] = 'EXT:myskin/stylesheets/custom/'; It is encouraged to separate the styles in two parts, once for the "structure" and the second for the "visual": $TBE_STYLES['stylesheetDirectories'][$_EXTKEY]['structure'] = 'EXT:myskin/stylesheets/structure/'; $TBE_STYLES['stylesheetDirectories'][$_EXTKEY]['visual'] = 'EXT:myskin/stylesheets/visual/';
SPRITE ICON API. Added on 2010-05-02 by Benjamin Mack - Should be a new section right after the skinning API part. Edited on 2010-05-25 by Steffen Ritter
Changes committed to CoreDocs
When a pending documentation change is committed to the Core Documentation, it is removed from this page and moved to: