You could use content deployment (be aware of limitations) to deploy between
the two Site collections and then just use a CQWP.
You may also want to look at Sahil Malik's open source project
http://blah.winsmarts.com/2008-3-Announcing_the_release_of_SPRSS.aspx
From: ozmoss@ozmoss.com [mailto:ozm...@ozmoss.com] On Behalf Of Paul Noone
Sent: Friday, January 16, 2009 1:59 PM
To: ozmoss@ozmoss.com
Subject: RE: RSS for articles pages from Intranet to Public-Facing site
They're separate farms. Is that still do-able?
Any reason why you'd use CQWP over RSS?
This is all hypothetical at the moment as I can't test anything until the new
farm is up.
Regards,
Paul
From: ozmoss@ozmoss.com [mailto:ozm...@ozmoss.com] On Behalf Of Brendan Law
Sent: Friday, 16 January 2009 3:54 PM
To: ozmoss@ozmoss.com
Subject: RE: RSS for articles pages from Intranet to Public-Facing site
What about using a content query web part to generate the RSS? You might need
to write some code on your Internet site to handle impersonation to your
Intranet site however...
- Brendan
From: ozmoss@ozmoss.com [mailto:ozm...@ozmoss.com] On Behalf Of Paul Noone
Sent: Friday, 16 January 2009 3:17 PM
To: ozmoss@ozmoss.com
Subject: RSS for articles pages from Intranet to Public-Facing site
Hi guys,
In an effort to avoid double-handling of article pages I was hoping to use an
RSS web part to display articles from our Intranet onto our public-facing site
(which has yet to be built).
Does anyone know if this is possible? It's just occurred to me that Intrant
content requires login and may not display. Although I recall reading somewhere
about syndicated content not being governed by the same permissions(?).
If this is the case, does anyone know of an easy way around this? Thoughts at
the moment are writing an event handler that triggers when a page with a
public flag is published, and then copying this to the destination library on
the public site. But this seems like overkill and results in doubling-up of
content.
Kind regards,
Paul
Support procedure: https://www.codify.com/lists/support
List address: ozmoss@ozmoss.com
Subscribe: ozmoss-subscr...@ozmoss.com
Unsubscribe: ozmoss-unsubscr...@ozmoss.com
List FAQ: http://www.codify.com/lists/ozmoss
Other lists you might want to join: http://www.codify.com/lists
This email is intended for the named recipient only. The information contained
in this message may be confidential, or commercially sensitive. If you are not
the intended recipient you must not reproduce or distribute any part of the
email, disclose its contents to any other party, or take any action in reliance
on it. If you have received this email in error, please contact the sender
immediately and please delete this message completely from any systems.
Confidentiality and legal privilege are not waived or lost by reason of
mistaken delivery to you.
Support procedure: https://www.codify.com/lists/support
List address: ozmoss@ozmoss.com
Subscribe: ozmoss-subscr...@ozmoss.com
Unsubscribe: ozmoss-unsubscr...@ozmoss.com
List FAQ: http://www.codify.com/lists/ozmoss
Other lists you might want to join: http://www.codify.com/lists
Support procedure: https://www.codify.com/lists/support
List address: ozmoss@ozmoss.com
Subscribe: ozmoss-subscr...@ozmoss.com
Unsubscribe: ozmoss-unsubscr...@ozmoss.com
List FAQ: http://www.codify.com/lists/ozmoss
Other lists you might want to join: http://www.codify.com/lists
Support procedure: http://www.codify.com/lists/support
List address: ozmoss@ozmoss.com
Subscribe: ozmoss-subscr...@ozmoss.com
Unsubscribe: ozmoss-unsubscr...@ozmoss.com
List FAQ: http://www.codify.com/lists/ozmoss
Other lists you might want to join: http://www.codify.com/lists
