Tag Info

New answers tagged

0

Got the solution Open the file "wss.xsd" at below path "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\XML" Find all xs:anyAttribute namespace="##other" processContents="lax" in the file and verify that it is the last child if not move it to the last position . see below piece of code. <xs:attribute name="PrependId" ...


0

I have used the below code to activate features with the help of CSOM. You can also try and use it, though I am not sure about its feasibility with office 365 but I'll try this and will update this answer. function ActivateFeature(featureGuid) { var clientContext = new SP.ClientContext.get_current(); var site = clientContext.get_site(); var guid = new ...


0

When publishing features (web or site collection scoped) get activated it becomes unsupported to save your site as a template. That is exactly happened in your scenario. If you want to use "save your site as a template" then don't activate publishing features on web or site collection level.


0

A site definition defines a unique SharePoint site. Site definition is a combination of multiple files like .xml, .aspx, .ascx, and .master page, .gif , .doc etc and are stored in C:\ProgramFiles\Common Files\Microsoft Shared\web server extensions\14\TEMPLATE\SiteTemplates directory. But Site Templates are created from an existing site and are stored in ...



Top 50 recent answers are included