In SharePoint Online I have detected a bug that prevents the suite bar logo (configured in the o365 tenant admin center) from being rendered after applying a theme with a non-default colour scheme. The logo is not just hidden or not visible; the HTML is no longer rendered to the page at all.
NOTE: This issue has been raised with Microsoft and they have acknowledged it as a bug. They have told is that a fix is planned for June 2015 and should take a couple of weeks to reach all tenants.
I was advised last week that a fix this issue had officially started rolling out. Today I can confirm that one of our test tenants no longer exhibits this behavior! At the time of writing some of our tenants have not yet received the fix, but it is definitely rolling out and should be with you soon if not already.
When exactly is this occurring?
There is a colour scheme file that nominated as the default for each master page. Only when using this colour scheme in conjunction with the given master page will the logo be present. Specifically, only a colour scheme which is nominated as the default colour scheme will show the suite navigation logo.
This is unrelated to any customisation work and can be observed on any OOTB SharePoint Online publishing site.
The default colour scheme for a given master page is nominated within that master page’s preview file. The preview file is the one which sits alongside the master page in the master page gallery and has the same name name as the master page but with an extension of ‘.preview’ instead of ‘.master’ (e.g., seattle.preview). The first line of the contents of this file identifies the default colour scheme for the master page. When this colour scheme is applied, the theming engine assumes that the CSS is already themed appropriately and does *not* act.
I still want the logo on every page, what can we do?
- As I have said, a fix is on the way – just wait a few months!
- It is against best practice
- This approach is brittle as the suite bar is a living, changing thing – Microsoft is updating it all the time and any changes they make will likely break this functionality.
- The logo will no longer be configurable via tenant admin settings.
- We can create and use multiple master pages – one for every theme colour
- Partially defeats the purpose of master pages which is to maintain all common pages elements in a single place.
- Master pages may fall out of synch
- Adds complexity for support
I want to reproduce this myself, how do I do it?
- Create an new site collection in a tenant that has a suite navigation logo configured, using the Publishing Site template
- Note that the logo is present
- Via Site Settings, “Change the look”
- Choose the “Office” composed look
[Specifically, we want the seattle master page and colour pallette 001]
- Change the colour scheme to anything except the default
- Apply the look
- Note that the logo is no longer present
- Re-apply the theme with the default colour scheme and logo will reappear