Hi,
I am trying to get OG user roles working on my test site and am unable to do so.
I have followed all the installation instructions (except the stylesheet change) and there are no errors.

Basically I have a sitewide role called 'Blogger' (Who has permission to create blogs). I want to be able to restrict the scope of this role within an OG so that a particular user can only create blogs within and OG.

After installation and configuration, I go to the Group page (say Group_foo_bar) and on its members/subscribers page I give 'Blogger' Right to a an user (say dummy_user). Before this, this user does not have node create permission sidewide.
Then I login as dummy_user but do not find the 'Create Blog' link on the group info Block. There is create content but it only has links to node types other than blogs (which are allowed for all users sitewide).

What am I doing wrong? Do I need to create a separate role with different sets of permissions for this purpose? I have not installed og_forums module. Is this a problem even in 5.x-3.2 ?

I would appreciate any help. This is a wonderful module and solves a lot of problems for me if I get it working.
Thanks!

Comments

somebodysysop’s picture

On project page:

If your basic "OG Roles aren't working", please note the following:
It appears that the Drupal caching mechanism is used much more stringently as a result of either 5.7 core or OG 5.x-7.x changes. Assuming OGR has been installed correctly, this may result in group roles you've assigned to group users not being respected when they should (i.e., when they are in group context). In this case, the solution is to implement the "Clear the Cache" setting in OGR: http://drupal.org/node/263944.

Also: http://drupal.org/node/286798

shas3n’s picture

Status: Active » Fixed

Thanks a lot!
That was fairly naive of me. For some reasons, I was under the impression that the newer versions do not need user.module to be patched. Patched it and it worked like a charm.
Shas3n

Anonymous’s picture

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.