By Jerimee on

Do I just over write the files? Anything more to it? Precautions I should take, things I should be concerned about?

⋅ Categories: Drupal 5.x

Comments

vm’s picture

vm commented

you start by reading the 5.2 release thread, specifically the upgrade section see: http://drupal.org/drupal-5.2

Jerimee’s picture

Jerimee commented

you mean this? http://drupal.org/upgrade/

I was worried that those instructions were out of date.

vm’s picture

vm commented

as well as:

Important note
The file settings.php is one of the files containing vulnerable code. It is therefore critical to replace all of your sites' settings.php files in subdirectories of sites with the new one from the archive. After you have replaced the files, make sure to edit the value of the $db_url variable to be identical to the value in your old settings.php. This is the information that determines how Drupal connects to a database.

I don't suggest overwriting your files, I suggest deleting them so you know they are gone, then reuploading. This includes the settings.php file. make a backup of this on your local machine, so you can inspect it for the line discussed and make changes to your new one. Then upload that one to where it belongs. There are no changes to the DB thus, updating from 5.x to 5.2 is an easy task.

There is also an UPGRADE.txt file in the drupal 5.2 download that you should consider reading.

ALWAYS make a back up of your site first though, just in case.

Jerimee’s picture

Jerimee commented

Yeah, for some reason I completely missed that. That does seem like a rather "important" note. Thanks for saving me from my own carelessness.

heine’s picture

heine commented

There are two database updates. Fortunately, visiting admin will bring up the nag screen with a link to update.php.
--
The Manual | Troubleshooting FAQ | Tips for posting | How to report a security issue.

vm’s picture

vm commented

My bad. I was running a -dev release and did not have an update bewteen it and 5.2. Thanks for the correction.

jwalling’s picture

jwalling commented

This is a good starting point.
http://drupal.org/upgrade/tutorial-introduction

I plan to copy my production site to a test site, and do the update on the test site. If all goes well, I will update the production site after I do a complete backup. I also plan to wait at least one week to see if there are any reported problems with 5.2 before I do the update.

John

Jerimee’s picture

Jerimee commented

ok, so I think I successfully upgraded. keeping my fingers crossed . . .

I did get one problem. After reenabling my calendar module I got this set of errors:


    * warning: calendar_menu(CALENDAR_PATH/calendar.theme) [function.calendar-menu]: failed to open stream: No such file or directory in /home/whereisl/public_html/nc10dems/modules/calendar/calendar.module on line 43.
    * warning: calendar_menu() [function.include]: Failed opening 'CALENDAR_PATH/calendar.theme' for inclusion (include_path='.:/usr/lib/php:/usr/local/lib/php') in /home/whereisl/public_html/nc10dems/modules/calendar/calendar.module on line 43.
    * warning: calendar_menu(CALENDAR_PATH/calendar.theme) [function.calendar-menu]: failed to open stream: No such file or directory in /home/whereisl/public_html/nc10dems/modules/calendar/calendar.module on line 43.
    * warning: calendar_menu() [function.include]: Failed opening 'CALENDAR_PATH/calendar.theme' for inclusion (include_path='.:/usr/lib/php:/usr/local/lib/php') in /home/whereisl/public_html/nc10dems/modules/calendar/calendar.module on line 43.
vm’s picture

vm commented

it is possible calendar needs to be updated to work with 5.2, file a bug report using the project page.

Jerimee’s picture

Jerimee commented

I was using calendar 1.4, calendar 1.5 (the latest one) works fine.

Amon_Re’s picture

Amon_Re commented

For some reason when i click the link to update.php i doesn't seem to do anytyhing, i just get an empty page, no errors no nothing, and my database isn't being updated.

Setting the check from TRUE to FALSE (as suggested in the upgrade document) doesn't help.

EDIT: Never mind, i enabled error reporting in the script & tracked down the problem

See my concert pictures, blog and development stuff!
Visit Amon's digital home