CommentFileSizeAuthor
#3 2.JPG42.4 KBmohsenzahra
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Sknight17’s picture

Sknight17 CreditAttribution: Sknight17 commented
Component: Rules Core » Rules Engine
Category: bug » feature
Status: Active » Closed (works as designed)

Ah, no bug to fix. You have to check to see if the entity has the field. After it checks, it then becomes available for use. Answer found at http://groups.drupal.org/node/177919

I should have thought of that :P

mjcarter’s picture

mjcarter CreditAttribution: mjcarter commented
Component: Rules Engine » Rules Core
Issue summary: View changes
Status: Closed (works as designed) » Active

I'm having this issue with Condition Set (OR). Adding a condition "entity has field" does nothing (and would break the logic of the condition set anyway). With Condition Set (AND) using "entity has field" exposes it, but not with (OR).

mohsenzahra’s picture

mohsenzahra CreditAttribution: mohsenzahra commented
Issue summary: View changes
FileSize
2.JPG42.4 KB

I myself have the same issue.

TR’s picture

TR CreditAttribution: TR commented
Status: Active » Closed (works as designed)

#2 The AND, OR, and NOT conditions are sufficient to create any logic expression, however complicated. Without knowing exactly what you want to do, I can't give an example that would work in your case, but you could certainly move the "Entity has field" out of the OR condition so that the field is available inside the OR. Or you can change (A OR B) into NOT(NOT A AND NOT B) since that is equivalent. I don't see any indication that something is wrong here.

#3 doesn't give enough information - I only see "Site" in the data selector, but whether that's correct or not I can't tell because I know nothing about the event so I don't know what is supposed to be in the context.

Restoring this to "Work's as designed" as set by the original poster in #1.