Following the advices to upgrade drupal from 5.10 to 6.4
- cck was updated to the recent version 5.x-1.9
- all custom modules (inclusively cck) were deactivated
- Drupal was upgraded to 6.4
- after upgrading some other modules
- the old cck directory was removed and
- cck-6.x-2.x-dev.tar.gz was extracted and activated again
- when running update.php some error messages appear:
user warning: Unknown column 'nf.active' in 'where clause' query: content_field_instance_read /* drupaladmin : content_field_instance_read */ SELECT * FROM node_field_instance nfi JOIN node_field nf ON nfi.field_name = nf.field_name WHERE nf.active = 1 AND nfi.widget_active = 1 AND nfi.type_name = 'adresse' ORDER BY nfi.weight ASC, nfi.label ASC in /srv/www/htdocs/drupal/sites/all/modules/cck/includes/content.crud.inc on line 455.
and
user warning: Unknown column 'nf.active' in 'where clause' query: content_schema /* drupaladmin : content_schema */ SELECT * FROM node_field_instance nfi LEFT JOIN node_field nf ON nf.field_name = nfi.field_name WHERE nf.active = 1 AND nfi.widget_active = 1 in /srv/www/htdocs/drupal/sites/all/modules/cck/content.install on line 183.
Checking the sources leads to the assumption that function content_instance_tablename (in content.module) does not recognize the right version number (because cck was reactivated?):
if (is_null($version)) {
$version = variable_get('content_schema_version', 0);
}
return $version < 6001 ? 'node_field_instance' : 'content_node_field_instance';
A workaround seems to be to redo update.php several times (3 times?)
Comments
Comment #1
yched commentedThks for reporting this.
Apart form the CCK bundle itself, were there other CCK-related modules (like date, imagefield, filefield...) that were updated in the same pass as CCK ?
Comment #2
yched commentedhttp://drupal.org/node/198502#comment-1009128 was marked duplicate
Comment #3
schildi commentednot in the same pass. I try to keep problems as small as possible.
Regards
Comment #4
karens commentedIf you had other CCK-related module in the modules folder, even if they were not enabled, they get updated in update.php. This is new behavior in D6 which automatically updates disabled modules. I know that imagefield and filefield have some update problems, so the question is whether any of these were in the modules folder when you updated.
Comment #5
schildi commentedYes there were some CCK modules like imagefield, text and others (see screen shot attached).
The screen shot was taken when I repeated the complete migration.
Comment #6
karens commentedImagefield updates are broken. See #296195: Imagefield widget upgrades aren't working.
Comment #7
karens commentedI have changed the update instructions to recommend that you leave all non-core CCK modules out of the modules folder until core CCK is updated and working, and then add other non-core CCK modules to the folder one at a time and enable them as you do. That should make sure core CCK gets updated without problems and help you tell which other modules are broken. Yched also added other checks to the install process to keep things from running before the dependencies are installed.
If you still have a backup I would go back and start over, using the latest code and the new instructions.
Comment #8
schildi commentedThank you very much, Karen!
I will get it a try next days and let you know about the results.
Comment #9
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.