There are already some blog posts on the order with wich SharePoint loads its css files. So I won't go into detail on that.
However I want to give you some info on an issue I had not long ago.
Situation
Custom Masterpage
Custom Theme on Root site
Other Custom Theme on child that touches some similar styles with other colors
Problem
The last css to get loaded was the one of the parent theme
Solution
Moving this tag
<SharePoint:Theme ID="Theme1" runat="server"/>
to be in front of
<asp:ContentPlaceHolder id="PlaceHolderAdditionalPageHead" runat="server">
</asp:ContentPlaceHolder>
More Info
I used a custom masterpage together with a theme. Because I wanted to do all css with the theme I moved the tag to just in front of the tag.
However when you configure a theme on a subsite it gets placed in the "additional page head" wich caused the above mentioned caution.
Moral
When designing your custom masterpage, think twice when moving tags .. and test test test.
Kind regards
Steven
No comments:
Post a Comment