Tag Info

New answers tagged

3

Use GLOBAL as TemplateName. <?xml version="1.0" encoding="utf-8"?> <Elements xmlns="http://schemas.microsoft.com/sharepoint/"> <FeatureSiteTemplateAssociation Id="{464b78de-c14e-4c88-bd52-00136fc899f4}" TemplateName="GLOBAL" /> </Elements> See Feature/Site Template Association


0

OK, here is how I did it. I wanted the Folder Settings in the Library Settings to default to "No" instead of the OOB setting of "Yes". Steps: 1. Created an Event Receiver to set the NoCrawl to "True" 2. Create an Empty Element with a Feature Scoped to Site. Event Receiver: Imports Microsoft.SharePoint.Utilities Imports ...


0

It's not possible to create site collection scoped event receivers. What you need is "Feature Stapling". You can connect a site or web scoped feature to a certain site template. So in your case you create a site scoped feature that contains the code to manipulate the home page of the root web. If you also want to activate that kind of modifications on all ...


0

I think you create an event receiver scoped to Web Events and fire it when A Site is being provisioned and A site was provisioned. How to Attach an Event Receiver to the Web Added Event And For What Purpose How to: Programmatically Activate a Feature


-1

You can disable it from the advanced setting of the list. Or if via CSS you can simply hide the button: #Ribbon\.Documents\.New\.NewFolder-Large { display:none; } But the best solution would be to create an event receiver which denies any attempt to add a new folder based on your own logic. Take a look to this old question: Prevent folder creation



Top 50 recent answers are included