Posted by franz on January 24, 2012 at 7:28pm
8 followers
Jump to:
| Project: | editablefields |
| Version: | 7.x-1.0-alpha2 |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
I needed a rule to fire anytime a certain field is changed. The usual approach with Rules is to fire on "Content changed" and compare the field values to check if they changed. However, Editable Fields doesn't call the node_save() sequence.
I think proper support would be to have a Rules event to fire anytime a field is updated.
Comments
#1
+1. I agree with Fabian
#2
I think you meant Franz, Fabian is Fabianx
#3
+1 but does anyone know of current workarounds to this problem? Perhaps a hook that triggers node_save() in the background via the AJAX request?
#4
I am currently firing off lots of rules on "After updating existing content" via an Editablefield and comparing the node-unchanged and node. Are you folks not able to get this to work? This is with dev.
#5
I tried with 7.x-1.x-dev . After updating existing content does not trigger with editable fields.
The field is a list for selecting a simple yes or no.
The action I use is page redirect for testing. This does not work for me.
Can you please help me with this. How actually are you using it with the comparisons
#6
Test this with a different action to confirm that your action settings aren't at fault. I made a simple rule just now triggered off of an update to existing content and a single condition (that it was of a certain content type). The action I used for testing was to send me an email. Toggling both an autocomplete field as well as a text select list seemed to trigger fine.
#7
Thanks for the reply.
I did a simple 'set data value' as the action, and yes it did trigger it. I also tried with 'send an email'.
The problem I faced is that this rule is triggered after moving away from the page or page reload.
I guess this is how it is supposed to work.
What I require was to trigger the rule as and when the field was saved on the same page for my workflow to work. Please help if you think i am missing something here.
#8
If I'm understanding what you are saying: You are trying to change one field's value and cause it to update the value of another field in the node that you are viewing?
If so, the rule is actually triggered immediately. Your action is only noticeable on a page reload because the 'set data value' doesn't asynchronously refresh the field on the page you are viewing. You could, of course, refresh the whole page with a rules action but that's probably not what you're after. Nor can I think of a good way of doing this without custom javascript.