[support] Organic Groups

Wed Feb 9 04:14:17 UTC 2011

Hi Sara,

Glad you made at least some progress.

Turn off the overlay! I think it is a separate module you turn off. (I
helped with some testing of 7 about a year ago for about three months... but
I haven't used 7 in at least 9 months and don't have it installed on any
sites now).

Report back and tell us if that solves the problem.

Shai

On Tue, Feb 8, 2011 at 8:53 PM, Hasti Ziaimatin <h.ziaimatin at uq.edu.au>wrote:

> Hi Shai,
>
>
>
> Thank you very much for your reply. I have followed your suggestions and
> now have an access control configuration tab for both the group content type
> as well as for each group created. However, the access control tab for a
> group, which appears as a result of enabling the “Enable per content node
> access control settings” checkbox in the group content type Access control
> configurations, isn’t accessible due to the following error:
>
>
>
> Webpage error details
>
> User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0;
> .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR
> 3.5.30729; .NET4.0C; .NET4.0E)
>
> Timestamp: Wed, 9 Feb 2011 01:45:07 UTC
>
> Message: Permission denied
>
> Line: 267
>
> Char: 3
>
> Code: 0
>
> URI: http://localhost/drupal7/modules/overlay/overlay-parent.js?v=1.0
>
>
>
> I have downloaded the latest build (690610_142.tar_.gz) for the content
> access module from the http://drupal.org/node/690610 website, extracted
> the contents using 7-Zip (as I’m working on windows); but I still get the
> same error. Therefore, I guess I can’t test the fine grained access
> configuration until group level access control config is working.
>
>
>
> My other question is how can we associate a “group content” with a group? I
> create a group content and set Group audience to an existing group, but when
> I go to the group page, the content doesn’t appear under the group.
>
>
>
> Your help is much appreciated.
>
>
>
> Cheers,
>
> Sara
>
>
>
>
>
> *From:* support-bounces at drupal.org [mailto:support-bounces at drupal.org] *On
> Behalf Of *Shai Gluskin
> *Sent:* Saturday, 5 February 2011 1:34 AM
> *To:* support at drupal.org
> *Subject:* Re: [support] Organic Groups
>
>
>
> HI Sara,
>
>
>
> I haven't used Organic Groups for 7, but most of what you are trying to do
> is pretty straightforward. First I should say... if you need your site up
> ASAP and you don't have developer support, you might consider D6. In a month
> or two, things will be a lot better with D7, so if you can be patient
> obviously there are big advantages to D7.
>
>
>
> Regarding per user access (only some members have access to...), you want:
>
>    1. Content access: http://drupal.org/project/content_access (a lot of
>    work is being done on the D7 version at: http://drupal.org/node/690610)
>    2. ACL: http://drupal.org/project/acl (there is already a D7 beta
>    version)
>
> #4 built in to OG as long as you make the group "Private"
>
> #5 only viewable by group. As long as you set the message to private this
> will work.
>
> #6, built in basic to OG
>
> #2, built in
>
> #8, I'm not sure what you mean by "roles assigned to members of a group",
> like what for example. "Administering group members" is something that comes
> built in with Organic Groups and you don't use the Core-based permissions
> system. With the OG admin interface, any current group admin can assign
> another member of that group to also be an admin.
>
> #9 The "audience" feature cover you there. On a per node (content) basis
> you can set the audience for that piece of content.
>
>
>
> I think that gets you goin'.
>
>
>
> Do report back,
>
>
>
> Shai Gluskin
>
> Owner, Content2zero Web Development
>
> 215-839-9001
>
>
>
>
>
> On Fri, Feb 4, 2011 at 1:48 AM, Hasti Ziaimatin <h.ziaimatin at uq.edu.au>
> wrote:
>
> Hi All,
>
>
>
> I’m new to Drupal and have recently installed Drupal 7 release version and
> the Organic Groups (OG) module. However, I can’t seem to be able to
> configure permissions and roles to facilitate our access control
> specifications. I appreciate your help in providing me with a guideline to
> enable me to satisfy the following access control specifications:
>
>
>
> Access control should be implemented for a knowledgebase system that
> facilitates collaborative knowledge management and research in a particular
> medical domain.
>
>
>
> 1.       Groups need to be created; these groups represent entities with
> knowledge and expertise in the particular medical domain
>
> 2.       Every group has an “owner” that can add members to the group
>
> 3.       The group owner loads/adds patient cases into the knowledgebase
> as content for the corresponding group
>
> 4.       Only members of the group can view these contents
>
> 5.       Contents loaded/added to a group cannot be viewed by members of
> other groups
>
> 6.       Members can only add content to the group/s of which they are a
> member
>
> 7.       Specific content in a group may need to be visible only to some
> members of the group
>
> 8.       Roles assigned to members of a group should be restricted to only
> that group unless the group owner specifically assigns that role to the user
> in another group.
>
> 9.       We would also like to look into enabling members of a group to
> have access to a subset of contents from another group.
>
>
>
>
>
> Your help is much appreciated. I also looked at using OG User Roles (OGUR)
> ; however, this module isn’t available for Drupal 7.
>
>
>
> Kind Regards,
>
> Sara
>
>
> --
> [ Drupal support list | http://lists.drupal.org/ ]
>
>
>
> --
> [ Drupal support list | http://lists.drupal.org/ ]
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/support/attachments/20110208/2c857517/attachment.html 