Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
The following fatal error I get when submitting the entries in the makemeeting form as user.
I'm using the latest dev of both this module and the OG module.
and
Comment | File | Size | Author |
---|---|---|---|
#10 | wsod_when_using_together_with_organic_groups-2475821-10.patch | 710 bytes | vensires |
#2 | error.png | 241.32 KB | Tony Stratton |
ajax error 1.png | 35.01 KB | Yuri | |
error.png | 1.92 MB | Yuri |
Comments
Comment #1
SebCorbin CreditAttribution: SebCorbin commentedCould 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
Comment #2
Tony Stratton CreditAttribution: Tony Stratton commentedNot 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"
Comment #3
SebCorbin CreditAttribution: SebCorbin commentedStill can't reproduce the bug using https://simplytest.me/project/og?add[]=makemeeting
Everything ok
I created a meeting and voted both as admin and user
Everything ok
Comment #4
gunwald CreditAttribution: gunwald commentedI get the same error as reported above:
When I refresh the page after the error occurred, the vote is saved nevertheless.
Comment #5
leo_g CreditAttribution: leo_g commentedI 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
Comment #6
sazevedo@ua.pt CreditAttribution: sazevedo@ua.pt commentedHello,
I still have this problem, any sollution?
thanks
Comment #7
SebCorbin CreditAttribution: SebCorbin commentedWill look into it with Atrium once I have time, also thanks for mentioning the bad commit
Comment #8
sazevedo@ua.pt CreditAttribution: sazevedo@ua.pt commentedHello,
have you found a solution for this problem?
thank you
Comment #9
anahawk CreditAttribution: anahawk commentedHi,
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:
became:
Comment #10
vensires CreditAttribution: vensires commentedBased 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.