Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
"field has changed" condition evaluates to true even if the field has not changed (text cck field as text field widget) when the node is saved.
but "field has changed" condition works (action occurs only if a value has actually changed) for text cck widget: check boxes/radio buttons.
Can a "diff" be added to compare the values of the text fields before and after the save?
Comments
Comment #1
YesCT CreditAttribution: YesCT commentedwhat happens if a node is saved and that node has some cck text fields? Is there a modified date stamp for the fields that is set whether or not the contents were modified?
Comment #2
YesCT CreditAttribution: YesCT commentedIf I have "Create new revision" checked in the default options for the Workflow, can I access the old value..
it might be enough to send the currect value (know the token to do that) and the old value (is there a token for that?), and the human that gets the email can look and see if the values were changed. Well, if that can be done, there should be a way to do a diff, eh?
Thanks for any ideas!
Comment #3
YesCT CreditAttribution: YesCT commentedrelated to #435400: Evaluates to True regardless of content update status ?
Comment #4
amitaibu#412058: 'field has value' condition returns wrong value - duplicate?
Comment #5
YesCT CreditAttribution: YesCT commentedComment #6
YesCT CreditAttribution: YesCT commentedre #4, I have the April 2nd (6.x-2.2) so I think it has the commit from March 30 in 412058, and my text fields are not empty (NULL), so I dont think that is it.
Does field change work for anyone for a plain text box type field? I could try it on a fresh install. And that might help eliminate any interaction with other modules (like devel or something).
Thanks Amitaibu! please keep suggesting possible duplicates! I dont know the cck queue very well.
Comment #7
fagoI don't think the mentioned issue is related.
Please try if the patch from #446390: make rules conditions more robust helps you - in my tests it worked with a textarea after the patch was applied.
Comment #8
fagoI just gave this a test with a usual CCK textfield too - it seems to work fine now.
Comment #9
YesCT CreditAttribution: YesCT commentedAh, fantastic. I'll try it! Thanks fago!
Comment #10
YesCT CreditAttribution: YesCT commentedThis worked like a charm. Just rocking awesome! Thanks. :)