Postponed
Project:
Rules
Version:
7.x-2.x-dev
Component:
Documentation
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
19 Apr 2012 at 09:33 UTC
Updated:
17 Oct 2019 at 22:09 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #0.0
radoo commentedevents conditions actions
Comment #0.1
radoo commenteddoesn't
Comment #1
mitchell commentedIf you're comparing the entered data, then you need 'text comparison', not 'data comparison'. It's kinda confusing, so assigning myself to update that in the docs, or something later on.
Comment #1.0
mitchell commentedequals yes
Comment #2
kattia commentedI have the same issue, does anyone have a solution?
Comment #3
neorg commentedPffff.... It took me tree days to find out what the problem is and how to deal with it.
If I drill down to the field by using the Data Selector the Data Compare fails.
If I use the direct input method and fill in the right field the Data Compare succeeds.
Some notes:
This is a part of the rule while using the Data Selector to get to the field "profile2-unchanged:user:profile-outlet:field-shopname"
This method fails!!
This is part of the rule export when I use de Direct input method and I past the field [profile2-unchanged:field-shopname] directly in the Data Value field
This method works!!
I am happy that I can finally can use rules now with this workaround, but I still think this is a bug in Profiles2
Comment #4
Stephan Barrett commentedneorg, I've not been able to get this to work for me based on your method above. Anyone else have any luck here?
Comment #5
tr commented@mitchell - did you ever write up that documentation? Still have plans to do that?
Comment #6
tr commented@mitchell - did you ever write up that documentation? Still have plans to do that?
Comment #7
tr commentedNot a bug, but still needs to be documented.