1) Created a Team Site Site Collection and enabled the Publishing Infrastructre (Site Collection and Site).
2) Through SharePoint Designer uploaded a Custom Master Page and Preview file (Actually just copied and renamed a similar one).
3) Added the entries to the Composed Looks Table under Site Settings–Also referenced an image in the Composed Looks.
4) Changed the Composed Look to the new Composed Look.
5) Created a new Team Site subsite.
(Had the traditional blue and white with flashy web part.)
6) Activated the the Site Publishing Infrastructure.
(The Site changed to my inherited Custom Look. This surprized me since I didn’t think Custom Looks was inheritable.)
7) For the heck of it, changed the subsite to another Custom Look.
(Not surprizing was that my new Custom Look from the Site Collection was not present to be reselected.)
8) Stumped out how I would even restore the subsite to the Custom Master Page.
(Was able to reinherit the Custom Look.)
What am I missing to be able to control the Custom Look on my subsite?
I’m pretty sure if I copy my Custom Master and Custom Preview File and setup my Composed Look Table on the subsite–All would be well in CustomLooksLand–I’ll do this today. (Thanks for the suggestion)
I still don’t like the way this works: Custom Looks is kind of Inheritable –but not Inheritable.
I did not get any of that point from your post sorry, it was too unclear that the issue was with publishing.
Go to Site Settings > Master Page and choose the option on how you want the theme to be inherited.
Sorry about that 🙂
Thanks I just wanted to confirm it wasn’t me. It does suck.
I’ve seen this before, where when I modify the built-in looks, subsites do not inherit, and I cannot select a look even if it has been saved in the table mentioned on the parent site.Â
It seems that the default behavior with publishing is to inherit from the parent, but once changed, you cannot revert. This sucks because even if you have that look saved in the parent sites looks table, you cannot select from it. In fact, the only way I was able to “revert” was using the back button to go back and use the one it inherited.Â
I think they may have instituted this to keep that custom looks table from becoming massive when users create a new look for subsites of subsites of subsites. I do think they should have created a “master” look table or at least given the option to store to the look library– which maybe they have but I don’t see it.
That is the start middle and beginning of custom looks.
If you want more I recommend branding sp2013 by Randy Drisgill
http://www.amazon.com/SharePoint-2013-Branding-Interface-Design/dp/…
<update>
Also making it that feature means you can activate it on the subsites making it easier to deploy 🙂
