[!!!][TASK] Drop additional palette handling
[Packages/TYPO3.CMS.git] / typo3 / sysext / core / Documentation / Changelog / master / Deprecation-67737-TcaDropAdditionalPalette.rst
1 ==================================================
2 Deprecation: #67737 - TCA: Drop additional palette
3 ==================================================
4
5 Description
6 ===========
7
8 The ``showitem`` string of ``TCA`` ``types`` allowed to define an "additional palette" as third
9 semicolon separated name of a field. Such a palette is then rendered after the main field.
10 This handling is dropped and existing "additional palettes" are migrated to a
11 "normal" palette definition directly after the field.
12
13 Before:
14
15 .. code-block:: php
16
17 'types' => array(
18 'aType' => array(
19 'showitem' => 'aField;aLabel;anAdditionalPaletteName',
20 ),
21 ),
22
23
24 The behavior before was: If the field ``aField`` is rendered, then the
25 palette ``anAdditionalPaletteName`` is rendered, too. This functionality is dropped, the
26 migrated field now looks like:
27
28 .. code-block:: php
29
30 'types' => array(
31 'aType' => array(
32 'showitem' => 'aField;aLabel, --palette--;;anAdditionalPaletteName',
33 ),
34 ),
35
36
37 A casual field name in ``showitem`` now only has a label override as additional
38 information, like ``aField;aLabel``, while a palette is referenced as
39 ``--palette--;aLabel;paletteName``.
40
41
42 Impact
43 ======
44
45 All extensions that use "additional palette" syntax are migrated to the new syntax, but will
46 throw a deprecation message.
47
48 The "additional palette" handling was sometimes misused as "poor-mans-access-control":
49 If access to the main field was not allowed, the palette fields were not rendered either. This
50 changed, the main field and the palette are decoupled, it may happen that additional fields
51 are now rendered for users that should not have access to it. Adapting the ``exclude`` config
52 definition of the palette fields and user or group access records is necessary in those cases.
53
54
55
56 Affected Installations
57 ======================
58
59 Extensions that use the "additional palette" handling.
60
61
62 Migration
63 =========
64
65 An automatic migration is in place and logged to ``typo3conf/deprecation_*``. The migration code
66 will be dropped with TYPO3 CMS 8, a manual fix of the according ``showitem`` field is required,
67 the deprecation log gives detailed information on how the definition should look like.