rules integration
mansspams - July 26, 2009 - 01:41
| Project: | Activity |
| Version: | 6.x-2.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
Rules has become very important module and advanced workflows can be built on it. A simple integration could save a lot of time and effort for you, as Activity maintainers. If you create simple action for Rules that feeds event to Activity module, your hands will be free from maintainig large parts of Activity module and it would provide greater freedom for users.
Best part? Jobs is done for you. There is already action that feeds token formated strings to wachdog. People may see flagging, node referencing and all kind of new info on Activity feed.
#1
Activity2 is built upon triggers, although it's extended as triggers did not fulfill all of our needs, which is also why Rules came about originally I think. So the basic framework to integrate them is definitely there, it would just need tested by someone and the actual integration figured out. We're definitely open to it, just do not have the bandwidth or need ourselves.
#2
subscribe. Rules have more options for fine tuning and will be so great when activity switch from triggers to rules.
#2
I remain HIGHLY skeptical.
How so, what could be replaced in Activity with Rules? The templating? Does Rules have stuff that works with Token (the watchdog uses t() for its formated strings)? Does this integration require that the variables be stored alongside the message (/me cringes)?
What find tuning is missing currently in Activity2 ?
#3
Hey everyone,
I'd love to see some Rules integration, but without affecting the basic architecture of Activity 2, which I think is already very sound (and is a big advantage of this module).
The added functionality that Rules gives is a lot of support for conditionals: for instance, you can trigger an action based on the value of a CCK field, by comparing two different CCK fields, by checking the path, or by straight PHP code. So Rules could make it possible to record an Activity (or NOT record an activity) based on whether data on a particular node matches a wide variety of pre-defined conditions -- all without any hand-coding. I think this is what the poster in #2 means by "fine tuning."
So I'd like to see a much more simple integration with Rules than previous posts on this thread. For instance, Activity module could provide a simple Rules action that merely records a message to Activity's log. This way, you wouldn't have to mess with the terrific and amazing work that has already been done on this module, yet others could additionally inject certain Rules triggers/events as needed.
Thoughts?
Thanks,
Ben