views:

205

answers:

3

My Database was quite large with lots of test data in tables like watchdog, access log,etc.. and I was running in to some trouble uploading. Then I proceeded to dive into the database and started truncating tables willy-nilly. I am figuring out that I should have used a little more discretion because I have had issues on the new production server.

The main problem is that annonymous users can't view any content, even though in 'permissions', they are set to access content. Also, they were definitely able to view content before the migration, so it had to be one of the tables I hacked. Because everything else is running smoothly.

Anyone have an idea which table, if truncated, might produce symptoms like this?

Update: - I checked that I have user 0 - which would probably yielded the same symptoms. - Problem persists though..

A: 

Do your users table contain a row with uid=0? If not, create it. This row represents anonymous users.

dusan
Ah, good one...But I checked, and user 0 exists.
cinqoTimo
A: 

Do you have (0,0,'all',1,0,0) in your node_access table?

See this comment: http://drupal.org/node/122476#comment-1058731

stephthegeek
A: 

Have you tried rebuilding permissions?

http://yourdomain.com/?q=admin/content/node-settings/rebuild

Or running update.php? Either should rebuild the node access table.

Jared

related questions