This seems contradicting to me!

The project page of emfield states:

FileField does not need a Drupal 7 version because it has been moved to Drupal Core! To upgrade FileField to Drupal 7, install the Drupal 7 CCK Package and use the Content Migrate to upgrade FileField to Drupal 7.

On the other side, the CCK "Migrate fields" assistant contradictingly reports:

[…]
Field: field_video
Field type: filefield
Content type(s): Text Plus, Text Plus Inline, Video
Other info: Missing field module: 'filefield'. This field cannot be migrated.
[…]

Comments

I had that error, too.

Solution?

I had the same problem. Cause I have Image FUPload widget at my filefield.
For Image FUpload issue search the table content_node_field_instance and change widget_type string to imagefield_widget and widget_module string to imagefield.

Status:Active» Closed (works as designed)

@smirnoff - That did it - thanks! (I'm guessing most other people having this problem had their image upload field using a different upload method, like ImageField Zip, or Image FUpload, as well...).

I have the same problem wiyh fupload fields. Unfortunately I don't have phpmyadmin because I use Aegir, if anyone had this same problem and used a MySQL command to fix this, please share it.

I know very little MySQL, I found this post: http://www.mydigitallife.info/how-to-find-and-replace-text-in-mysql-data...

I tried:

update content_node_field_instance set widget_type = replace(widget_type, ‘image_fupload_imagefield_widget’, ‘imagefield_widget’);

But I get this error: Unknow column 'image_fupload_imagefield_widget' in 'field_list'.

Any ideas on how to fix the command?

I have this even though widget_type and module_type are as they should. I had imagefield_crop on this site but i changed the widget before upgrade.

I also get "Notice: Undefined index: default_image in content_migrate_filefield_field_alter() (line 25 of"

Status:Closed (works as designed)» Active

I think this is still a bug.

There are lots of modules that use file filelds or image fields and just add a new widget (I'm experiencing this problem with audiofield module, see #1423656: Audio fields will not upgrade from D6 -> D7 (audiofields do not work with the CCK content migrate module)).

These fields should be able to be upgraded without us having to manually change the database to fool the system into thinking the fields were provided by filefield module in this way.

ll said #8. Facing this issue here and am lost. Any tips for correcting? running mysql and php myadmin.

+1 on #8 we shouldn't be running MySQL commands to successfully upgrade our Drupal sites.

Sure it's a bug. There should be no need to manually run SQL commands on upgrade.

In the meantime, the SQL command that allows one to upgrade:

update {content_node_field_instance}
   set widget_type = 'imagefield_widget', widget_module = 'imagefield'
          where widget_module = 'uploadfield';

You can run this snippet using Devel module. You don't need PHPMyAdmin os SQL access for this (though you must remove the "{}" if you run the SQL directly on the database).

Component:CCK in core» upgrade path
Priority:Normal» Critical

+1 on #8 we shouldn't be running MySQL commands to successfully upgrade our Drupal sites.
As I was using 'Image FUPload ', solution on #3 worked nicely for me.

Setting priority to critical since this don't let you upgrade between versions.

#3 worked for me too, million thanks!