My customers wants the marketing folks to be notified when someone unsubscribes, so here's the patch.
| Comment | File | Size | Author |
|---|---|---|---|
| comment_notify.unsub_.patch | 3.3 KB | nancydru |
My customers wants the marketing folks to be notified when someone unsubscribes, so here's the patch.
| Comment | File | Size | Author |
|---|---|---|---|
| comment_notify.unsub_.patch | 3.3 KB | nancydru |
Comments
Comment #2
gregglesThis seems like a really cool idea, but I'm not sure it makes sense to have in the core of the module.
Perhaps the best thing we should do is create some hooks for actions that happen in comment_notify so that other modules can modify it more?
I think the big points where comment_notify takes actions are
1. sending the e-mails
2. unsubscribing a user (either by them or by an admin)
Anything else where we'd want modules to be able to make modifications or take actions at those points.
Comment #3
nancydruYes, hooking the tokens so they can be altered before substitution, or to add more (which implies hooking the settings list too). This is another reason why Tokens just make sense...
If the unsub text is blank, then this feature does nothing except take up a small amount of space.
Comment #4
gregglesAfter more thought and no support for the original issue, I'm changing this to be a 7.x issue about adding more hooks to the module. Since it's pretty far afield from where we started I unassigned you, Nancy, but if you want to do the things I mentioned in #2, please take it back!