I just started playing with this module, and it is really cool.
However, I was surprised to see that I'm supposed to enter any reactions inside the link configuration – the natural thing to me would be to have each configured link to show up as an event for regular reaction rules.
Thus, this is a feature request to make each Rules link show up as a separate event. (Then, of course, each Rules link should provide the entity which it is attached to as a parameter.)
Thanks for a cool module!
See also #1309444: Allow links to reuse condition sets for visibility, rather than providing their own for a discussion on making Rules Link reuse existing condition components rather than creating a new one for each link.
Comments
Comment #1
archnode commentedI second that it would be really helpful to have the attached entity as a parameter!
Comment #2
itangalo commented@archnode: The attached entity is currently a parameter – just for information.
Comment #3
archnode commentedSorry, I got something wrong. The attached entity is present as a parameter, but I wasn't able to access my custom fields.
I guess this is due to rules being unable to validate the node type in this context. A data comparison of the node type as a condition makes those fields available, though.
Would it be somehow possible (and would it make sense) to structure the rules workflow of rules_link in a way that gets you access to the custom fields right away, as that would be more logical and save a few conditions?
Comment #4
itangalo commented@archnode: I agree that would be nice, but I don't think it's possible since the links can be added to more than one entity/node type. (If it was one single entity bundle, though, it should be theoretically possible.)
Comment #5
archnode commented@Itangalo: You are right! I rest my case.
Comment #6
jurriaanroelofs commentedJust in case anyone still needs this http://drupal.org/project/rules_linkevent
works great.
Comment #7
mitchell commentedI agree completely.
Also, I think this change would take away the need for the current rule-sets method. While, they're not necessarily mutually exclusive, I don't see a reason to keep the rule-set configuration method.
I think this change also brings up other question, would the conditional display configuration still needed after this change? I asked if Rules Form Support fit the bill for adding or not adding form elements over at #1309444-6: Allow links to reuse condition sets for visibility, rather than providing their own.
#6: I tried that module, but didn't have much luck. Would you be able to help with #1491940: How to use? Provide example link and rule.? I wrote up more on this subject in #1365658: Difference with Rules link module, and basically feel that both projects have merit, yet that project is not ready to replace this one.
Comment #7.0
mitchell commentedAdded a link to #1309444, being a related issue.