• Changed field type: The 'field_image' field type will be changed from 'filefield' to 'image'.
  • Missing widget: The 'image' widget is not available for the field_image field, it will be set to the default widget.
  • Missing formatter: The 'manufacturer_image_linked' formatter used in 1 view modes for the field_image field is not available, these displays will be reset to the default formatter.
  • Missing formatter: The 'manufacturer_image_default' formatter used in 2 view modes for the field_image field is not available, these displays will be reset to the default formatter.

Why can't it figure out the correct widget?

I manually recreated the "manufacturer_image" image style because image styles apparently don't get migrated. So now why can't it figure out the display?

I can still change the D6 site, so I can fix things there if it helps.

Comments

We have the same problem.

Did you already solve this? I'm stuck with this error. After upgrade the image is gone.

Priority:Normal» Major

Nope, still waiting for some advice.

I'm testing in local and for me it's OK.
Because of poor English, I perhaps miss your approach.
As for me, I recreated an image style same as D6 imagecache presset and used it in "manage display " tab.

Did you then have to update the "manage display?" On my test site, I could, but after the first of the year I have a customer with 36 content types, most of which have image fields; I don't want to have to all that manually.

Yes I had to change the image style in "manage display". Even though I had created first the image style needed.
So you're right, it's a hard job if so many content types with images.
I'd like upgrade paths would be finished soon, other cck upgrade problems are waiting to be fixed.

The worst part is that Field conversion is problematic, so I always do a test migration first. I'm going to have to do all that manual work TWICE.

I don't think we can resolve the "reset to the default formatter" warning prior to actually migrating a field. The field needs to be associated with a content type before we can set a formatter. So I'm thinking we need to...

  1. migrate the fields
  2. migrate the styles (see below)
  3. associate the style with the content type and field

That's me just thinking out loud. I could be missing some order issue.

I used the approach in #1316472-4: Upgrade your imagecache presets to D7 image styles via features to migrate my D6 ImageCache Presets to D7 Image Styles. It's not completely automatic, but if you have a lot of presets it can definitely help avoid the tedious process of re-creating all of them manually.

I'm not sure if we can still access the required D6 data after field migration to be able to programmatically re-create the associations between the content types and D7 styles. I'm still working my way through a D6 => D7 upgrade.

i also have the same problem. help. i can see most of the thing accept image field.

My recommendation is to set the widget to "Image" on your D6 install first. When you go to migrate to D7, it will still come up with the Missing widget: The 'image' widget is not available for the field_image field, it will be set to the default widget. however it "should" migrate just fine.

I had FUpload installed as the imagefield widget on my D6 install and it would not migrate PERIOD. I had to roll back and change the widget type from Fupload -> Image, even though it still gave me the error about the 'image' widget.

Regarding the:

  • Missing formatter: The 'manufacturer_image_linked' formatter used in 1 view modes for the field_image field is not available, these displays will be reset to the default formatter.
  • Missing formatter: The 'manufacturer_image_default' formatter used in 2 view modes for the field_image field is not available, these displays will be reset to the default formatter.

From what I can tell, because the imagecache presets aren't quite the same for modules in D7 to recognize them. I did comment #4 approach from the #1316472-4: Upgrade your imagecache presets to D7 image styles via features which brings in the presets just fine, however views still won't recognize them. From what I can tell, when you install views, it completely discards all image fields and you have to manually re-create them. A huge pain if you have a lot of views dealing with images...

Also from my experience, Panels won't recognize ANY of the newly migrated fields either. You will have to manually re-add the panel content for any "cck" fields that were previously used in D6.

Because of the issues with Panels & Views, I recommend leaving your production site alone. I've upgraded sites live in the past (plenty of backups, don't worry) even though I know it's against best practice. However, on a site with fields in a lot of views or panels that will have to manually be re-generated by hand, I recommend downloading and installing the Acquia Dev Desktop If you aren't familiar with it, it is a full blown apache, php & mysql server package that is designed especially for use with Drupal. Pull your live database and production files to your local computer and do all of the upgrade there. Then you can reference the settings on the live site, with the ones on your local upgrade site to get everything set back up the way it should be.

Just my $0.02

Status:Active» Needs review
StatusFileSize
new2.26 KB

Here's an (untested!) patch that is what I am currently thinking the problem is. Fields using imagecache presets aren't being converted to d7 image styles...

The same as #10 with a syntax fix to make it work. Tested!

Issue tags:+project, +Drupal.org D7

(increasing visibility as we want this for d.o)

Status:Needs review» Fixed

Committed #12 (slightly adjusted comments)
Thanks !

Status:Fixed» Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

I think an update in the cck module does brake the patching. I can't patch it anymore.

patch -p1 < 1339962-filefield-image-formatter-convert-11.patch
patching file modules/content_migrate/modules/content_migrate.filefield.inc
Hunk #1 FAILED at 80.
1 out of 1 hunk FAILED -- saving rejects to file modules/content_migrate/modules/content_migrate.filefield.inc.rej

I really need to transfer those filefields from d6 to d7, so this is a huge deal for me at the moment.

Anyway... patched the file manually, but i still cannot import the cck fields from d6 to7.

Still getting errors like these, and no images get imported:
https://www.dropbox.com/s/2x7pmhxpmwdnys4/cck-problem1.jpg.png

@nicjasno Have you tried changing the "image widget" on D6 to a default state? It might be one of the widgets that isn't upgrading and hosing the rest of the update. For example, if you're using some sort of multi-upload for an imagefield and it isn't allowing the upgrade...

The other place to check is "node revisions". If you have them enabled, it might cause you problems though I think it was supposed to have been fixed by now. On more than one site, I've had to use the "revision deletion" module to blow away all node revisions and then disable it from the content type.

Just a few suggestions off the top of my head.

(Make sure you make a backup before any major changes like deleting the node revisions)

Usually it works. I don't understand why you had to patch it manually. Check that. The patch was committed last year. Use the latest dev (which fixes a few other major bugs), but it is also the sole 7.x tar that you can download.

I patched it manually (replaced the code), but it still does not work.

I have only 2 options for the widget. Image and file upload. Field is a FileField.
Initially i had the widget as image, and changed it to file upload to try again, yet the migration still dreams of the image widget.

I'm really running out of ideas. :(

Did you solve this? I am dealing with the same issue...

The error still appears, although I imported all imagecache presets, other fields are imported correctly except image fields.
I also applied the patch but still no good in retrieving any successful result.
All other required modules are in place cause I checked thoroughly.
Maybe should the widget type in drupal 6 be file upload, because that transferred without any problem, I mean is just a thought...
Any feedback is greatly appreciated
Thanks