[BUGFIX] Add languageUid to index_name to make it unique

[csidirop]

Fixes #1182 and the issues described in #1182 (comment) .

[sebastian-meyer]

I am wondering if we would need to change the default translation method as well. What happens if we manually translate a metadata record in the backend? I assume the translated record would also get an exact copy of the original index_name triggering the same issues when moving the newly translated record around...

Maybe we need to work around this by changing the l10n_mode from 'exclude' to 'prefixLangTitle' and set TCEMAIN.translateToMessage to an appropriate prefix (like '%s_').

[sebastian-meyer]

@csidirop Could you please verify that this also works for records manually translated in the backend? What does the index_name of those records look like?

[sebastian-meyer]

@beatrycze-volk Is this potentially also related to not using the DataHandler in the backend (like in #1184)?

[beatrycze-volk]

@beatrycze-volk Is this potentially also related to not using the DataHandler in the backend (like in #1184)?

That is quiet possible. With DataHandler translated records were created automatically not like now manually.

[sebastian-meyer]

So then this should be fixed with your re-introduction of the DataHandler as mentioned in #1184. Nice!

I'll leave this PR for now, because consistently using the DataHandler would be the better solution.

[sebastian-meyer]

Reverting to using the DataHandler is more work than anticipated. Therefor I'll merge this workaround for now in order to release version 5.0.
I'll open a new issue for DataHandler usage.