New answers tagged

0

For detailed information you can refer this link


2

Site features (here site means "site collection", while web means root-site/sub-site) can only be activated at a site-collection level (i.e. from the root-site of a collection, under the "Site collection features" page). Site features produce their effects on the entire site collection. For instance: If it contains a custom action, the custom action is ...


-1

It requires SharePoint 2013 Enterprise version to have those web parts available.


0

Yes, they get created when you save the site as a template. Try using SharePoint client browser and get the Feature ID, then use PowerShell to delete/remove them using -Force attribute. You can also retrieve feature id from the Site settings page. Site Settings > Site Collection Administration > Site collection features Then use FireBug/IE ...


0

Firstly I agree with @Aveenav that you should look into the building wsp package, that will follow Sharepoint model, it will place the master page in layouts directory, push it if you connect servers etc. But if you really need to, you can place in the SP library, and call it from there (you can place in the layouts as well but you will have to keep that ...


-1

Try: {your site}/_layouts/15/ChangeSiteMasterPage.aspx Amal's answer didn't have the 15 in it. I don't have enough rep to add a comment to his solution.


0

Instead of using PowerShell, create a WSP package and hookup and event receiver for the feature that sets the master page. That way you can apply same master page to sub sites.


0

Try appending URL /_layouts/changesitemasterpage.aspx



Top 50 recent answers are included