It would be nice if the Node Expire was able to expire nodes based on other fields, eg. With events then it would be nice to have the node expire a specified number of days/weeks... after the end date of the event.

It would also be nice if it was able to run an "Action" from the action module when this happened, so that the node was not just "unpublished" but could then perform any action at the expiration time.

Geoffrey

Comments

astoltz’s picture

I don't understand the first part of your request. What other fields might you want to base the expiration off of? I had plans of adding a new expiration type "Expire After Last Selected Update" which would require the user to state that the module has been updated to update the expiration time. This is essentially the difference (according to its author) between this module and the "Auto Expire" module. (The Drupal policies and such state its a better idea to make 1 really good module than 2 lower end ones. I'm all for this idea too.)

As far as the actions module goes: I'll look into this type of thing. I haven't used Drupal 6 very much and haven't really used the Actions module. Since it's bundled in with Drupal 6 now I can see this at least being a possibility.

ksenzee’s picture

> What other fields might you want to base the expiration off of?

A CCK date field would be nifty. :)

sza’s picture

exactly! :)

doc2@drupalfr.org’s picture

With a specific date field... would be just great!

sszalla’s picture

+1 on that!

raplom’s picture

It's been a few months but I'd also have a use for node_expire based on a CCK date field.

petergrob’s picture

Is there also a possibility to customize the mail with some info in the node for example %body ?

Thnx,
Peter

brmassa’s picture

Status: Active » Fixed

Guys,

the new version of this module simplified the administration of expire fields. Its not CCK, however. Take a look.

regards,

massa

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.