Let's say based on a CCK field "Keep", or higher than a 3 star fivestar-rating, how can I keep select nodes from expiring, while the rest are purged normally?

Is there a way to hook into the feedapi_node to override the expiration check?

Comments

aron novak’s picture

aron novak
Primary language Hungarian
Location Hungary, Budapest
commented

Unfortunately there is no clean way to do this.
Maybe you can manipulate the {feedapi_node_item}.arrived externally to save some items from the deletion ;)

Büke Beyond’s picture

Büke Beyond commented

I was thinking of sending direct queries to the feedapi_node_item table. If a record (with a nid) is removed from that table, I assume that node becomes disowned by the feed and feedapi_node.

Perhaps in the future, there can be some function calls abstracting these operations? .. feedapi_node_own($feednid, $nid, $url, $guid ....), feedapi_node_disown($nid), etc..

The nice thing in the Simplefeed module is, that there is a custom feed_item node type. This node type has the editable fields URL, expiration and Owner Feed. In feedapi, this data gets internally attached to the node, but is normally hidden from the user, and is meant to be read-only for the programmer.

I like the fact that feedapi_node can use any user defined node type. Yet, I think there must be a way for feeedapi_node to modify the feed items via hook_form_alter(), to bring these editable fields to the user, too.

I think combined with some commands (and hook handlers) for programmers, feedapi_node can really fulfill its potential.

Feedapi itself is excellent abstraction for feed parsing and plugins, but feedapi_node also needs to become extensible, so that the many benefits of having the feed items as nodes can be unleashed.