New answers tagged custom-masterpage
You can use SharePoint API : PublishingWeb (http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.publishing.publishingweb_methods.aspx) with the method "AddPublishingPage" if you need to customize this page after creation (i.e. add webparts on it), simply use SPWebPartManager ...
For 2013, to reference the virtual directories you must add /15 after the "_controltemplates" in this case. Like this: /_controltemplates/15/langSelector.ascx
Have you considered using feature stapling? Feature stapling is designed to activate a feature when a new site is created. Whether it activates can be setup to determine the site template id of the new site. In your case you would simply make sure to activate the stapling when you are creating a site of the templates you require. Once you have this you can ...
Just to follow on from James' answer. You could create a "singleton" list (a list with one item) in the site template. That list an have configuration information such as master page name. Your web provisioning provider could read this list item, do what it needs to then deletes the list from the site. Mark.
I love these puzzles :) I think one way to do it (first way that comes to mind) is a custom Provisioning Provider for each template type (you specify this in the WebTemp...xml file) - you'll need one class per web template to set the masterpage after the ApplyWebTemplate() method call. I don't think there's a way to pass the Provisioning Provider any ...
Starter Master Pages is a great resource for learning about SharePoint 2010 master pages and a good starting point for SharePoint 2010 branding projects From _starter_publishing.master <!-- s4-ca is the main body div --> <div class="s4-ca"> <div class="s4-notdlg"> <!-- links for I like it and Tags and Notes ...
To make a custom master page I recommend you to start from the V4. Make sure that you don't delete any content place holder from the original master. If you don't want to use some of them on your custom master you should hide it through CSS.
Make sure you've enabled Publishing Feature for both Site Collection and Site. Under Look and Feel > Click Navigation Make sure Show Subsites is checked and Structured Navigation is selected for Global Navigation. In your custom master page find the code <SharePoint:AspMenu ID="TopNavigationMenu" Runat="server" EnableViewState="false" ...
Can you check to see what the minified masterpage is inheriting from? Is the codebehind set for that masterpage correct?
Top 50 recent answers are included