Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
"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.
Comment | File | Size | Author |
---|---|---|---|
OG content notification.png | 42.51 KB | mefisto75 |
Comments
Comment #1
trumanru CreditAttribution: trumanru commentedHave same problem with next release candidate version of Rules module (RC2)
Organic groups version: 7.x-1.1
Maybe it's organic groups problem?
Comment #2
fagoPlease 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.
Comment #3
Stalski CreditAttribution: Stalski commented7.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?
Comment #4
Energyblazar CreditAttribution: Energyblazar commentedsame 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
Comment #5
mitchell CreditAttribution: mitchell commentedThis is an OG bug.
Comment #6
mossy2100 CreditAttribution: mossy2100 commentedThe 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?
Comment #7
shushu CreditAttribution: shushu commentedCouldn't reproduce.
Please verify it can be reproduced on 7.x-2.x-dev, and please export the rule.
Comment #8
David_Rothstein CreditAttribution: David_Rothstein at Tag1 Consulting commentedThis 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.
Comment #9
feldmarv CreditAttribution: feldmarv commentedI 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.