AI OnAI Off
Copy master contents on translation rather to keep the fields blank.
Khurram,
Check this post: http://cjsharp.com/blog/2013/04/19/automatically-populating-page-or-block-type-properties-for-a-language-branch-in-episerver-7/
It was built for EPiServer 7.1, but there shouldn't be any difference for 7.5+
Edited,
Oct 09, 2014 14:46
Mark Stott
- Jul 10, 2020 11:34
As a heads up, the linked blog post was written with a version of EPiServer where the ContentEventArgs.Content had context to the original content item, this appears to no longer be the case and you get an clean version of appropriate content type with an empty/default content reference. It appears only to be linked to the original content after the create button has been pressed in the UI.
You could potentially you can hook into the CreatingContentLanguage or CreatedContentLanguage events, but any required fields would need to be populated first via the frontend. This would result in required fields being populated by the user and then potentially overridden by this event unless you change the behaviour of the suggested code.
You could potentially you can hook into the CreatingContentLanguage or CreatedContentLanguage events, but any required fields would need to be populated first via the frontend. This would result in required fields being populated by the user and then potentially overridden by this event unless you change the behaviour of the suggested code.
Content editors can achieve this by comparing the current published version to the published version of the master branch:
Jul 10, 2020 11:42
Appreciate this post is old, but iut has new comments. The Episerver Languages add-on allows you to use the gadget to create language versions prepopulated with the content from another language. Using this add-on should prevent the need for any manual compare.
We've used this quite successfully in productions sites, mostly for different english variants where we use fallback languages but sometimes need to create a UK/US specific page with minor content changes for legal reasons.
I can't post links unfortunately but a Google for 'episerver languages add-on' should bring up the webhelp for it.
Jul 13, 2020 11:32
When a block/page is translated the Master content(Content in master language) is not 'carried' across.
Master language is English Uk and client want to translate it in English US. on Translating US all fields are blank Is there any way to get English UK values by default before translation.
Regards
/K