Comments on: Provisioning Content Query Web Part querying subsites in a structured and repeatable way

By: Jeff angama

Jeff angama — Mon, 27 Jun 2011 12:39:56 +0000

Thanks you for the great article. It really helped me. But I had a problem with I tried to integrate a content query webpart in the onet.xml.

I solved it and published a post about it
http://jeff-sharepoint-note.blogspot.com/2011/06/create-content-query-webpart-in-site.html

By: LOVE_MOSS_NOT

LOVE_MOSS_NOT — Mon, 28 Dec 2009 16:37:36 +0000

Thank you! really helpful.

As always, pulling my hair with this wonderful and powerful product.

By: Waldek Mastykarz

Waldek Mastykarz — Wed, 14 Oct 2009 04:28:57 +0000

@Mohamed: While you could base your provisioning process fully upon ONET.XML, it has some serious drawbacks.
First of all you would have to define in ONET.XML ALL the different Site Definitions. As working with ONET.XML isn't easy, it would take a lot of time to do it. Additionally you cannot really debug ONET.XML: it either works or doesn't. And if it breaks the ULS log is the only place where you can look for errors.
Then ONET.XML is not updateable: according to the SharePoint SDK modifying a Site Definition after instances of it have been provisioned is not supported.

By: Mohamed Hachem

Mohamed Hachem — Tue, 13 Oct 2009 20:18:48 +0000

Actually, when using onet.xml file for deploying solution. if you put the webpart within module and set WebUrl property to ~site top level url will be returned dynamically.

It is not the case when you add webpart mannually or you deploy it using wsp builder because only the module context allow for the interpretation of the top level url.

Since I am using onet.xml it is an awsome solution hope that other people will use

By: Waldek Mastykarz

Waldek Mastykarz — Thu, 04 Dec 2008 19:03:34 +0000

@Paul: As I've mentioned I've used the token inside ONET.XML. That's where the web part is being provisioned. From what you're saying you've been trying to use the token within the CQWP deployed as a web control. I don't think it will work as the token is being replaced during the deployment and not on run-time.

By: Paul Brown

Paul Brown — Thu, 04 Dec 2008 16:49:20 +0000

That doesn't make as much sense as it should, as my pseudo-markup's been removed. It should say something like the webpart has in its XML in the page layout -

[ PublishingWebControls:ContentByQueryWebPart ... WebUrl="~Site" ... ]
Other stuff here
[/PublishingWebControls:ContentByQueryWebPart]

By: Paul Brown

Paul Brown — Thu, 04 Dec 2008 16:27:51 +0000

Humm – this doesn't work for me, which is a pity as it looked a very promising solution to a problem I'm having.

Of course the chances are that I'm doing something wrong, but if I understand you correctly this is a fairly simple concept.

I edited my .webpart as per your screenshot above to have '~Site' as the WebUrl, which when it's imported into my layout becomes
Other stuff here

The trouble is, in my output page, I get nothing. If I then replace WebUrl="/MYSUBSITE" then it works as expected (except my layout is then hard coded to a specific subsite, i.e. the problem I'm trying to get around.

Is there something obvious I'm missing?

By: Waldek Mastykarz

Waldek Mastykarz — Sat, 08 Nov 2008 13:50:16 +0000

Thanks for the link, Jeremy :)

By: Jeremy Thake

Jeremy Thake — Sat, 08 Nov 2008 05:56:16 +0000

I have written a series and one of the parts goes into detail on how to provision a CQWP via API code in a Feature
http://wss.made4the.net/archive/2008/06/07/solution-development-in-sharepoint-2007-part-5.aspx