May 5, 2011 Leave a comment
During a SharePoint publishing project I was involved in, the Business said that they had a requirement for “the ability to publish manually to the Production site as required (ie: no set times or sweeps)”. In this specific scenario, they used publishing pages that contained Web Parts to display SharePoint Document Libraries.
For those of you familiar with SharePoint’s Content Deployment settings, we know that these can be scheduled to run every 15/30/45 minutes, once a day, once a week, or once a month. These deployments are either Incremental (new, changed, deleted) or Full (everything).
SharePoint also has an out-of-the-box Quick Deploy feature that allows for publishing outside of the scheduled content deployment job for specific content.
- It can be set for intervals as frequent as 10 minutes (although consider the environment and the risks of hampering server performance as the site grows)
- A SharePoint Quick Deploy group can be utilized at the Site Collection level to include particular users that will be authorized to flag content for the next Quick Deploy cycle.
However, there is a limitation to this. The native Quick Deploy mechanism works for more conventional content, such as text, images, links on a page. It will not traverse the Web Part object model, nor will it recognize changes made within Libraries/Lists (such as adding a new PDF). To remedy this, a custom publishing feature would need to be written and deployed across the environment. There is an example of a customized version of the Quick Deploy that will search Document Libraries as well as conventional content.