The .htaccess file is there, but I can't confirm if it is correct or not. I got it from a brand new download of Drupal 5.16. If I go to index.php?q=user I can login, and then I can see the site pages then, except for the fact that the theme is gone (no sidebar, and background is white). Does any of this mean anything to you? I'll see if I can get the theme working again. Daniel. William Smith wrote:

Did you move the .htaccess file? It is quite proper that /update.php should give the Drupal access denied error if you aren't logged in as user #1. However, your /index.php access denied page does not look like it is coming from Drupal. Navigating to /user, I notice that it is returning a "Parallels Control Panel" page, not the expected Drupal user login page.

Your page routing is off, and this is probably because you did not move .htaccess

Best, William

On Mon, Dec 15, 2008 at 9:08 AM, Daniel Carrera <daniel.carrera@zmsl.com <mailto:daniel.carrera@zmsl.com>> wrote:

Hello,

I have moved a Drupal site to a new host and I can't access it! It gives me an access denied error and I believe that it is something with Drupal. Here is the site:

http://rosemarymusker.co.uk/index.php

I'm sure that it is a Drupal error because if you go to the update page you see this:

http://rosemarymusker.co.uk/update.php

You can see that this is a Drupal page, that Drupal itself is accessible and working but Drupal refuses to allow access. So the access denied error must be a problem with Drupal.

Does anyone have any suggestions?

Daniel. -- [ Drupal support list | http://lists.drupal.org/ ]

Daniel Carrera wrote:

I'll poke around the admin pages and see if I find anything odd.

WHOO HOO!!! Rebuild Permissions did it. Thanks for all the help. Especial thanks to Earnie who noticed that I could still login by appending ?q=user. Without that I would still be banging my head against the wall. In the end, there were two distinct problems: 1) The theme wasn't working. I "fixed" this by switching to another theme and switching back. Weird. 2) The node permissions were broken. I fixed these with rebuild permissions. Cheers, Daniel.