"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

YesCT’s picture

Project: Rules » Content Construction Kit (CCK)
Version: 6.x-1.0-rc1 » 6.x-2.2
Component: Rules Engine » Rules Integration

what 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?

YesCT’s picture

If 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!

YesCT’s picture

amitaibu’s picture

YesCT’s picture

Title: "field has changed" condition evaluates to true even if the field has not changed (cck test field) » "field has changed" condition evaluates to true even if the field has not changed (cck text field)
YesCT’s picture

re #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.

fago’s picture

I 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.

fago’s picture

Status: Active » Fixed

I just gave this a test with a usual CCK textfield too - it seems to work fine now.

YesCT’s picture

Ah, fantastic. I'll try it! Thanks fago!

YesCT’s picture

This worked like a charm. Just rocking awesome! Thanks. :)

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.