Feature #103072
open
Manage translation DB fields
0%
Description
Currently the TCA of TYPO3 knows these ctrl options to enable and manage translation behavior for tables:
- languageField (sys_language_uid by convention)
- transOrigPointerField (l10n_parent by convention, l18n_parent in tt_content)
- translationSource(l10n_source by convention)
- transOrigDiffSourceField (l10n_diffsource by convention, l18n_diffsource in tt_content)
Each of these have 2 purposes:
1. Enable translations or a related feature
2. Tell TYPO3 which DB field to use in queries
This by itself is a problem but the main question is whether the names of these DB fields need to be configurable at all.
There are recently a lot of consolidations and simplifications in TCA. The same could be applied here:
- Turn these options from string to bool, thus only enable/disable the feature. TYPO3 would then use fixed DB field names and thus fully manage these.
- Consolidate/merge these options with better and clearer names, e.g. 'enableTranslations' => true, 'trackTranslationDifferences' => true or similar.
Updated by
Updated by Benni Mack 11 days ago
- Status changed from New to Accepted
I am much in favor of this "simplification".
For this to work, I assume that we provide a new option in v13, so you don't have to define the other fields anymore.
https://review.typo3.org/c/Packages/TYPO3.CMS/+/75486
We already create the DB fields. I would always create:- sys_language_uid
- l10n_parent
- l10n_source
- l10n_diffsource
unless defined otherwise.
In v14 we could get rid of the other "ctrl" section options then.