-
Notifications
You must be signed in to change notification settings - Fork 0
Feature Request: mirror content from "other" language #10
Comments
Perhaps we should now delete all wrongly copied wrong-language content from the pages. |
Unfortunately, I didn't have the time yet to look into this and test it thoroughly. But it seems like there are still a few problems. Take for example the following page (which I stumbled upon) where there is a "leaked" "German" version (which in reality is a copy of the original English content). The English version of the page got updated with additional content in the meantime – but in the backend there is no way to edit the German text which persists as the copy of the original English version. I cannot say if this is some kind of special case where only the calender is affected.
|
Hmm, I don't see a German text which is a copy of the English text on that page. Neither on the frontend nor on the backend. This page has an English content (an HTML Editor with some text) and a different German content (a person contact). So neither content is empty, this "leak" bug didn't apply and a fallback to the other language doesn't apply. If the contact card would be added to the English content and removed from the German content, the German content would be emtpy and a German session would see the English text with "Diese Seite ist in Deutsch nicht verfügbar". |
At the moment, there is a fallback only for missing German-language content. A line reading "Seite nicht verfügbar in Deutsch" is displayed above the mirrored English site.
In contrast, when English content is missing during the editing process, the German version gets automatically copied/forked into the empty English text boxes upon the first save. This can be irritating and causes problems when the editors resume their work in the wrong language version of the content.
The best solution would be to have the fallback both ways and display a line "Site not available in English" with the German content mirrored below.
The text was updated successfully, but these errors were encountered: