Currently, only those entity properties can be used within entity query, which are shared across all of the entity bundles. This is irritating, as the UI actually lists all properties, but when try to use them, their type remains unknown.

CommentFileSizeAuthor
#2 2058037_rules_support_all_entity_properties_entity_query_2.patch2.69 KBdasjo
#1 2058037_rules_support_all_entity_properties_entity_query.patch2.66 KBdasjo

Comments

dasjo’s picture

dasjo
he/him
Primary language German
Location Zurich
commented
Status: Active » Needs review
StatusFileSize
new 2058037_rules_support_all_entity_properties_entity_query.patch2.66 KB

The attached patch fixes the above problem. It has been tested with a boolean field that is added to only 1 node type (bundle).

dasjo’s picture

dasjo
he/him
Primary language German
Location Zurich
commented
StatusFileSize
new 2058037_rules_support_all_entity_properties_entity_query_2.patch2.69 KB

attached is a minor re-roll that makes function naming more clear & fixes the documentation code style.

fago’s picture

fago
Primary language German
Location Vienna
commented
Status: Needs review » Fixed

Thanks, committed.

Status: Fixed » Closed (fixed)

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

sportel’s picture

sportel commented
Issue summary: View changes
Status: Closed (fixed) » Needs review

This patch seems to have created a bug in all versions since 7.x-2.4. See https://drupal.org/node/2137681 for details and https://drupal.org/comment/8471281#comment-8471281 in particular. I hope someone is able to fix this (I unfortunately am not).

Thanks,

Mike.

checker’s picture

checker commented

I have reverted this patch in rules 2.6 to fix this bug. At the moment i can't find negative side effects without this patch.

travist’s picture

travist commented
Status: Needs review » Closed (fixed)

I believe this patch is correct, and that the issues you are referring to are implementation issues with the Rules configurations. Please see #2137681: Error: The data type of the configured argument does not match the parameter's value requirement. for a better explanation.

manishs’s picture

manishs commented

The issue https://www.drupal.org/node/2137681 is appearing again after this patch has been reverted. I had to downgrade to 2.3 and then it worked fine for me.

deggertsen’s picture

deggertsen commented

Just confirming that this patch is still causing this issue: #2137681: Error: The data type of the configured argument does not match the parameter's value requirement.
Do we need to set this back to "Needs work"?