By Steven Mansour on

Hello,

I made some changes to a site I run that I thought were small; I deleted one vocabulary assigned to blog posts and audio files, and created a new one to replace it.

However, now users get access denied when trying to view blog posts and some custom content types. Only users with "administer nodes" are able to view any sort of content, so my site (a blogging aggregator) is effectively down.

I've disabled all contrib modules and tried lots of different things, but I'm stuck now.

Any ideas why non-admins would suddenly lose the rights to view blog posts and other content?

s.

⋅ Categories: Drupal 5.x

Comments

zilla’s picture

zilla commented

uh, based on what you said it sounds like you removed a vocabulary to which they were all assigned and so users are now seeing nothing - you may need to go back and reassign it all manually OR roll back to an earlier version and simply edit each vocabulary term (probably an easier thing to do)

Steven Mansour’s picture

Steven Mansour commented

Thanks Dave,

But I don't think that changing vocabulary affects permissions to the content itself; I'm not using any form of Taxonomy access control or anything.

s.

sepeck’s picture

sepeck commented

Make sure you have a UID0 in the user table. UID0 is used for anonymous content and rarely can glitch out and disappear. It is VERY rare, but with tens of thousands of Drupal installs sometimes weird things happen.

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide

zilla’s picture

zilla commented

maybe (not sure) a dbase rebuild, or run update.php, or check your mysql for error logs on the content requests to see what's happening when it displays nothing...

Steven Mansour’s picture

Steven Mansour commented

I didn't find what the problem was, but I solved it by simply updating each node (using an automated script to "edit" each one then click "save").

I imagine I could've used the "rebuild node permissions" button to fix it too now.

Thanks again,

s.