1) Answer: using a delegate control with ControlId="GlobalSiteLink0"2) Answer: VariationRootPageLayout.aspx3) Answer:1) create a copy of the variationroot.ascx and change the reference to the user control in the VariationRootPageLayout.aspx using Sharepoint designer.2) add the required logic directly into the VariationRootPageLayout.aspx and enable inline code in the web.config
The most important category is Site Management. You should filter the ULS log for this category first. If this does not give you relevant information, add the other two WCM categories on top.If the problem is related to problems occurring during export/import, you need to add the two SPF categories on top in the sequence listed.
Where are configuration settings stored?Answer: Property Bag of root site of site collectionProperty Bag of root folder of root site of site collectionProperty Bag of root folder of Relationships ListListItems in Relationships ListListItems in Variation Labels listProperty Bag of the sites in the Variation HierarchyListItem columns of Pages in the Variation Hierarchy Answer: ItemUpdated (minor versions and/or content moderation enabled)ItemCheckedIn (minor versions and content moderation disabled)[Solution]WCM/Site ManagementAnswer the following questions to confirm your understanding of lesson topics.1. How is the variation labels menu integrated into the master page?[Solution]using a delegate control with ControlId="GlobalSiteLink0"2. Which page layout is used for the VariationRoot.aspx?[Solution]VariationRootPageLayout.aspx3. How can you configure a specific logic for the variation root landing page for just one single site collection?[Solution] 1) Create a copy of the variationroot.ascx and change the reference to the user control in the VariationRootPageLayout.aspx using Sharepoint designer2) Add the required logic directly into the VariationRootPageLayout.aspx and enable inline code in the web.config
BIWUG on SharePoint 2010 Multilingual Solutions (Variations) Deep Dive
Used to restore and update relationships list entries in case that a publishing page was restored fromthe recycle bin.Used to trigger the peer page creation and peer page update if automatic content creation andpropagation is enabled for Pages libraries which have minor versions and/or content moderationenabled.Used to trigger the peer page creation and peer page update if automatic content creation andpropagation is enabled for Pages libraries which have minor versions and content moderationdisabled.Used to collect the variation group id information from a publishing page which is about to be deletedto make it available in the ItemDeleted event firing after the delete operation.
Used to update the relationships list entries for deleted and recycled publishing pages.If a publishing page which resided in the source variation label is deleted or recycled then allrelationships list entries referencing the variation group of the deleted/recycled page are recycled aswell.If a publishing page which resided in a target variation label was deleted or recycled then itsrelationships list entry is marked as deleted by setting the value of the "Deleted" column of therelationships list entry to "Yes".In case of a restore of such a page from the recycle bin, these actions have to be reverted.Used to trigger source site variation to target labels when the Publishing feature is activated on a site.This happens as well when a new Publishing site is provisioned or if the feature is manuallyactivated on a site.
Used to delete the relationship list entry and the variation specific properties when deactivating thepublishing feature on a site.Used to cancel a delete operation in case that the site being deleted is the variation root site (ifspawned labels exist) or a Variation Top site. In addition, the variation system uses this event to cleanup the relationship list items for the deleted site and its pages.Used to cancel the move operation in case that the site being moved is a variation top site, asmoving a Variation Top site would destroy the variation label it belongs to.Used to trigger source site variation to target labels if a site is moved from outside into the sourcevariation hierarchy. In addition, it will maintain the information in the relationship list in case that a siteis moved out of a variation label.