Drupal site not behaving - process of elimination

views:

answers:

+1 Q:

Drupal site not behaving - process of elimination

I have two versions of a Drupal site running on my local dev environment. Site X boots perfectly; site Y doesn't - rather than running index.php, install.php is called.

So far, I've:

Stepped through site Y with a PHP debugger; index.php does not seem to be called at all.
Pointed site Y at the database for site X to see whether there were database corruption issues; seemingly, there weren't.
Swapped out the .htaccess file in site Y for the .htaccess file in site X. No joy.

What should I try next?

+1 A:

Does settings.php exist in site Y and does it have the correct database information?

Also, are these two seperate drupal installs, or one drupal install setup multisite?

Kevin 2010-07-29 15:42:05

Thanks.settings.php does exist in site Y, and it seems to have the correct database information. When I point site X at the database for site Y, site X boots.These are two separate, single-site Drupal installs.

Jim 2010-07-29 15:57:13

What if you try backing up that database, and dropping in a blank settings.php (copied from default.settings.php) and run the install process, does it connect to the right database then?

Kevin 2010-07-29 15:59:17

Thanks! This didn't quite work but I've now got site Y booting. I'm getting Access Denied messages, though, and the theme isn't loading - I think this might be something to do with site Y being built in a Wintel environment; I use OSX. I'll keep plugging away, but would appreciate any inspired insights :)

Jim 2010-07-30 18:25:26

ok, turns out it was a pretty standard D6 perms issue - set the perms on each folder in sites/ for site Y to the same as the perms for site X, et voila. tks for your help, Kevin :)

Jim 2010-07-31 14:06:46

the above provides a walkthrough, so question answered.

Jim 2010-07-31 14:07:31

ansaurus

tags:

views:

answers:

Drupal site not behaving - process of elimination

related questions