All users but user/1 denied access to all content

media girl - April 26, 2005 - 18:37

I'm pretty sure this is not a bug but a glitch in my database somewhere. I've had a smooth upgrade, and the site is shaping up ... but only for my user/1 admin account. What I am seeing otherwise:

  1. All other users are denied access to all content. This is even though I have rechecked the access settings 100 times. Access content is enabled for all users.
  2. Experimenting, I discovered that all other users are denied access to even front_page. This is even though I have enabled front_page access. Turning the module off again does nothing. The users simply cannot access /node or any node content, new or legacy.
  3. All other users see the default Drupal welcome message -- "TWelcome to your new Drupal-powered website. This message will guide you through your first steps with Drupal, and will disappear once you have posted your first piece of content...." -- even though there are a dozen or so existing posts. I created a new test post, promoted it, and still all other users get that initial welcome message.
  4. I created a new user (user/9) and still ran into all the above problems.
  5. Changing themes does not affect any of this.
  6. Interestingly, user profiles are accessible.
  7. Non-clean urls (e.g., ?q=node) are not found. Not surprising, as this is an access denied problem.

Okay, here's the backround I think might be relevant. My proper backup with all the extra modules disabled ended up getting corrupted, so I had to insert a week-old database backup (with modules not disabled) to use for upgrading. One of those modules was taxonomy_access. I'm suspecting that there is a lingering permission setting that I cannot access now with the current system. I dropped the term_access table, but that did not fix things. I cleared the cache, but that did not fix things.

If I am dealing with a legacy setting from the old taxonomy_access module, is there another place I should look, another table I should drop or a line I should edit? Any clues would be appreciated!!!

Update

media girl - April 27, 2005 - 02:52

I've been able to activate front_page for anonymous users, and since learned that other users with administrator privileges can access all content. But normal registered users still cannot. Is there a trigger somewhere, a legacy of taxonomy_access, perhaps, that is preventing normal access to normally public content? Any SQL ideas?
--
mediagirl.org

Be sure to FULLY disable taxonomy_access before upgrade

media girl - April 27, 2005 - 20:55

I made a new backup of the old site database, and reinstalled the database on the new site. The upgrade ran quite smoothly. Here's what I (the dim bulb this week) re-learned:

It behooves the upgrading administrator to remember that taxonomy access permissions will lock up an upgraded site. Be sure to disable the module using the complete 2-step procedure:

1/ Go to admin/settings/taxonomy_access and disable the module functions

2/ Go to admin/modules and disable the module itself

If you skip step one, you will run into access permission errors on the upgraded site.

I hope this saves someone else from the day of puzzlement I experienced.

--
mediagirl.org

How did you activate front_page?

hound - April 29, 2005 - 21:42

How did you activate front_page? I have the same problem. Anonymous users see the "here's how to activate your new Drupal Site" page, complete with the offer to create a new superuser. Help! All of my content is there, but it does not show the way it did under 4.5.2

More

hound - April 29, 2005 - 22:32

More info about my problem; I have enabled the node_privacy_byrole 4.5.2 module. When I did the upgrade to 4.6.0 I just bulled ahead and created a second directory tree with that code and ran the update.php script - without first disabling the node_privacy_byrole module in my 4.5.2 installation.

I have gone back to the old setup, and with that module disabled I get a blank front page. It seems that my problem may have to do with properly migrating guest permissions to the page '/node'.

Any ideas? I can go back to my 4.5.2 setup so this is not a disaster, but I would definitely like to try the new version...

 
 

Drupal is a registered trademark of Dries Buytaert.