"Organic groups access control" causes "Access denied" on content access permissions rebuild

spflanze - September 20, 2009 - 18:31
Project:Organic groups
Version:6.x-2.0
Component:og.module
Category:bug report
Priority:normal
Assigned:Unassigned
Status:active
Description

I started with a freshly installed Drupal 6.14 installation with no content and no modules enabled other than default for a new install. The first thing I did with the new installation is enable "Organic groups." Next I enabled "Organic groups access control." This enablement caused this message to appear at the top of the administer modules page:

The content access permissions need to be rebuilt. Please visit this page.

I initially ignored this message and set up Organic Groups content types and permissions. Then clicked on the link of this message to rebuild content access permissions. I got a page with this message:
Are you sure you want to rebuild the permissions on site content?
This action rebuilds all permissions on site content, and may be a lengthy process. This action cannot be undone.

I went ahead with the rebuild and got a page with this message:
Access denied
You are not authorized to access this page.

Because I did this as user 1 on a fresh install I do not understand how I could be denied access to anything.

I had a look at the node_access table and found it empty. The single row that was there after installation and just before this rebuild was empty.

I am still able to access administrative functions without having to log in again. But the "The content access permissions need to be rebuilt. Please visit this page." is still there on many admin pages.

The single row in the node_access table reappears when I disable ""Organic groups access control," and the message "Content permissions have been rebuilt." appears at the top of the modules right after this disablement.

What has gone wrong here?

#1

matt_harrold - September 22, 2009 - 02:16

I don't have a solution ... but I can confirm the same issue on my system. Brand new install (6.14, OG2.0) ... cannot create groups, access denied.

Any solutions out there ? It seems like a bug to me, not a support request.

#2

spflanze - October 1, 2009 - 19:04
Category:support request» bug report

I agree this is most likely a bug. I am changing this thread category to a bug report.

#3

easytech - October 16, 2009 - 22:25

I also figured out that enabling organic access control needs to rebuild the content access permission. Tried out 80 times but I was unable to rebuild. Finally I have disabled that.. any solutions out here

#4

LEternity - October 26, 2009 - 21:48

subscribing

#5

LEternity - October 27, 2009 - 13:50

I found a couple of approaches in different posts. Neither one of them did it for me though. A lot of speculation going on.

http://drupal.org/node/300079
http://drupal.org/node/281326

#6

Janam - November 11, 2009 - 07:23

subscribing

#7

Zarevac - November 17, 2009 - 21:19

Subscribing

#8

Zarevac - November 18, 2009 - 11:15

Well, I checked the settings file to check if the paths etc. were set good and I also tried cookies, browser, theme change, taking the inserts from a backed up file. Nothing shows up in the systems error report and I did manage to narrow it down to the OG module and specifically to the Organic groups access control. One thing Drupal does give me when trying to run the rebuild is a 404 error.

#9

Zarevac - November 18, 2009 - 14:39

Tried a clean install, same problem.

#10

marcp - November 18, 2009 - 17:54

If you can give the exact sequence of steps that caused the problem that will help folks figure out what's wrong. For example, start with:

1. Install Drupal 6.14
2. Put OG 6.x-2.0 in sites/all/modules
3. Enable Organic Groups and OG Access Control
4. etc...

If you can give a full list of reproducible steps (and then reproduce them yourself) you'll make the maintainers' jobs easier (and probably figure out what went wrong along the way).

#11

Zarevac - November 21, 2009 - 18:05

1. Install Drupal 6.14,
2. Installed OG latest stable version in sites/all/modules/
3. Enabled Groups and OG Access Control
4. Got notification to rebuild,
5. Tried to Rebuild and it went bananas.

Tried on two installs now same problem. Could it be mod_sec?

#12

marcp - November 21, 2009 - 18:08

By "went bananas" do you mean 404? If there were other messages it would be useful for you to post them here.

#13

Zarevac - November 21, 2009 - 21:53

Yes 404 and now a 406 after I changed the permissions of the index file and turned off clean urls. I removed og but it persists.

#14

Zarevac - November 22, 2009 - 22:55

I fixed it.
1. Disable clean urls,
2. Add exception for htaccess mod_sec: SecFilterEngine Off
3. Run rebuild and it worked.

 
 

Drupal is a registered trademark of Dries Buytaert.