Localization failed; There already was a localization for this language of the record!
If - by accident - a (single) record got translated before its parent got translated, then the translation will never again be accessible from within IRRE.
Think of a Cities and Hotels. Hotels are Inline-Records within Cities.
If you translate a Hotel and later you want to translate the city, that contains this hotel, the error-message
"Localization failed; There already was a localization for this language of the record!"
So IRRE knows, that there is a translation, but because this translation does not have the correct relation, its not getting processed.
BUT: IRRE knows the relation of the (untranslated) default-records an could easily correct the relation to the already translated child-record - Right ?
The same problem occurs, if you translate using L10N-Mgr: All imported Irre-Child-Records dont have the correct relation to their parents and so will not be accessible via IRRE from their parent-records...
#7 Updated by Stefan Geith over 7 years ago
This Problem is still in 4.5 and 4.7 - patch is for 4.5 and I use it in every Installation.
Rebase to current master is a problem - I don't use 6.x atm and do not have a dev-setup for 6.x at the moment.
I will even have to test, if this is still not solved in 6.x ...
#9 Updated by Maik Peuser over 6 years ago
we could get it running with a modified version (TYPO3 6.17). We replaced all old t3lib_div calls and the testInt call. So far most of it for im/export via backend works, but anything with fal-relations isn't translated correctly. the fal relations are broken and you cannot those relations in backend.
Question is if this is core related or maybe only in the extension ?eat =)
#17 Updated by Raphaël Splivalo Splivalo 9 months ago
- Priority changed from Should have to -- undefined --
- TYPO3 Version changed from 7 to 9
- PHP Version changed from 5.5 to 7.3
Sorry to re-open this issue.
We have TYPO3 9.5.13 on some websites and we have that problem.
When we try to translate a page we have that warning "There already was a localization for this language of the record", when we look at the pages table in DB the page record have a correct l10n_source but no id in the l10n_parent column.
We have that errors with migrated TYPO3 (V7 to V9 or V8 to V9).
Thanks for your help
#18 Updated by Christian Oettinger 8 months ago
I had the same issue (warning "There already was a localization for this language of the record" when trying to create a translation).
In my case a BE user was trying to create a translation of a page while the field
Transl.Orig (l10n_parent) [pages:l10n_parent]
was not set as editable in Access List of the appropriate BE user group.
So the translation was created but "l10n_parent" had value 0, which led to the problem in my case.
Have a great day!