SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Morning all,

I'm using SharePoint 2007 Standard SP3

I'm interested in getting some opinions on the best way to surface content from one part of a SharePoint 2007 site collection into another. I have four document libraries within a child site that I want to surface on a sibling but the limitations of the CQWP prevent me from doing so. I believe this is because it's not within the same part of the tree.

So, I'd like to get an wider idea of whay my options are, when it comes to presenting content from one sibling within another, so that I can avoid content duplication.

Many thanks, Steven

share|improve this question

In the past I have used third party solutions (such as Bamboo cross-site web part) to expose information across site collections in MOSS.

You could use custom code as well to expose this information if you have this option (though it will take a while). For example a custom web part to display documents from another site collection.

Another option is to build a vanilla web part page in the original site collection with the document library list view web part, then embed it as an iframe into another page on the destination site collection. This will work best if the two site collections are in the same web application (to prevent cross-site issues). You may have to do some fiddling to make it display correctly (for example removing nav/headings from the embedded page).


(put this content as a CEWP in MyNewPage.aspx):

<iframe src="">
share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.