My suggestion is to test the quickest method on your local machine or on yoru server having a back up handy.
because you did not keep your site up to date bewteen 5.1 - 5.3 you missed a security patch that went into settings.php. Thus make sure you manually add your $db_url information and reupload this file. as per the important note in the 5.2 release thread : http://drupal.org/drupal-5.2 _____________________________________________________________________ My posts & comments are usually dripping with sarcasm.
If you ask nicely I'll give you a towel : )
I upgraded from 5.1 to 5.3 on my local site. Everything seems OK.
@VeryMisunderstood : What do u mean by "you missed a security patch". That settings.php patch isn't included in 5.3? I think it is. Sorry if I misunderstood :P....
if you replaced your settings.php file when you did the upgrade to 5.3 you are fine. Yes the patch is in 5.3. Although I don't understand where my comment confuses you.
My intention was to draw the OP's attention to the need to replace settings.php during an upgrade from 5.1. Under normal circumstances replacing settings.php isn't necessary as this file does not normally change. Had the OP continued to use settings.php from 5.1, he/she would have missed a patched file. namely settings.php.
I was just trying to point out that it was important to replace settings.php.
. _____________________________________________________________________ My posts & comments are usually dripping with sarcasm.
If you ask nicely I'll give you a towel : )
no problem _____________________________________________________________________ My posts & comments are usually dripping with sarcasm.
If you ask nicely I'll give you a towel : )
Totally locked out of the upgrade, I rolled back. I had to start a new site, new db with the new Drupal and then transfer user accounts. Most of the content is now stuck in a subdomain.
without knowing how you tried to upgrade from 4.7.x - 5.3 theres no way for anyone to help
from a 4.7.x install you should have gone to the latest release of 4.7.x first.
with contrib mdoules disabled, move to Drupal 5 as 4.7.x modules won't work with 5 _____________________________________________________________________ My posts & comments are usually dripping with sarcasm.
If you ask nicely I'll give you a towel : )
Hey Rick,
Please tell me...as I`m a newbie to Drupal as well, was it hard to upgrade? Did you have any modules/ themes installed or was it all standard? I`m just curious...I`m delaying the whole thing for days now... :)
themes and contrib modules that were put in sites/all/modules or sites/all/themes will be fine. The settings.php file must be replaced per the security realse of 5.2. This is why it's important to update with each release. To make it easier. goto your profile and subscribe to the security newsletter.
If updating makes you nervous, you should get yourself more aquaninted with the process by creating duplicate of your site, either in a subdomain of your server, or on your local machine and applying the update there first.
as always backup your system, in the rare case that something goes wrong.
_____________________________________________________________________ My posts & comments are usually dripping with sarcasm.
If you ask nicely I'll give you a towel : )
Although I have never done this as well,...I`ll try to update local first. Unfortunately I have many customized modules that only work fur my custom design. Will these work as well? For example, I use Nodewords (http://drupal.org/project/nodewords). In it`s current release it works with Drupal 5.x-1.5. If I get this right, it is not supported in Drupal 5.3, right? Same with Pathauto: http://drupal.org/project/pathauto
modules written for Drupal 5, work with all versions of Drupal 5 hence the 5.x = version of Drupal 1.5 = version of module =
nodewords-5.x-1.5.tar.gz
see: http://drupal.org/handbook/version-info with regards to contributed modules _____________________________________________________________________ My posts & comments are usually dripping with sarcasm.
If you ask nicely I'll give you a towel : )
Comments
=-=
My suggestion is to test the quickest method on your local machine or on yoru server having a back up handy.
because you did not keep your site up to date bewteen 5.1 - 5.3 you missed a security patch that went into settings.php. Thus make sure you manually add your $db_url information and reupload this file. as per the important note in the 5.2 release thread : http://drupal.org/drupal-5.2
_____________________________________________________________________
My posts & comments are usually dripping with sarcasm.
If you ask nicely I'll give you a towel : )
I upgraded from 5.1 to 5.3
I upgraded from 5.1 to 5.3 on my local site. Everything seems OK.
@VeryMisunderstood : What do u mean by "you missed a security patch". That settings.php patch isn't included in 5.3? I think it is. Sorry if I misunderstood :P....
http://www.dobro.gr - Online community for Greek students in Bulgaria
http://simpledesigns.hopto.org - simple designs
=-=
if you replaced your settings.php file when you did the upgrade to 5.3 you are fine. Yes the patch is in 5.3. Although I don't understand where my comment confuses you.
My intention was to draw the OP's attention to the need to replace settings.php during an upgrade from 5.1. Under normal circumstances replacing settings.php isn't necessary as this file does not normally change. Had the OP continued to use settings.php from 5.1, he/she would have missed a patched file. namely settings.php.
I was just trying to point out that it was important to replace settings.php.
.
_____________________________________________________________________
My posts & comments are usually dripping with sarcasm.
If you ask nicely I'll give you a towel : )
Thanks for the explanation
Thanks for the explanation :-)
http://www.dobro.gr - Online community for Greek students in Bulgaria
http://simpledesigns.hopto.org - simple designs
=-=
no problem
_____________________________________________________________________
My posts & comments are usually dripping with sarcasm.
If you ask nicely I'll give you a towel : )
Total Breakage from 4.7.x to 5.3
That was a sleepless night I'd rather not repeat.
Totally locked out of the upgrade, I rolled back. I had to start a new site, new db with the new Drupal and then transfer user accounts. Most of the content is now stuck in a subdomain.
Upgrade was a total disaster.
=-=
without knowing how you tried to upgrade from 4.7.x - 5.3 theres no way for anyone to help
from a 4.7.x install you should have gone to the latest release of 4.7.x first.
with contrib mdoules disabled, move to Drupal 5 as 4.7.x modules won't work with 5
_____________________________________________________________________
My posts & comments are usually dripping with sarcasm.
If you ask nicely I'll give you a towel : )
woops! Good to know! I
woops! Good to know! I haven't edit my settings.php I used my old one instead. But I exchanged it now to the updated version.
Thanks for the info!
Have to do the same. 5.1 > 5.3
Hey Rick,
Please tell me...as I`m a newbie to Drupal as well, was it hard to upgrade? Did you have any modules/ themes installed or was it all standard? I`m just curious...I`m delaying the whole thing for days now... :)
=-=
themes and contrib modules that were put in sites/all/modules or sites/all/themes will be fine. The settings.php file must be replaced per the security realse of 5.2. This is why it's important to update with each release. To make it easier. goto your profile and subscribe to the security newsletter.
If updating makes you nervous, you should get yourself more aquaninted with the process by creating duplicate of your site, either in a subdomain of your server, or on your local machine and applying the update there first.
as always backup your system, in the rare case that something goes wrong.
_____________________________________________________________________
My posts & comments are usually dripping with sarcasm.
If you ask nicely I'll give you a towel : )
Hi Jabz
I actually haven't done it yet, but I'll let you know.
I have only ever done one upgrade before and that was from 4.7 to 5.2 and it went fine. I had a few contrib modules and a theme installed.
This is an excellent tutorial on how to do upgrades:
http://www.lullabot.com/videocast/upgrading_from_drupal_4_7_x_to_drupal_5_x
I am not sure what I would have done without that. If you follow that exactly, I would not worry and would go ahead.
It does seems like a little hair raising, but probably when you've done it a few times it's no big deal.
Yeha, I`ll try local
Although I have never done this as well,...I`ll try to update local first. Unfortunately I have many customized modules that only work fur my custom design. Will these work as well? For example, I use Nodewords (http://drupal.org/project/nodewords). In it`s current release it works with Drupal 5.x-1.5. If I get this right, it is not supported in Drupal 5.3, right? Same with Pathauto: http://drupal.org/project/pathauto
=-=
modules written for Drupal 5, work with all versions of Drupal 5 hence the 5.x = version of Drupal 1.5 = version of module =
nodewords-5.x-1.5.tar.gz
see: http://drupal.org/handbook/version-info with regards to contributed modules
_____________________________________________________________________
My posts & comments are usually dripping with sarcasm.
If you ask nicely I'll give you a towel : )