By annabellisimo on

Hi, I'm very new to Drupal and bravely attempted today's upgrade.

I deleted all my Drupal 5.1 files from the server, uploaded the 5.2 files, then uploaded my backup sites/all/modules, sites/all/themes and .htaccess files.

I went to run update.php and it redirects me to install.php -- which doesn't do anything.

I must have broken something, but I can't figure out what. I have checked that everything is uploaded. I have changed update.php to $access_check = FALSE; in case I had been logged out, but that didn't fix the problem.

I'm using ftp to upload files, and don't have very much familiarity with php, so any suggestions in the kind of basic language you'd explain Drupal to your mother in would be gratefully received. I have been running 5.1 successfully for the past month, and the installation of that went very smoothly.

Thanks for any help you can give me.

⋅ Categories: Drupal 5.x

Comments

heine’s picture

heine commented

I think you need to edit sites/default/settings.php or sites/[example.com]/settings.php to provide the database credentials: 

$db_url = 'mysql://username:password@host/databasename';

You can copy the line from the settings.php in your backup. Do not copy the old settings.php!
--
The Manual | Troubleshooting FAQ | Tips for posting | How to report a security issue.

annabellisimo’s picture

annabellisimo commented

Thanks, but I actually hadn't changed that line in my old settings.php file! I wasn't sure which bits to replace with what, and it worked fine as it was.

I will change it now. I have my database username, password and database name, but I'm not sure what to put for 'host' or 'localhost' -- my URL?

EDIT: Just changed it, leaving 'localhost' as 'localhost' and it no longer redirects to install.php -- but it still doesn't trigger anything (white screen of death).

chadchandler’s picture

chadchandler commented

Right click the settings.php file if you are using a FTP client and check the permissions, and make sure write is enabled.

Change back to read only afterwards. White screen could also mean you need to allocate more memory. However, try what I just posted first.

annabellisimo’s picture

annabellisimo commented

Thanks for the advice. Write wasn't enabled, so I made the change, but update.php still does nothing.

I'm not sure about the memory issue, I know I sound retarded but do you mean disk space? I upgraded my hosting plan earlier today and so I've just added loads more space.

annabellisimo’s picture

annabellisimo commented

I've just gone through the install with a fine toothed comb and discovered my FTP client hadn't uploaded the contents of a couple of sub-folders. Will fix that and see if it fixes the update problem.

That will teach me for trying to learn Drupal while switching to a Mac and a new FTP client all at the same time.

eva’s picture

eva commented

you might want to recheck your settings file for two things:

1. as suggested above - make sure that your settings.php file has writable permissions (777 is what i used - make sure you change it back when done)
2. i realized that in my tired stupor i put the specific db information in the example line, not in the line that's actually read:

make sure it's the line with the dollar sign looking character that's below the */:

*/
$db_url = 'mysql://dbusername:dbpassword@localhost/dbname';
$db_prefix = '';

my update then occurred the way it should - now i'm dealing with the fallout errors;)

good luck and hope that helps,
eva

my sites: http://www.selfesteemcommunication.com

annabellisimo’s picture

annabellisimo commented

Glad to know I'm not the only one. Once I found the sub-folders my FTP client had left empty, the update worked -- now just discovering all the other bits it half-uploaded.

I obviously need to find a better FTP client for Mac.

Thanks so much for your help everyone!

Bunker-1’s picture

Bunker-1 commented

*off topic*

I don't know which FTP client you use, but try transmit or if you prefer freeware cyberduck.

Btw I had the same problem, because I replaced my settings.php file but I just filled in the right details and it went straight on to the update.php :-)

kornbread’s picture

kornbread commented

This is the best piece of advice on this topic!

I'm sure this is normal information for most people, but it would have been nice if the Upgrade.txt had this information in it.

Thank you very much for helping me sleep comfortably tonight. :)

asb’s picture

asb commented

The same happens here, when I'm upgrading Drupal 5.2 to 5.3; it's absolutely reproducable on five different Drupal sites.

I'm working on my server via SSH, where I'm downloading the archive with wget; I'm uncompressing the file locally on the server, where I'm overwriting the old installation files with the new ones.

When accessing update.php in the browser, it redirects to the installer script which forces me to enter database name, db username and db password; this requires granting write permissions for /sites/default/settings.php (chmod 777); then the installer recognizes, that Drupal is already installed and offers me finally to access update.php (*cool*), whichs works fine. After this, I have to remove write permissions from /sites/default/settings.php (chmod 755), and the update is done.

I had never before such an behaviour when updating/upgrading Drupal, and I'm running it for several years.

Hope this helps,
Regards, -asb

carusen’s picture

carusen commented

This just happened to me when upgrading from drupal 6 to 7. Fixing settings.php works.