Since the release of Microsoft Office SharePoint Server 2007 the Content Query Web Part (CQWP) has served us very well as probably the best content aggregation solution available on the SharePoint platform. And while I’ve been using it heavily for Web Content Management solutions for the last three years with great success, I got really surprised when I found out that the CQWP provided with SharePoint 2010 doesn’t work with anonymous access!
We all know Content Query Web Part (CQWP) – probably the greatest Web Part provided with SharePoint Server that allows you to build dynamic content aggregations in a matter of minutes. CQWP is known not only for its great performance but also for its flexibility and extensibility capabilities. In SharePoint Server 2010 Content Query Web Part introduces even more functionality among which the slots – a cool feature that allows you to create semantic and reusable templates. And while creating new templates became as simple as it was never before there is one thing that you should keep in mind while working with Content Query Web Part slots.
Imagine the following scenario: you created a new Content Type in SharePoint 2010. You built the Content Type ID correctly.aspx) and even included the FieldRefs element. Still, after you provisioned your Content Type it doesn’t contain any fields:
Do you still remember how many clicks did you need in Microsoft Office SharePoint Server 2007 to create a new Publishing Page? First you had to pick the New Page option from the Site Actions menu. Then you had to provide some information about the page and then finally, after pressing the OK button, you were redirected to the newly created page. SharePoint Server 2010 simplifies that process, but did you know that you can push it even further, and create new Publishing Pages with a single mouse click?