By Konstantin Boyandin on

Greetings,

Looks like this is a popular problem. I have disabled all the modules, logged as user id 1, removed all by files directory, copied new Drupal distribution, called the update.php script and all the hell broke loose. The missing fields errors, and so on, and when I manually renamed them, the site used to display 'Page not found'.

MySQL: 4.1.19, PHP 4.4.2 (CGI mode)

I tried to return everything back, but when I renamed DB tables fields back, 4.6.6. won't work as well, some of content was damaged. The obvious way is to restore DB backup and leave things as they are, but I need at least the feature of 4.7.2 - to assign input filtering formats to any role.

The same happened to my second Drupal site, all screwed up. I didn't try to update the third site and chose to transfer the content manually, even though it's very slow.

Methinks the update.php script should be more foolproof and much more tested - I wasted two days trying to upgrade and the sites were down almost all the time.

The clean installation of 4.7.2 works perfectly.

All the best,

Konstantin

⋅ Categories: Drupal 4.6.x

Comments

killes@www.drop.org’s picture

killes@www.drop.org commented

Without the actual errors you encountered we can't help you. The problem is certainly not popular.
--
Drupal services
My Drupal services

--
Drupal services
My Drupal services

Konstantin Boyandin’s picture

Konstantin Boyandin commented

Unfortunately, I had no time to post all the MySQL/PHP error messages here and wait for feedback, since all I needed was to have the sites back online.

I say 'popular', since I have read many complaints about update.php being unable to modify the DB schema ('theme' field missing, unknown field 'access' etc).

All I saw after all the DB tables have been corrected was blank screen. There are no hints how to discover the origin of problem quickly in such a case.

Next time I will make a copy of the site on my local computer and post all the problems here, before applying any changes to the real site. I didn't think update.php would trash the DB.

I haven't incurred any code changes manually - only modules available from this site.

Thanks!

ciric@drupal.org’s picture

ciric@drupal.org commented

I agree with Konstantin, upgrading from 4.6.6 (or 4.6.5) to 4.7.x is a very popular problem.

Please read all the posts referring to 4.7.2 and update.php and the charset modification.

Please, we need a more reliable update.php.

I did not find any answer to many posts referring to the correct choice of update number: 129 is shown automatically but it is not good at all and we cannot try all the possible choices up to 182.

For instance this post: http://drupal.org/node/67468 was not answered.

Does anybody know what is the good update choice when upgrading from 4.6.6 to 4.7.2?

Riccardo