I've followed the documentation and I've simplified my permission scheme to bare bones. An authenticated user only has forum and comment permissions by default. When he joins a group, he is granted rights to create story and page. This appears to transpire correctly under the create content option, as when the user is viewing the homepage, both story and page appears as expected. The problem occurs upon choosing to create content. He is hit with: "Access denied -You are not authorized to access this page." At which point he looses the links to create stories and pages. Clean URLs are enabled and I'm using 6.17. OG access control is installed, but not TAC or ACL. In fact, I've eliminated all access modules to narrow down the problem. Permissions have been rebuilt and all caches have been cleared. This appears to have been dealt with here: http://drupal.org/node/535738 but it dead ends without a satisfactory solution, as my Group Details block is already enabled. I'm not using any translation modules, but maybe something needs to be turned off? Could there be a dependency some where? I'm stumped.

Comments

robatk’s picture

There is an issue that may shed some light on the above. I'm using the jquery menu module, which means when I select the little triangle to the left of "create content", I can see that stories and pages have loaded as it should. However, if I select the word link, then I'm transported to that URL which I'm sure breaks the context of being on a group page. The result being that the user has lost the privileges.

djdevin’s picture

Are you using spaces_og? Had the exact same problem, ended up being resolved with module weights.

Install/enable module_weights
Set spaces_og to -1
Set og_user_roles to -2
Devel clear cache

By default the spaces_menu_access callback gets called for node/add/% before og_user_roles has a chance to assigns the role.

avpaderno’s picture

Version: 6.x-4.1 » 6.x-4.x-dev
Issue summary: View changes
Status: Active » Closed (outdated)
Issue tags: -Access denied

I am closing this issue, since it's for a Drupal version no longer supported.