I'm looking for a way to integrate Rules to send a reminder email on a given date. So, for example, a user creates a content type and one of the fields is an expiration date. I'd like to send them a reminder email basically saying:

"Hey! This content is expiring today! Make sure you check it out!"

I know I can set a rule to send an email X days after content creation, and I know I can run a daily cron task (but when you just run a cron task, it seems you can't run a check against all nodes of a certain content type to check if they expire that day). I just can't seem to put those two functions together.

Anyone else have this issue and (even better) perhaps a solution?

Thanks in advance!

Comments

fago’s picture

Component: Rules Core » Rules Engine

Do it like that:
>I know I can set a rule to send an email X days after content creation,

So create an rule set that takes a node argument, then once it created schedule the set to be executed on the given date. So you can use the rule set to send the mail and unpublish the node or whatever.

menoseficaz’s picture

Could you point me to directions on how to set a rule for an email to go 'x' days after content creation?

I think this is the best approach and I thought of a solution similar to this, but not sure how to implement. Thanks!

TheAlienShore’s picture

Version: 6.x-1.0-beta3 » 6.x-1.0-rc2

I'm also trying to send out an email to a user when the value of a cck date field is in the past. What is the best way to do this? I've set up a rule with Event "After creating new content" and a condition "CCK: Field has Changed" and chose my date field. But I'm only allowed to select a specific date. Is there a way to select something like "Date = less than now"? Thanks!

tahiticlic’s picture

Same need here, still no solution?

[Edit] found a solution for my problem which is a bit different since it's only a scheduled rule I need, based on node creation date...

klausi’s picture

Version: 6.x-1.0-rc2 » 6.x-1.x-dev

Check out the Rules Scheduler tutorial that deals with a similar issue: http://drupal.org/node/520012

mitchell’s picture

Status: Active » Fixed

Fixed in #5

Status: Fixed » Closed (fixed)

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