Bug #78050
closedTranslation of inline records not working correctly with categories
0%
Description
There is an issue when using inline records with categories on translated records. If both the parent record and the inline record have categories I get a JavaScript error when I want to use "Localize all records" and the inline record does not update. If I reload the page then the record is translated correctly.
The easiest way to reproduce the issue is to use a fresh TYPO3 7.6 installation and install the news extension. (However it is reproducible with any element that has inline records)
- Install TYPO3 7.6
- Install news extension
- Create and translate a sysfolder
- Enable the option "records.contentElementRelation" in the news extension via extension manager
- Add new news entry with a content element relation e.g. a text element
- Translate the news record
- Hit "Localize all records" on the content element relation of the translated record
This will produce the following JavaScript error:
Uncaught TypeError: Cannot read property 'dom' of null tree.js:73
The problem is, that somehow TYPO3 wants to update the form element data[tt_content][{uid}][categories]
instead of data[tx_news_domain_model_news][{uid}][categories]
. That leads to a JavaScript error because the element with the id md5('data[tt_content][{uid}][categories]')
is not found.
Updated by Riccardo De Contardi almost 8 years ago
- Category set to Backend JavaScript
Still present on 7.6.13
Updated by Christoph Vigano over 7 years ago
I also see this error when trying to translate new text records inside of a Grid Element. TYPO3 Version 7.6.21.
Updated by Frank Nägler about 7 years ago
- Status changed from New to Needs Feedback
is this still an issue in v8 or only in v7?
Updated by Markus Mächler about 7 years ago
this seems to be resolved in typo3 v8
Updated by Frank Nägler about 7 years ago
- Status changed from Needs Feedback to Accepted
thanks for your feedback, so this is only an issue in v7
Updated by Susanne Moog over 4 years ago
- Status changed from Accepted to Closed
As v7 is not supported anymore, closing the issue here as fixed in later versions.