On a couple of sites with variants now, I've set it up so that the variant is pre-populated when it is first created with property values from the 'default language' eg English.
In some circumstances, depending on who is translating, this was preferred to side by side editing.
And particularly when there are complex property editors, eg the grid or nested content - the editor is happy to translate the text, but doesn't want to have to redo the layout!
The way I'd do this is using the EditorModelEventManager SendingContentModel event - that gives you access to all the variants, and their status, 'before' the page is displayed to the Editor 'for editing'.
I've written a 'broader' blog post about using this even to filter which languages an editor can see:
There is an option to do this in Translation Manager (it would be really nice in the core )
If a node hasn't been sent to translation yet (if its out for translation then the content will populate from the job when it is returned) - Then there will be a "clone" option that will copy all of the default culture proprieties to the selected language.
The code isn't super complex - i think i have it available somewhere, the real issue is where you put the button, which is why we made it part of the translation manager tool.
Language Variant - copy "English" page to other language
Is there any way to copy the whole english page to the other language? I have a grid on the page and I dont seem to be able to copy it.
Hi Lori
On a couple of sites with variants now, I've set it up so that the variant is pre-populated when it is first created with property values from the 'default language' eg English.
In some circumstances, depending on who is translating, this was preferred to side by side editing.
And particularly when there are complex property editors, eg the grid or nested content - the editor is happy to translate the text, but doesn't want to have to redo the layout!
The way I'd do this is using the EditorModelEventManager SendingContentModel event - that gives you access to all the variants, and their status, 'before' the page is displayed to the Editor 'for editing'.
I've written a 'broader' blog post about using this even to filter which languages an editor can see:
http://tooorangey.co.uk/posts/umbraco-v8-variants-and-limiting-editor-access-by-language-an-adventure-story/
but it also contains an example under the heading 'populating default values for variants' that might give you inspiration for how this could be done.
regards
marc
Hi Lori,
There is an option to do this in Translation Manager (it would be really nice in the core )
If a node hasn't been sent to translation yet (if its out for translation then the content will populate from the job when it is returned) - Then there will be a "clone" option that will copy all of the default culture proprieties to the selected language.
The code isn't super complex - i think i have it available somewhere, the real issue is where you put the button, which is why we made it part of the translation manager tool.
is working on a reply...