Here's what I learned today: you can't require a group post to have an audience and also mandate that it be public. Apparently that's because "public" is considered a group. So you can mandate that a user choose a group all you want, it doesn't mean a damn thing because the hidden "public" checkbox is also considered a group.

So if I want to mandate that a user choose one group, the post has to be private. Because even if "public" is optional, "public" is still a group. Any group they choose will make the post "private", which means non-group members can't see it. Is that correct?

So yeah, I marked this as critical because unless there's a workaround for this I can't use OG in any capacity. Somebody please tell me I'm wrong.

CommentFileSizeAuthor
#1 og.JPG19.81 KBmjohnq3

Comments

mjohnq3’s picture

mjohnq3 commented
StatusFileSize
new og.JPG19.81 KB

Public content is public; anyone with permission to 'access content' on the site may view it. Posts may be Public, Private, or a combination of both. See the attached image for the Audience options.

jthomasbailey’s picture

jthomasbailey commented

Yes... the problem is when I force a user to choose one and only one group their choice is ignored because the default "public" is a group.

At least I think that's what's happening, I turned off OG Access Control and it's still doing it. It might actually be a bug.

jthomasbailey’s picture

jthomasbailey commented
Title: "Public" should not be considered a group! » Impossible to limit to one group
Project: Organic Groups » OG Audience By Type
Version: 6.x-2.x-dev » 6.x-1.x-dev
Component: og.module » Code
Category: feature » bug

Never mind. Problem is with OG Audience By Type, but I'm not sure exactly what's wrong yet.

jthomasbailey’s picture

jthomasbailey commented
Title: Impossible to limit to one group » Neither 'Force Single' or 'Require' work because of 'Dummy Value'

What's happening is a 'dummy value' is assigned to og_groups so that it passes validation - on line 94 of og_abt.module - and this counts as 1 group. So if you use the 'force single' option it counts that dummy value as a group and ignores the actual group choice.

This also means that the 'require' option doesn't work because if no group is chosen the 'dummy value' is still selected.

Major bug.

jthomasbailey’s picture

jthomasbailey commented
Title: Neither 'Force Single' or 'Require' work because of 'Dummy Value' » Neither 'Force Single' or 'Require' work

not sure if it's because of Dummy Value or not. This is really a shame, this would be great module if it worked.

jthomasbailey’s picture

jthomasbailey commented
Title: Neither 'Force Single' or 'Require' work » Attention: This Module Doesn't Work With Organic Groups 2.x
Status: Active » Closed (won't fix)

Well I'm stupid, it took me 3 days to figure out this only works with OG 1.x. I downgraded to 1.x and it's doing what it's supposed to.

jthomasbailey’s picture

jthomasbailey commented
Title: Attention: This Module Doesn't Work With Organic Groups 2.x » 'force single' and 'require' don't work for non-admins
Status: Closed (won't fix) » Active

I spoke too soon, this thing doesn't work with 1.x either. Works fine for Administrator but for other roles 'force single' won't assign a post to a group and 'require' doesn't do anything.