Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
By Tommy Sundstrom on
After upgrading to 4.6.5 from from a development version of Drupal released after 4.6.2, I have this strange problem:
When I come as an anonymous user the front page shows the "Welcome to your new Drupal-powered website"-page, i.e. the page that is shown when you have a fresh installation of Drupal that still has no content.
If I log in, everything works just fine. All the content are there, and I can do all things I should be able to do. This is true both when logged in as user 1, and with other accounts.
But as an anonymous user I can't see any content.
If I try to go directly to a node (by entering it's url), I get a "403 Access Denied". The 403 message is in the graphical style of my ISP. If I try to go to the same url when logged in, there is no problems.
In the 'access control'-page, the node module/access content is checked for anonymous users.
I have also created a fresh database (initilized with the database.mysql-script from 4.6.5). This works just fine, and after creating some content as a logged in user, I'm able to read it as an anonymous user. This leads me to the conclusion that the error is somwhere in my old database.
--
When upgrading, I checked the update.php script, but since there was no updates later than 2005-05-07 and 4.6.2 was released 2005-06-29 there was no upgrade to perform.
One strange thing with this though: when manualy checking the database I noticed that in the "users" table there is one new field "changed" that my old database did not have. So I added it by hand.
This wakes the suspicion that my old database is out of sync. But I can't find any other dicrepancies (exept that my old database has a "access" field in the "users" that the new one is missing).
--
In an attack of desperaton I even tried with selecting a number of tables from the old database, exporting them and then importing them into the new. But this did not help.
The only difference is that when I try to reach the node directly as an anonymous user, by entering the url, I do not get a 403, I get a 500 (An internal server error occured while processing your request), and the suggestion that this kind of error often is the result of that the program has not been made executable. (Accessing the same node when logged in works just fine.)
--
Any advice/pointers would be apreciated.
Comments
Solution
I've tracked the problem down to the node_access table.
It seams that it is necessary to have the modules that are mentioned in the "realm" column active, in order to avoid this problem.
In my case it was taxonomy_access that where missing.
Probably I did not deactivate it properly before starting the upgrade.
This problem is also discussed in http://drupal.org/node/11228
it was quite a learning for
it was quite a learning for me, I read various threads, thought the problem would be uninstalling Simple access or OG, or Taxonomy access, well it was none of these for me
I cleared up the entire node access table, keeping just one record, it still did not work.
Finally i checked the node table and found that the content was created by user which I had manually deleted from backend.
So I changed the uid on node table to valid user and Kabooom .... it worked!
______________________________________
Cheap domains @ http://whiz.in
Another solution
http://drupal.org/node/64114