WSOD when using together with organic groups

Could you provide your OG configuration :
- which type is the makemeeting field on
- which type is the group type
- which type is the group content type

Not to hi-jack this thread, but I'm having an identical error using groups. I can try to answer these questions based on my config...
1) which type is the makemeeting field - "meeting_scheduling"
2) which type is the group type - "committee"
3) which type is the group content type - "meeting_scheduling"

Still can't reproduce the bug using https://simplytest.me/project/og?add[]=makemeeting

• I enabled makemeeting, og ui
• I added a content type committee that is a group
• I added a content type meeting_scheduling that is a group content

1. I created both content using admin and voted using admin.
   Everything ok
2. I added 'create meeting_scheduling' and 'provide makemeeting on answers' permissions for authenticated user and created one
   
   I created a meeting and voted both as admin and user
   
   Everything ok

I get the same error as reported above:

• I created a node type that is group content and assigned to a group.
• Added a make meeting field to it.
• Added a node of the type above.
• Voted as site admin: everything works fine
• Voted as normal user: Got the error as reported above.

When I refresh the page after the error occurred, the vote is saved nevertheless.

I have this problem when using makemeeting with Atrium 2.60 which depends on organic groups. I checked the latest commits and this error was introduced with the cache changes in. Commit before is working..

Commit 37a86d7 on 7.x-2.x
by SebCorbin
Follow-up #Issue #2104033 by DuaelFr, SebCorbin: Invalidate core page cache and contrib Entity Cache when add/edit/deleting an answer

Hello,

I still have this problem, any sollution?
thanks

Will look into it with Atrium once I have time, also thanks for mentioning the bad commit

Hello,

have you found a solution for this problem?
thank you

Hi,
I had the same issue when trying to combine this module with Organic Groups 2.x. I'll add my findings:
The issue is coming from _makemeeting_clear_referencing_fields() in makemeeting.module. There's a condition there to check against the field handler being 'base', but for OG the handler is actually 'og', so the OG reference gets included in the "referencing fields" by mistake (for me, the makemeeting field is on a bundle that is group content, so the OG group is referenced not referencing). Now, I'm not sure what was the purpose of 'base', so I dare not suggest everyone should kick it out; but in my case, the condition to check against the bundle was sufficient, so I just removed the handler condition.
In short, what was:

    // If the field is using the base handler check if the bundle is allowed.
    if ($field['settings']['handler'] == 'base' && !in_array($bundle, $field['settings']['handler_settings']['target_bundles'])) {
      continue;
    }

became:

    // If the field is using the base handler check if the bundle is allowed.
    if (!in_array($bundle, $field['settings']['handler_settings']['target_bundles'])) {
      continue;
    }

Based on what was proposed in #9, I instead added a second condition specifically for OG since this is the only module so far that seems to cause an issue.