When creating your own site definitions you can set the ProvisionAssembly and ProvisionClass to have .NET code fired when a new site is created. your class should inherit from the SPWebProvisioningProvider class.
This is useful for example if you want to create a site hierarchy as part of the site creation. In MOSS, the Publishing [...]
Posted under Developer
This post was written by spotd on June 19, 2009
When you are creating a custom site definition you can set the ExecuteUrl of the onet.xml Project element to a site-relative URL. When users create new sites from the definition they will be sent to the ExecuteUrl instead of the home page when the site is first created.
You can use this to send your users [...]
Posted under Developer
This post was written by spotd on June 16, 2009
If you want to keep your designers on a leech you can set the DisableWebDesignFeatures in your site definition’s onet.xml file. Set the attribute in the Project element to one or more values from the following list:
wdfbackup Disable Web site backup.
wdfrestore Disable Web site restore.
wdfpackageimport Disable Web site package [...]
Posted under Developer
This post was written by spotd on April 22, 2009
When you modify any fle or page in SharePoint, for example using SharePoint Designer, that file becomes Customized. In practice, this creates a copy of the original file and stores the copy in the database along with your changes. Changes to the original source file will no longer affect your customized file.
You can revert your [...]
Posted under End User
This post was written by spotd on April 17, 2009