Home

Custom Masterpages and SPOL Modern UI

%3CLINGO-SUB%20id%3D%22lingo-sub-8941%22%20slang%3D%22en-US%22%3ECustom%20Masterpages%20and%20SPOL%20Modern%20UI%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-8941%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20some%20branded%20custom%20master%20pages%20in%20SPOL%2C%20and%20have%20noticed%20in%20our%20First%20Release%20tenant%20that%20we%20lose%20branding%20in%20the%20new%20%22Modern%22%20UI.%20Is%20there%20any%20guidance%20here%3F%20Anything%20we%20can%20do%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-9046%22%20slang%3D%22en-US%22%3ERe%3A%20Custom%20Masterpages%20and%20SPOL%20Modern%20UI%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-9046%22%20slang%3D%22en-US%22%3EI%20would%20also%20say%20that%20eve%20in%20classic%20view%20it's%20not%20a%20good%20idea%20to%20use%20a%20custom%20master%20page...you%20could%20do%20it%2C%20but%20you%20were%20also%20responsible%20to%20update%20your%20custom%20masterpage%20with%20any%20new%20stuff%20added%20by%20Microsoft%20to%20default%20masterpages%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-8946%22%20slang%3D%22en-US%22%3ERe%3A%20Custom%20Masterpages%20and%20SPOL%20Modern%20UI%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-8946%22%20slang%3D%22en-US%22%3E%3CP%3ENope%2C%20masterpages%20are%20essentially%20dead.%20%26nbsp%3BYou%20can%20stay%20in%20%22classic%20UI%22%20and%20keep%20using%20them%20for%20the%20time%20being.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThey%20have%20no%20guidence%20for%20how%20we%20can%20do%20any%20level%20of%20branding%20in%20modern%20UI.%20%26nbsp%3BOther%20things%20they%20are%20killing%20include%20usercustomactions%20(which%20is%20what%20we%20transitioned%20to%20to%20get%20away%20from%20master%20pages).%20%26nbsp%3BOne%20of%20our%20critical%20customizations%20is%20a%20global%20enterprise%20navigation%20injected%20into%20all%20site%20collections%20and%20all%20sites.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMuch%20much%20much%20angst%20and%20conversation%20about%20this%20in%20Yammer.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESupposedly%20new%20stuff%20coming%20down%20the%20pipe%2C%26nbsp%3Bbut%26nbsp%3Bno%20clue%20what%20it%20will%20look%20like.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Brad Morgan
Visitor

We have some branded custom master pages in SPOL, and have noticed in our First Release tenant that we lose branding in the new "Modern" UI. Is there any guidance here? Anything we can do?

2 Replies
Highlighted

Nope, masterpages are essentially dead.  You can stay in "classic UI" and keep using them for the time being.

 

They have no guidence for how we can do any level of branding in modern UI.  Other things they are killing include usercustomactions (which is what we transitioned to to get away from master pages).  One of our critical customizations is a global enterprise navigation injected into all site collections and all sites.

 

Much much much angst and conversation about this in Yammer. 

 

Supposedly new stuff coming down the pipe, but no clue what it will look like.

I would also say that eve in classic view it's not a good idea to use a custom master page...you could do it, but you were also responsible to update your custom masterpage with any new stuff added by Microsoft to default masterpages
Related Conversations