"OG group content notification" shows error - Error: The data type of the configured argument does not match the parameter's entity requirement.
Screenshot's attached.

CommentFileSizeAuthor
OG content notification.png42.51 KBmefisto75
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

trumanru’s picture

Version: 7.x-2.0-rc1 » 7.x-2.0-rc2
Issue tags: +rules, +Organic Groups, +OG

Have same problem with next release candidate version of Rules module (RC2)

Organic groups version: 7.x-1.1

Maybe it's organic groups problem?

fago’s picture

Please try whether update to the latest og version or rules version helps. I had this some time ago too, but it works for me now.

Stalski’s picture

7.x-1.1 gave the problem and I now upgraded to 7.x-1.3 and still the same problem.
Is there any evolution at this matter?

Energyblazar’s picture

same problem here...but it the argument still works....If one creates a group and then try creating a content belonging to that group it is created....

but still would like to know more about it.....why is that red error line appearing

mitchell’s picture

Title: OG with pre-installed Rules » 'Enity is group' condition - data type mismatch
Project: Rules » Organic groups
Version: 7.x-2.0-rc2 » 7.x-2.x-dev
Component: Provided Rules integration » OG actions

This is an OG bug.

mossy2100’s picture

The rule will only allow you to select site or node as the group content entity type.
But og_get_all_group_content_entity() only returns ['user'].
That's why these can't be made to line up. I'm not sure of the exact cause yet. Can 'user' entity type even be group content?

shushu’s picture

Issue summary: View changes
Status: Active » Postponed (maintainer needs more info)

Couldn't reproduce.
Please verify it can be reproduced on 7.x-2.x-dev, and please export the rule.

David_Rothstein’s picture

Title: 'Enity is group' condition - data type mismatch » 'Enity is group' condition - data type mismatch for the default OG New Content Notification (rules_og_new_content) rule
Status: Postponed (maintainer needs more info) » Active

This is easy to reproduce just by turning on the OG module and the Rules Admin module on a fresh installation, then going to admin/config/workflow/rules (or viewing/editing the rules_og_new_content rule itself).

It looks like it happens when the site doesn't have any content types that have a group audience field (i.e., no content types that can be created within a group).

Seems like the OG module should handle this somehow but I'm not sure there's a way to kill the rule entirely when it's not relevant for a particular site.

feldmarv’s picture

I still have this Problem Drupal 7.39, OG 7.x-2.7+43-dev one content type is associated with OG also group joining works. But Rules are blocked because of this error.