Closed (fixed)
Project:
Workflow-ng
Version:
5.x-2.x-dev
Component:
Wng Module Integration
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
16 Jan 2008 at 08:08 UTC
Updated:
12 Apr 2009 at 23:40 UTC
Question brought up by reviewing the comment notification configuration: http://drupal.org/node/156531
This is a nice workflow, however it does not match all the functionality of the Subscriptions module, including keeping subscription preferences per user, multiple subscription types, opt-in / opt-out / auto-subscribe per node, etc.
There should be a lot of value in moving out notifications out of the Subscriptions module to use Workflow NG instead. Best use of the Subscription module would be to manage per-user/per-node settings and trigger workflow events when needed.
A possibility of integration is worth assessing.
Comments
Comment #1
fagoindeed, that sounds useful.
I think there are two possible ways to go:
1. try to rebuild subscriptions with workflow-ng
2. integrate subscriptions with workflow-ng
ad 1.
What's probably most missing here, is the possibility to have settings per user. Perhaps the core profile module can be used for this? (Is there token support for it!?) Otherwise one could also use a node profile content type for the settings, one would just need a nodeprofile load action for workflow-ng 2.x.
ad 2.:
sounds useful, in particular for cases like "I want do send out subscriptions per pm instead" or if one needs customized mail texts per role. So the module could generate a new event when a subscription should be sent. However we'd also need an option to turn the "subscription mails" of the module OF. For this way I'd suggest to file a feature request for the subscription module.
Comment #2
dkruglyak commentedI will look into this further. If we go with Option 1, the settings are actually per User, per Entity, with entity being a Node or a Blog or a Taxonomy or a Node Type. How could we create workflow events on two entities at the same time?
Comment #3
fagoWhy on two entities?
Comment #4
mitchell commentedThis is now fixed with Flag's #298109: Rules integration.