Visual How-To: Customizing Content Query Web Parts by Using Custom Properties in Office SharePoint Server 2007

Free People Searches » Visual How-To: Customizing Content Query Web Parts by Using Custom Properties in Office SharePoint Server 2007

Thu, 06 Dec 2007 01:13:32 GMT

PingBack from http://www.absolutely-people-search.info/?p=3509

re: Visual How-To: Customizing Content Query Web Parts by Using Custom Properties in Office SharePoint Server 2007

Rick Mason — Thu, 13 Dec 2007 01:28:56 GMT

Hi George

We're using the CQWP to aggregate content from around our WCM-based website onto our home page. Or at least, we were. After a couple of weeks of live content we discovered that the CQWP was aggregating content from some sites, but not from others, so we had to abandon it in favour of a rich text box and manual links.

I looked into the problem and found that it was definitely related to the site rather than to the content being queried. It was possible to take a page of content which the CQWP did pick up, move it to a different site using the Site Content and Structure tool, and find that it was no longer picked up. Move it back to the original site, or to any other site the CQWP recognised, and it worked again.

The query was for WCM pages of a given content type where a text field contained a specific term. The content types of the pages being returned were children of the content type the CQWP was looking for. The text field was being used for tagging - for example, we would put "homenew" in the text field to have a page appear in the "What's new" list on our home page.

Also, we were using the CQWP as a control placed directly on a page layout, not in a web part zone. This was to avoid the unnecessary tables rendered by web part zones.

Any idea what might have caused this problem?

re: Visual How-To: Customizing Content Query Web Parts by Using Custom Properties in Office SharePoint Server 2007

ecmblog — Sat, 23 Feb 2008 02:16:30 GMT

Sorry for the very late reply. It's possible that the list or library where you moved your item didn't have the field that you used for tagging, which meant the query didn't include that item anymore. It's also possible the item's content type wasn't available in the target list or library, which may translate into not all columns being available or accessible.

If you go to View Properties of the item after it's moved, you should be able to see what fields are available.