Merge with subscriptions, notifications or comment_notify ?
ezra-g - July 6, 2008 - 17:17
| Project: | Comment Dialogue |
| Version: | 5.x-1.1 |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | by design |
Jump to:
Description
Drupal already has the subscriptions, notifications and comment_notify modules. Perhaps this module should be merged as a feature to one of those modules. If not, could you please address why not?
Thanks!
#1
although I haven't installed this module yet, it may be exactly what I'm looking for.
The problem with 'comment notify' is that you cannot restrict per node type.
I have organic groups and I don't want to activate 'comment notify' on those nodes, it looks like this module might do the trick.
Will comment back once I've tested,
J
#2
That sounds like a feature request, not a requirement for an entirely new module.
@peashooter: As you know, the maintainer of comment_notify has approved this as a reasonable feature request: #264584: Limit Comment Notify to Certain Node Types.
#3
Comment Dialogue was required by a client to manage comment notification between an editor (or group of editors) and a writer. Rather than me justify why my client needs this, I might ask you to show me another module or group of modules which can accomplish the following:
* Selected roles are notified when the node author comments, the node author is notified when anyone else comments. We do not want blind notification to _everyone_ on comments, only the proper parties.
* Selected roles are notified without ever having to subscribe to nodes. That's part of the editors' job, as specified by their role, to manage communication with other roles, namely writers.
* Writers should not have to subscribe to their own nodes and further, should not be able to "turn off" notification. This is not a public-facing _community site_, where notification preferences are nice to have. This is Drupal being used to solve business workflow issues, where notification is not optional.
While I understand your comments about module proliferation, I believe you might possibly be biased towards Drupal-as-community-portal rather than Drupal-as-business-tool. This module is addressed towards the latter use.
#4