Geek Answers Handbook

Sharepoint Foundation Home Pages on Subsidiaries

Using the Sharepoint Foundation 2010 I edited v4.master, added a link to the new CSS file, saved the changes, and did not apply them to the home site.

However, when I create a child node, it uses the old version of v4.master for some annoying reason. I vaguely know that some publishing features from SPS are not included in the SPF, so many online tips are not relevant (?)

If there is a way to make new children objects inherited by the new V4.master, I would be very grateful.

+4
source share
4 answers

This is only possible with a custom WSP or HttpModule that requires .NET code. Server versions of SharePoint can easily cope with the Masterpage option, a quick Google search for a “solution for the main page” yielded good results, including:

http://blog.thedesigndrifter.com/?p=1112

http://rickhilferink.wordpress.com/2011/01/25/creating-a-sharepoint-2010-foundation-masterpage-solution-and-automatically-activate-it-for-all-sites-and-newly-created- subsites /

+2
source

If you want to have a master page in the root of a site collection inherited by child nodes, then you better use the publishing site template.

Then you can go to: / _ Layouts / ChangeSiteMasterPage.aspx and specify your own main page and inherit it with all its children.

0
source

it's probably too late to benefit you, but perhaps it will benefit others. I found that if you did not rename the customized main page to something other than v4.master, then the subtitles do not inherit the customized version of v4.master, but instead use the original non-standard v4.master. So make sure you make a copy of v4.master and rename it. Here are a few steps from [my blog post], here's how I did it:

  • Right-click on v4.master and select 'Reset to define the site, and the original v4.master will be restored, and SPD 2010 will automatically create the v4_copy (1) .master page (screenshot 14).
  • Launch custom.master, publish the main version and approve the file
  • Go to the section "Site Actions"> "Site Settings"> "Master Pages" and select the new main page, custom.master, for both the main page of the site and the main page of the system and select the "Reset for all sub-sites for inheritance" checkbox of this alternate CSS URL (screenshot 15)
  • Now, if you forgot to activate the publishing function for a new subsidiary site with the Team site template, it still does not inherit the custom.master page, so go to "Site Actions"> "Site Settings"> "Manage Site Features" and activate the publication (screenshot 16 )
  • Once the function is activated, you will see a new main page and its styles (screenshot 17).
0
source

I solved this problem by creating a new custom site customization using Visual Studio and SharePoint Site Definition. I added a function that adds my own master page (edited with v4.master) to the gallery of the main page of the site (_catalogs / masterpage):

<Module Name="MasterPageModule" RootWebOnly="FALSE" List="116" Url="_catalogs/masterpage" > <File Url="mymasterpage.master" Path="MasterPageModule\mymasterpage.master" IgnoreIfAlreadyExists="TRUE" Type="GhostableInLibrary"> <Property Name="ContentTypeId" Value="0x010105"/> </File>

The main thing to get the same main page for all sites is to set MasterPageFile -property in Default.aspx as follows: MasterPageFile = "~ sitecollection / _catalogs / masterpage / mymasterpage.master" - this always refers to the root allocation level.

I think the same thing can be achieved using the FeatureActivated method, but in my case it did not work, I don’t know why.

0
source

More articles:


All Articles