Exposing RSS feed links to CCK

Events happening in the community are now at Drupal community events on www.drupal.org.
jimsmith's picture

I hate to double post, but I posted the following in the Drupal forum and got no responses. Perhaps this is a better place. Then again, maybe my post didn't make any sense. At that risk I'm posting here...

Moshe Weitzman's fantastic description of the New York Observer was a real eye-opener for me. In particular, his description of using a CCK node type to build home and channel pages got me to think about how I could use that method in a project I'm about to start.

However, for that idea to work for me I need to put a twist on it.

Moshe describes how a collection of nodereference fields is used to select the nodes that will appear in the home or channel page. What I'd like to do is similar to that, but instead of selecting from nodes, I want to select from stories published on another site.

In other words, I want to be able to select from individual stories that appear in an RSS feed.

I presume this is doable by exposing the output of an aggregator feed to CCK. I've searched through the CCK project pages and forums but I haven't found anyone doing something like this.

Has anyone tried it? Any ideas how to do it?

Comments

not exist

moshe weitzman's picture

nothing like that exists AFAIK. neat.

modules do exist that turn incoming feed items into nodes. thats a bit heavyweight, but would solve your node ref problem.

I've played around with that, but...

jimsmith's picture

What I found was nodereference linked to the node's URL and not original story's URL. Still, there may be a way to code around that since the node contains the originating URL.

But you're right, it is a heavyweight way to go. I'd be loading up my site with nodes I'm not using just to get access to a few. Even by putting a limit to how long those nodes live would be inefficient.

Content Construction Kit (CCK)

Group organizers

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds: