7

On the site collection level, the SharePoint Publishing Infrastructure Feature needs to be active, and on the web level, SharePoint Server Publishing needs to be active. If not, you are not allowed to change master page.


7

Users with read permission doesn't have the right to read files and documents in draft mode and minor versions. Users with contribute permission level can see draft mode and minor versions. That's why you need to publish files before visitors (with read permission only) can access the updated major version (1.0, 2.0, 3.0 and so on). If you don't have a ...


4

Is Microsoft still committed to SharePoint Designer? - They are committed to it being supported for SharePoint 2016 and SharePoint Online. There will be no new version of SPD coming out in the future. I heard there would be no SPD 2016? - Correct, but SPD2013 works with SP2016. Anybody creating design packages for SPO with something other than SPD? - ...


4

SharePoint Designer 2013 works very well for SharePoint Server 2016 and SharePoint Online. And you can continue to use your old branding techniques, if you like. And it really depends of what you're trying to do. You can use Theming by uploading a custom *.spcolor file. You can generate the spcolor-file by using the free SharePoint Color Palette Tool. When ...


4

Hey there I see you've tagged this question with "sharepoint-online". Are you sure customizing the MasterPage is an investment you want to make? Publishing sites as we knew it are pretty much obsolete when communication sites are rolled out. When you're still on-premises it makes a bit more sense. That said, if you want to have a custom MasterPage you can ...


3

If I where you, I would try to ignore that warning and replace <div class="ms-rtestate-field">Page Content field value. Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. ...


3

reference Search for ID="PlaceHolderTopNavbar" Bring the Sharepoint:AspMenu control outside of this placeholder and delete asp:ContentPlaceHolder tag


3

Best Practice is to not do it - as Microsoft doesn't support it. "In SharePoint 2013 you cannot uninstall an imported design package, and you should never attempt to deactivate a design package through the solution gallery. If you do, page layout content types are removed and users may not be able to create subsites" Reference: http://msdn.microsoft.com/...


3

Add New Item and add Sharepoint/Office Module type in project Add the Folders and Files to the Module In the elements file use this format:- <?xml version="1.0" encoding="utf-8"?> <Elements xmlns="http://schemas.microsoft.com/sharepoint/"> <Module Name="Scripts" Url="Style Library/Scripts"> <File Path="DataTableAssets\Scripts\jquery....


3

The distinction between the system master page (aka "default master page" in SharePoint Designer, aka MasterUrl in the C# API) and the site master page (aka "custom master page" in SharePoint Designer, aka CustomMasterUrl in the C# API) only appears for publishing sites. In a team site, only the system master page is taken into account for both the site ...


3

When I started with branding, followed these steps and found these blogs to be invaluable: Step 1: - Design a good master page, i.e. an HTML page which will be converted to master page, follow this blog. Step 2: - Follow this blog for example on layouts which you will have to create for a master page: I hope that will prove to be helpful for you as well.


2

Did you change any attributes inside SharePoint:AspMenu ? Try setting StaticDisplayLevels="3" and MaximumDynamicDisplayLevels="1" inside your generated HTML for the master. Or, in the Design manager, in snippet's settings, you could set the same settings according to the sceenshot:


2

Seems that the list view webpart is missing from your welcomepage. SharePoint has a specific webpart for showing the document set content, the content of the .dwp that is used when provisioning OOTB is: <?xml version="1.0" encoding="utf-8" ?> <WebPart xmlns="http://schemas.microsoft.com/WebPart/v2"> <Assembly>Microsoft.Office....


2

Issue in my case seems to occur when you create new content type based on page content type but don't add any custom columns to the content type. Once you add one additional custom column to the content type in addition to Page content type default columns issue is gone.


2

go to Site Settings>Design Manager>Edit Master Pages and make sure the master page is published. Look at the Approval Status column. If it says Draft then your master page is not published yet. Publish a major version and the status will change to Approved. To publish a major version click the ellipsis (...) then click it again in the pop-up window and ...


2

You need to use <MS> and <ME> tags which denote the beginning and end of a SharePoint control or a snippet. The <SPM> tag ("SharePoint markup") which you have used actually is used for registering a SharePoint namespace. So, the code should be: <!--MS:<SharePoint:CssRegistration ID="CssRegistration3" Name="<% $SPUrl:~...


2

Design Manager (feature which enables HTML to masterpage conversion) is not available in Team Sites as it requires Sharepoint Server Publishing feature to be enabled. If you want to enable it: Open Site Settings, Click on "Site collection features" under Site Collection Administration. This will open Site Collection Features page. Search for "SharePoint ...


2

In SharePoint 2013, you have the flexibility to use HTML file to edit the master page and it will be converted to .master file automatically. That means you can edit the .html version of master page in any Editor (Text editor or Html editor like Notepad++, Dreamweaver, Visual Studio etc.). During editing you can place different SharePoint controls on ...


2

You can use Sharepoint Designer. Copy one of the existing Sharepoint masterpages to start from. Connect to site using SP Designer or Map network drive to site and edit files in your favorite IDE. More on SP F Branding here: http://social.technet.microsoft.com/Forums/sharepoint/en-US/82d56cc6-a15f-4dfd-b190-eb074393893a/sharepoint-2013-foundation-editing-...


2

To get the snippets you must have the design file (HTML file) and these snippets should be copied to only .html files but not .aspx files. You can create a page layout from the Deisgn Manager -> Edit Page Layouts -> Create a page layout option. This comes with design file.


2

my references are changecase blog sharepointexperience blog which gave me useful info. And do yourself a favour and try to do it WITHOUT SharePoint-Designer because "SPD" is crap and buggy :-/


2

It's a matter of opinion and requirements of course, but at it's current state i would say the modern pages are more than ready to be used in production sites. You can customize them as you've discovered, with SharePoint Framework, and you can apply a theme as a part of a site design. The classic look will be a thing of the past at some point, so my clear ...


1

Based on your attached article it's a normal behavior for your changes to be applied for all site collection and all subsites. This is Because of you have changed the master page of your site collection then apply this for all subsite as the author mentioned in his article. To let it work for a specific subsite you should do the following : Try to copy ...


1

I think you tried to edit your webpart page in Normal Mode, not Advanced Mode. To Edit it in Advanced mode . Open your Web Part Page > From the above ribbon click on Home > Click on Advanced Mode. Now you can continue your tutorial , by adding Empty data view Within ZoneTemplate tag as shown below


1

The link explains only to place how you can place the dynamic Web Part zone in that page layout. Once you save and select that page layout in any of your publishing page, you will be able to add a web part in edit page section. Read this article. If you want to place your custom static Web Part zone in page layout, Though there are different ways to do ...


1

Once I had the same issue with my SharePoint 2013 sub site. So I had to set the theme again, that way it helped me. I know it is weird issue but saved my day. You should try that too. The only thing problematic here is the theme CSS file. Don't know why that CSS file is not being found. Hope this helps!


1

SharePoint pages are, by default, associated with site definition files. When a master page is customized in SharePoint Designer, it is no longer associated with the site definition. This can result in additional administrative work following future updates or upgrades to SharePoint, which is why you see this message. You can always reset the master page to ...


1

Ultimately these snippets are basically just for preview purposes - they would not change the actual server side rendering of the final components! You could change various settings, but mainly styling via CSS (http://msdn.microsoft.com/en-us/library/office/dn205275.aspx) but this won't affect the final results. Exactly for the Metadata publishing field (...


Only top voted, non community-wiki answers of a minimum length are eligible