1

I have a site template that we use for creating Project Workspaces. The template was developed by another person who has now left the Company. It was working fine until I was doing some work on external sharing, and realized I had to deactivate the ViewFormPagesLockDown feature in order to be able to share folders externally. So I did.

Then I realized that the site template stopped working. The error Message said that it required the ViewFormPagesLockDown Feature. After downloading and inspecting the wsp for the site template, I can see that it indeed lists this feature (ID="{7c637b23-06c4-472d-9a9a-7c175762c5c4}") in the ONet.xml file. The problem is that I have no idea why.

I cannot activate the feature, because it prevents folder sharing. I will probably end up creating a New site template from scratch and hope that this feature is not required. But I would very much like to know why and how this feature is added to the requirements of the site template, and if possible, how to remove it.

4
  • After fiddling around a bit, I might have found the answer. I activated the feature, created a New, empty sub site from the site template. Then I deactivated the feature, and saved the site as a New site template. After the inspecting the New site template, the lockdown feature is gone. So it looks like it includes the features already activated as required when creating a New site template. I find this a bit strange, because then there is no way to actually know which features are required, it just assumes that all features are required. – Thorvald Bøe Jan 23 '15 at 15:18
  • How did you disable ViewFormPagesLockDown Feature in SPO? – user41496 Apr 17 '15 at 2:26
  • Site settings/site actions/manage site features. That particular feature is only available in Publishing sites. – Thorvald Bøe Apr 20 '15 at 8:54
  • 1
    Correct location is Site Settings/Site Action/Manage Site Collection Features – Jussi Palo Jan 15 '18 at 15:24
1

As described in the Comment, it seems like all features that are active at the time of creation of the template will be required. So to fix it, deactivate the feature and create a New site template.

0

If you have the subsite of the template, you can just save it again as template, and the new template should work.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.