Hi,
If I understand how the update system works correctly, the reason why you can't do that in one step is simple:
1. Let's say you are on Drupal 4.6.0 2. Let's say I am on Drupal 4.6.1 3. Now, if we both run the same process to update, one of us will get errors.
You must first get to Drupal 4.6.1 to bring updates to par with the requirements for update 130 and 131.
Each update makes changes to the database. A person on 4.5.5 will have a different looking database to a person having 4.6.0. It is virtually not possible to make all inclusive updates, as it would make the logic in the update script too complex.
If I am totally wrong here, please excuse my ignorance, as I would learn something from this too, if I am wrong in my arguments here... :-)
Regards,
Kobus
abalieno@cesspit.net 9/6/2005 1:41 PM >>>
I'm going to upgrade tomorrow but my Drpal install never autoselect the database upgrade.
Now I think the basic process is about going from 4.6.0 to 4.6.1 and then 4.6.2 and finally 4.6.3.
But how the hell I upgrade the database? I don't know what to select.
On the site it's written I have to do all the minor steps but this doesn't make sense. On the update.inc file the 4.6.0 version correspond to "update 129" and there are only "update 130" and 131 after that. While Drupal went through THREE revisions.
If the process upgrade is just about copying over the new files and perform update 130 and 131, why the hell I cannot do that in just one step?
-HRose / Abalieno
Hello, all,
I've been wondering about this as well. Obviously, the change from 4.5.5 to 4.6.0 involves changes to the db structure.
However, do any of the changes involved in the 4.6.x upgrades involve changes in the db structure, or are all the changes in the code of the core drupal files?
Because, if the db remains unchanged, and it is only the core files (ie, code) that has been changed, wouldn't it be possible to backup the settings.php file, unzip a fresh 4.6.3 release over the 4.6.0 release, restore the settings.php file, and be done with it?
So, I guess what I'm asking is: are there any db changes in the single upgrades from 4.6.0 to 4.6.1 to 4.6.2to 4.6.3?
Thanks,
Bill.
Kobus Myburgh wrote:
Hi,
If I understand how the update system works correctly, the reason why you can't do that in one step is simple:
- Let's say you are on Drupal 4.6.0
- Let's say I am on Drupal 4.6.1
- Now, if we both run the same process to update, one of us will get errors.
You must first get to Drupal 4.6.1 to bring updates to par with the requirements for update 130 and 131.
Each update makes changes to the database. A person on 4.5.5 will have a different looking database to a person having 4.6.0. It is virtually not possible to make all inclusive updates, as it would make the logic in the update script too complex.
If I am totally wrong here, please excuse my ignorance, as I would learn something from this too, if I am wrong in my arguments here... :-)
Regards,
Kobus
abalieno@cesspit.net 9/6/2005 1:41 PM >>>
I'm going to upgrade tomorrow but my Drpal install never autoselect the database upgrade.
Now I think the basic process is about going from 4.6.0 to 4.6.1 and then 4.6.2 and finally 4.6.3.
But how the hell I upgrade the database? I don't know what to select.
On the site it's written I have to do all the minor steps but this doesn't make sense. On the update.inc file the 4.6.0 version correspond to "update 129" and there are only "update 130" and 131 after that. While Drupal went through THREE revisions.
If the process upgrade is just about copying over the new files and perform update 130 and 131, why the hell I cannot do that in just one step?
-HRose / Abalieno
However, do any of the changes involved in the 4.6.x upgrades involve changes in the db structure, or are all the changes in the code of the core drupal files?
There are some changes to the db, yes.
Because, if the db remains unchanged, and it is only the core files (ie, code) that has been changed, wouldn't it be possible to backup the settings.php file, unzip a fresh 4.6.3 release over the 4.6.0 release, restore the settings.php file, and be done with it?
So, I guess what I'm asking is: are there any db changes in the single upgrades from 4.6.0 to 4.6.1 to 4.6.2to 4.6.3?
Yes, there are changes and you need to run update 130 and 131 (as far as I know the 4.6.0 corresponds to update 129) to use the 4.6.3 without a problem.
What I wonder is why I cannot do this just by running them through the very last package.
What I wonder is why I cannot do this just by running them through the
very
last package.
What do you mean by "running them through the very last package. " ? The update is very easy, put all new 4.6.3 files on your server and run update.php, it will automatically check the last update you went through (it must be 129) and then run 130 and 131 and that's it...
What do you mean by "running them through the very last package. " ? The update is very easy, put all new 4.6.3 files on your server and run update.php, it will automatically check the last update you went through (it must be 129) and then run 130 and 131 and that's it...
What I mean is that Drupal site doesn't make sense: "For the most trouble-free transition from an existing installation, it is recommended that you first upgrade to Drupal 4.6.2. "
And if you go see Drupal 4.6.2 you see the same phrase repeated with Drupal 4.6.1, hinting that I should patch each subversion on its own instead of just jumping to the last package available. Which doesn't make sense.
-HRose / Abalieno
Only if you update from very old versions can you best first update to an intermediate version. From 5.3..x you can best first got to a 4.5 then onwards to 4.6.3
But updating from 4.6.1 to 4.6.3 can be done without steps inbetween.
I fail to see what all the fuzz is about.
Op dinsdag 06 september 2005 21:30, schreef Abalieno:
What do you mean by "running them through the very last package. " ? The update is very easy, put all new 4.6.3 files on your server and run update.php, it will automatically check the last update you went through (it must be 129) and then run 130 and 131 and that's it...
What I mean is that Drupal site doesn't make sense: "For the most trouble-free transition from an existing installation, it is recommended that you first upgrade to Drupal 4.6.2. "
And if you go see Drupal 4.6.2 you see the same phrase repeated with Drupal 4.6.1, hinting that I should patch each subversion on its own instead of just jumping to the last package available. Which doesn't make sense.
-HRose / Abalieno
Regards, Bèr
Hi Bèr,
We have a very old Drupal (4.3.1) running some really valuable sites for the content management community (CMS-News.org, CMS-Forum.org) and are trying to upgrade in the recommended steps 4.3.1 > 4.4.2 > 4.5, etc.
We get a very odd result (a blank page) when we run the update.php script.
We backed everything up, added two new required fields to the database, then ran the update.php script for one of our sites (CMS-News).
The results of clicking on the cms-news.org/update.php?op=update (just once) was a blank page.
We also get a blank page when we request the updated site http://www.cms-news.org.
We then tried the same operations for the CMS Forum site. Just to check we were connecting properly, we requested http://cms-forum.org *before* we added the two new fields to its system table, and it came back (properly) with an error message saying "throttle" field was missing.
This told us that the new 4.4.2 code was running.
Any advice on how to get past this blank page? If we figure it out, we will add some notes on how to update to the drupal.org update discussion.
Thanks.
Bèr Kessels wrote:
Only if you update from very old versions can you best first update to an intermediate version. From 5.3..x you can best first got to a 4.5 then onwards to 4.6.3
But updating from 4.6.1 to 4.6.3 can be done without steps inbetween.
I fail to see what all the fuzz is about.
Hello,
I suspect either a memory issue, or another php problem. Logs are your friend. You can best have a look in your error logs and post them to this thread. Please only post the relevant errors.
Bèr
Op dinsdag 06 september 2005 23:00, schreef Bob Doyle:
Hi Bèr,
We have a very old Drupal (4.3.1) running some really valuable sites for the content management community (CMS-News.org, CMS-Forum.org) and are trying to upgrade in the recommended steps 4.3.1 > 4.4.2 > 4.5, etc.
We get a very odd result (a blank page) when we run the update.php script.
We backed everything up, added two new required fields to the database, then ran the update.php script for one of our sites (CMS-News).
The results of clicking on the cms-news.org/update.php?op=update (just once) was a blank page.
We also get a blank page when we request the updated site http://www.cms-news.org.
We then tried the same operations for the CMS Forum site. Just to check we were connecting properly, we requested http://cms-forum.org *before* we added the two new fields to its system table, and it came back (properly) with an error message saying "throttle" field was missing.
This told us that the new 4.4.2 code was running.
Any advice on how to get past this blank page? If we figure it out, we will add some notes on how to update to the drupal.org update discussion.
Thanks.
Bèr Kessels wrote:
Only if you update from very old versions can you best first update to an intermediate version. From 5.3..x you can best first got to a 4.5 then onwards to 4.6.3
But updating from 4.6.1 to 4.6.3 can be done without steps inbetween.
I fail to see what all the fuzz is about.
-- Bob Doyle Editor In Chief, CMS Review - http://www.cmsreview.com Technology Adviser, CM Pros - http://www.cmprofessionals.org Contributing Editor, EContent Magazine - http://www.econtentmag.com/About/AboutAuthor.aspx?AuthorID=155 CEO, skyBuilders - http://www.skybuilders.com 77 Huron Avenue Cambridge, MA 02138 617-876-5678
Regards, Bèr
- Now, if we both run the same process to update, one of us will get
errors.
You must first get to Drupal 4.6.1 to bring updates to par with the requirements for update 130 and 131.
But the point is that the update.inc file in the last drupal package already contains ALL the upgrade steps of the previous versions. In fact the update 130 is probably the 1.6.1, while update 131 is for 1.6.2.
I really don't see why I cannot execute them one after the other since upgrading through the two packages does the exact same thing.
-HRose / Abalieno
-
Abalieno -
Bill Fitzgerald -
Bob Doyle -
Bèr Kessels -
Kobus Myburgh -
Nicolas Tostin