imagecaption_position is used by css_styled_content and must be in Core!
It is stated in:
typo3_src (7.6 LTS)/typo3/sysext/core/Documentation/Changelog/7.2/Breaking-65922-MoveUnusedTt_contentTcaFieldsToCompatibility6.rst
There are some database fields defined in 'frontend' which are not used by `frontend` or `css_styled_content`. These fields have been moved to `compatibility6`.
This is wrong. At least imagecaption_position - possibly also other fields, but that I did not test - are indeed used by css_styled_content!
Therefore, this field must be migrated back into the core. To use current functionality (as captionAlign), it is madness to use a compatibility extension.
See also: \TYPO3\CMS\CssStyledContent\Controller\CssStyledContentController::render_textpic() , Ctrl+F for 'captionAlign', and
(7.6 LTS) typo3_src/typo3/sysext/css_styled_content/static/setup.txt:795
imagecaption_position is also used as css_styled_content imageblock palette in: typo3_src/typo3/sysext/css_styled_content/Configuration/TCA/Overrides/tt_content.php:431
[BUGFIX] Readd used fields in css_styled_content
These fields were removed from EXT:frontend and moved to compatibility6.
But both fields are still used by csc and should be provided by the
Tested-by: TYPO3com <email@example.com>
Reviewed-by: Wouter Wolters <firstname.lastname@example.org>
Tested-by: Wouter Wolters <email@example.com>
Reviewed-by: Susanne Moog <firstname.lastname@example.org>
Tested-by: Susanne Moog <email@example.com>
#1 Updated by Leonie Philine Bitto 11 months ago
To make the issue clearer:
The field(s) has/have been moved from EXT:frontend into EXT:compatibility6 - even though imagecaption_position is an active TYPO3 7 feature of css_styled_content.
This means that while imagecaption_position might be misplaced in EXT:frontend, it must now be moved into EXT:css_styled_content - and definitely not into EXT:compatibility6.
#3 Updated by David Bruchmann 11 months ago
I can confirm that issue, the fields should be moved to css_styled_content.
"compatibility6" seems being the wrong place too for me as long as the fields are (still) used by css_styled_content.
Probably it's not "madness" but just has been a task by people who primary use fluid_styled_content now without much care about the good old css_styled_content ;-)