Limit group content per group [#2477283]

We have content types A, B and C, behaving like groups.
We have content type AA,BB behaving like group content.

I expected to use that "Target Bundles" box so that only A-type nodes could be selected as Audience for a new AA-type node and B-type nodes could be selected as Audience for a new BB-type.

The user who have access to create A content type should not get the permission to create BB content type and also the user who have access to create B content type should not get the permission to create AA content type.

Comment	File	Size	Author
#7	og-permissions.png	210.73 KB	ttronslien
#7	Screen Shot 2015-11-04 at 7.48.42 AM.png	25.92 KB	ttronslien
#2	og_second_field.png	37.45 KB	reynosoreyesmiguel
#2	og_field_one_config.png	41.83 KB	reynosoreyesmiguel
#2	og_error_for_second_entity.png	21.37 KB	reynosoreyesmiguel

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

jastraat CreditAttribution: jastraat commented 3 June 2015 at 06:09

This should be possible already, but you would need to use two different entityreference fields with separate target bundle configuration.

Comment #2

reynosoreyesmiguel CreditAttribution: reynosoreyesmiguel commented 2 November 2015 at 07:56

File	Size
og_error_for_second_entity.png	21.37 KB
og_field_one_config.png	41.83 KB
og_second_field.png	37.45 KB

Hi.
I have exactly same situation. When i try to add two different entity references for my two og group content types i get the error :

FieldValidationException: Errores de validación de campo en OgBehaviorHandler->validate() (línea 295 de /srv/httpd/sites/portal/sites/all/modules/og/plugins/entityreference/behavior/OgBehaviorHandler.class.php).

Attach the configuration for two fields.

Comment #3

ttronslien CreditAttribution: ttronslien at Portage CyberTech commented 4 November 2015 at 00:16

@reynosoreyesmiguel I think your issue is solved in the following issue: FieldValidationException: error when saving entity og reference fields

Comment #4

ttronslien CreditAttribution: ttronslien at Portage CyberTech commented 4 November 2015 at 00:15

It's not clear here "if the user who has access to create..." is granted access based on a regular Drupal role or the user's association with the group. Have you tried the module Organic Groups Create Permissions

This module provides the following key features:

Users can no longer create content in groups they are not active members of
Provides a new group level "Create" permission

Comment #5

ttronslien CreditAttribution: ttronslien commented 4 November 2015 at 00:13

Category:

Feature request

» Support request

Comment #6

jastraat CreditAttribution: jastraat commented 4 November 2015 at 07:14

I don't believe OG create permissions is compatible with the 7.x-2.x version of OG which already has built in create permissions.

The roles that determine create access can be either the Drupal role or the user's role in the group. It depends on if you've enabled 'strict' permissions in the OG settings. When 'strict' permissions are enabled, users need to either have access granted by their group membership role or have full 'administer og permissions' at the Drupal role level.

Comment #7

ttronslien CreditAttribution: ttronslien commented 4 November 2015 at 12:51

File	Size
Screen Shot 2015-11-04 at 7.48.42 AM.png	25.92 KB
og-permissions.png	210.73 KB

You were right about the built in.

So maybe I am not understanding what you are getting at, but here is what I did

Created Content Type Group A, B, and C
Created Content Type AA, and BB with Group relations to the respective Group Content Types
Created Group A and Group B of the respective Content Type
For the fun of it, I added a new role on drupal level (Contributor) and one of each of the respective Groups (Contributors)
Configured such that Contributors in Type Group A can add, edit, delete content type AA, did the Same for Group B. (Screenshot attached)
Created dummy userA and dummy userB.
Assigned user to their respective Groups, giving them contributor role
Enabled og_extras and placed the content block in a visible region (I found this to be helpful http://makandracards.com/jan0sch/11463-drupal-organic-groups-extras-add-...)
and when I log in as userB, I get Create Content BB
and I log in as userA, I get Create Content AA (Screen shot attached)

I hope this helps, and if I am off the charts in the wrong direction, please tell me so.