Upgrade from D5 to D6 - Problems

Hello quicksketch,

I do have the same problem. Attached is an archive of files extracted from my database. They feature two content types. Each of them have an imagefield field. But one of them comes from D5, the other has been created after the upgrade. Indeed, some database upgrades seem to miss. But I ran update.php, first for the filefield module, and then, for the imagefield module. On my D6 installation, I have no other image module enabled (such as imageAPI, imagecache, thickbox, that were enabled on my D5 installation).

It seems to me that manually selecting an upgrade version is usually not recommended ... Or is this the unique workaround ?

Thanks all for your help.

Regards.

Another report of the same problem (only upgrading from alpha7 to rc1, sounds like identical symptoms though). #433986: ImageField Error While Upgrading.

Also, if you ran update.php before installing FileField, you might fall victim to several nasty problems. Since ImageField will convert all its fields to FileField, but because FileField doesn't exist, none of the fields will work. I'm not really sure what will happen in this scenario, but it won't be good. #430866: Update error when filefield was not previously used might fix this problem, requiring FileField before ImageField will do anything.

I just upgraded a few days ago without any issue from D5 to D6 with Imagefield 6.x-3.0-rc1. What I did after upgraded Core and CCK was to upgrade Imagefield, ImageCache, ImageAPI and also install Filefield at the same time. Make sure you don't have anything that you don't wish to update at that time in the "modules" folder.

For Thickbox, since I enabled it after upgraded Imagefield, I found that all images in imagefield were all disappeared. That was because all the setting to display field by Thickbox fallback to "Generic Files". So, I had to go to set that again to make all images appear.

Actually, I've did that twice without any problem with Imagefield. (First is to upgrade a test site, then, did a real upgrade after that.)

I ran the update several more times without problems, both with and without FileField available. This sounds like it's going to be one of those impossible problems since no one is willing to upgrade their site multiple times to find the problem. Until a method to reproduce this problem is available, there's nothing that can be done to fix it.

Thank you very much quicksketch and abx for all your answers !

Finally, I followed gauravkumar87 (thanks for posting) advice and ran upgrade 6001 of imagefield. It executed (among others) the #6004 update, that wasn't previously performed on my database. The structure of my content_type_xxx table is now upgraded to D6. And my images are ... back ! Just one thing : I had had to modify the Display setting of my image field from "generic files" to "image", in my content type settings, to get the image on the node display.

Perhaps, the missing upgrades are due to the fact that, I first installed the FileField module, ran update.php, and THEN I installed the Imagefied module, and ran update.php a second time (I did that because, usually, the advice was to upgrade one CCK module at a time, so that potential errors occuring during one update don't interfere with the other). It seems that for filefield and imagefield modules, we have to install and enable them together, and then, run update.php one time (as said in the upgrade.txt file ....).

Hope my posts are understandable .... English is not my mother language ...

Regards.

Any Ubercart users might be interested in this separate problem: #431502: Ubercart beta 5 (and lower) not compatible with ImageField.

I'm marking this fixed as it seems that we have confirming reports that the upgrade is working when the database is in an expected state.