Issue Bug Closed

#31812Localization failed; There already was a localization for this language of the record!

Stefan Geith 11/15/11, 09:52 updated 03/09/20, 12:10

Description

If – by accident – a (single) record got translated before its parent got translated, then the translation will never again be accessible from within IRRE.

Example:
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!“
is thrown.

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…

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.