Closed (fixed)
Project:
Organic Groups
Version:
master
Component:
og.module
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
16 Jun 2006 at 06:44 UTC
Updated:
27 Feb 2008 at 10:52 UTC
Every node that I create within the group is made public even though the public box is not checked. When I log out, I can navigate to the group and still see nodes that are not selected for public.
Suggestions?
Comments
Comment #1
jonathan_hunt commentedI'm new to og, and I thought this was a bug also, but looking at the code in og.module, this is the default behaviour. You probably need to (a) delete a row from node_access table, and (b) edit og.module to change the behavious. See my comment elsewhere http://drupal.org/node/21133#comment-131920
Comment #2
ron collins commentedthis seems to be a duplicate of http://drupal.org/node/21133
Comment #3
ron collins commentedmy mistake. that last node was a forum topic. there was another dup which is now pointed here.
to summarize, there seem to be two issues:
1) anonymous users can browse to a group's home page even when the group is "private". i assume private in this context means that the "list in groups directory" option is not checked for that group.
2) anonymous users can browse to content on a group's homepage which has the "public" option (under groups) unchecked. presumably, content flagged in this way should only be visible to group members.
this is still an issue in // $Id: og.module,v 1.110.2.157 2006/12/12 02:56:34 weitzman Exp $
Comment #4
Tresler commentedThis might be a seperate issue, but on groups.drupal.org you can create a group - and _before_ it is approved others can join the group, post comments etc.
I didn't have time to look to closely, it happened by accident. A friend made a group - sent me the url, I joined and commented - then saw a banner at the top that read "The post has been submitted for moderation and won't be accessible until it has been approved." And I checked and sure enough - on the groups list the 'subscribe' link isn't there for that group and said friend told me it hadn't been approved yet.
Anyway, hope this helps.
Comment #5
beginner commentedSubscribing.
This bug exists in HEAD, too.
Comment #6
beginner commentedI am trying to figure out what is happenning....
I think looking at the {node_access} is relevant.
One node which should be private to a single og, has: realm = all, grant_view = 1. I guess it is not supposted to be this way...
But even if I manually update the DB so that realm = all and grant_view = 0, the node is visible.
I don't know enough that part of the code, so I am merely pocking around, to see what I can find...
Comment #7
beginner commentedOh my god!
I was sure that I had enabled the Organic groups access control at /?q=admin/og/og, but checking back, I found it disabled.
Obviously, enabling it solved the problem.
I suspect that the people above forgot to do the same thing.
I close this issue: If anyone can confirm that they have enabled the Organic groups access control at /?q=admin/og/og and STILL experience the same problem, please post precise instruction on how to reproduce!
Comment #8
(not verified) commentedComment #9
kloosm commentedI don't know it's me, but when I disable access control in organic groups module, groups aren't visible to anonymous users. When I enable the module, group content is visible. I also installed content_access module and set that the group content type can only be viewed by authenticated users.