By calebgilbert on

Am trying to upgrade from 4.6.6 to 4.7.2 and I just know that I am not using the right schema version. I tried using the update.php file to figure it out - which is when it really gets weird.

This is all there is in the update.php file:

    $sql_updates = array(
      '2004-10-31: first update since Drupal 4.5.0 release' => 110,
      '2004-11-07' => 111, '2004-11-15' => 112, '2004-11-28' => 113,
      '2004-12-05' => 114, '2005-01-07' => 115, '2005-01-14' => 116,
      '2005-01-18' => 117, '2005-01-19' => 118, '2005-01-20' => 119,
      '2005-01-25' => 120, '2005-01-26' => 121, '2005-01-27' => 122,
      '2005-01-28' => 123, '2005-02-11' => 124, '2005-02-23' => 125,
      '2005-03-03' => 126, '2005-03-18' => 127, '2005-03-21' => 128,
      // The following three updates were made on the 4.6 branch
      '2005-04-14' => 128, '2005-05-06' => 128, '2005-05-07' => 128,
      '2005-04-08: first update since Drupal 4.6.0 release' => 129,
      '2005-04-10' => 130, '2005-04-11' => 131, '2005-04-14' => 132,
      '2005-04-24' => 133, '2005-04-30' => 134, '2005-05-06' => 135,
      '2005-05-08' => 136, '2005-05-09' => 137, '2005-05-10' => 138,
      '2005-05-11' => 139, '2005-05-12' => 140, '2005-05-22' => 141,
      '2005-07-29' => 142, '2005-07-30' => 143, '2005-08-08' => 144,
      '2005-08-15' => 145, '2005-08-25' => 146, '2005-09-07' => 147,
      '2005-09-18' => 148, '2005-09-27' => 149, '2005-10-15' => 150,
      '2005-10-23' => 151, '2005-10-28' => 152, '2005-11-03' => 153,
      '2005-11-14' => 154, '2005-11-27' => 155, '2005-12-03' => 156,
    );

... so in update.php the schema numbers only go to 156 but on the update selector itself (via the browser when I'm pointed at http://example.com/update.php) the schema id's go all they way to 180'ish.

The default schema that is autoselected puts me on 129 which is for 4.6.0. and the date for 129 is 2005-04-14.

The changelog for 4.6.6 however gives a date of much, much later - 2006-03-13.

So update.php doesn't list anything that matches that date and the default choice of 129 leaves me with a non-workable upgrade.

Anyone know the scheme number to choose for 4.6.6 to 4.7.2 - or how to figure it out myself...

⋅ Categories: Drupal 4.7.x

Comments

ciric@drupal.org’s picture

ciric@drupal.org commented

Unfortunately I do not have an answer, but the same problem.

I post this to try to have some answer from Drupal staff. It should not be so difficult...

Riccardo

ron collins’s picture

ron collins commented

i had a similar problem. i commented out this line from update.php:

'2005-04-14' => 128, '2005-05-06' => 128, '2005-05-07' => 128,

and had to do some other tweeking (which probably is not related to your problem). from there, you can check the CHANGLOG.txt for the most recent date.

after a lot of playing with this, i would highly recommend upgrading to 4.6.8 before going any further. i used update 132 after updating to 4.6.8.

ciric@drupal.org’s picture

ciric@drupal.org commented

My solution was to first upgrade from 4.6.6 to 4.7.0 and then from 4.7.0 to 4.7.2.

The updater selected 129 for the 1st upgrade and and then 180 for the second.

I had other problems for upgrading due to accented characters like à, é, and I explain everything about my upgrade in 35 steps (sorry, in italian!) here:

http://www.ricir.net/drupal/?q=node/545

Riccardo

z.stolar’s picture

z.stolar commented

Hey Riccardo,

I've experienced the same problem with a hebrew site, after running update.php.
I suspect the problem might occure again, if update.php is ever executed to update other modules.
My italian isn't that good (It's owful). I'v translated your article through gooogle, but the translation isn't perfect. Is there any chance that you'll translate the article to english? I think it will help a lot of non-english site owners...

======================
Z.Stolar
iStolar Consulting
linnovate.net - Open Source Solutions
iStolar illustration