Error handling 'data' column in D6 file fields

What type of field is field_fichier_joint_innovation? What does the source table for that field look like (what is the name of the column containing the description)?

OK, this popped up in a project I'm involved with, I now know that #1971778: Migrate the image data (alt, title and description) by the Wizard is the source of the problem, looking into it...

OK, fix committed.

I get similar errors mapping the image Alt field on CCK image fields.

The source shows the Alt subfield as available. I'm not sure where this fails. It all works fine on CCK Images that don't have the ALT field enabled.

Looking at the D6 data structure, it is embedded in a '_data' column with this string: a:12:{s:3:"alt";s:10:"Date Night";s:3:"fid";s:2:"2...
Is there a way to pull from this column directly?

On import this message is returned:

Migration failed with source plugin exception: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'f.field_event_image_alt' in 'field list'

Here is the field mapping code from my module:

    $this->addFieldMapping('field_event_image_main', 'field_event_image')
         ->sourceMigration('JakesFile');
    $this->addFieldMapping('field_event_image_main:file_class')
         ->defaultValue('MigrateFileFid');
    $this->addFieldMapping('field_event_image_main:preserve_files')
         ->defaultValue(TRUE);
    $this->addFieldMapping('field_event_image_main:title')
         ->defaultValue(t('(c) 2013 Jakes on the Lake'));
    $this->addFieldMapping('field_event_image_main:alt', 'field_event_image:alt')
         ->defaultValue('');
    $this->addFieldMapping('field_event_image_main:language')
         ->defaultValue(LANGUAGE_NONE);

drush mfd shows:

EventNode Destination Fields
...
 Event Main Image                                                                     field_event_image_main
 Option: Implementation of MigrateFile to use                                         field_event_image_main:file_class
 Subfield: Language for the field                                                     field_event_image_main:language
 Option: Boolean indicating whether files should be preserved or deleted on rollback  field_event_image_main:preserve_files
 Subfield: String to be used as the alt value                                         field_event_image_main:alt
 Subfield: String to be used as the title value                                       field_event_image_main:title
...

drush mfs shows:

EventNode Source Fields
...
 Event Image                              field_event_image
 Event Image subfield                     field_event_image:list
 Event Image subfield                     field_event_image:alt
...

drush mm shows:

 Destination                            Source                          Default                   Description                                                                                                                       
 field_event_description                field_event_description
 field_event_description:format         field_event_description:format
 field_event_image_main                 field_event_image
 field_event_image_main:alt             field_event_image:alt
 field_event_image_main:file_class                                      MigrateFileFid
 field_event_image_main:language                                        und
 field_event_image_main:preserve_files                                  1
 field_event_image_main:title                                           (c) 2013 Jakes on the Lake
 field_legacy_nid                       nid                                                         We have a common field to save the D6 nid

In populateSourceFieldInfo() on line 142 of file migrate_d2d/d6/d6.inc there is a section which checks if the widget has custom_alt assigned and if so exposes a new field with an _alt at the end of the field name:

if (!empty($widget_settings['custom_alt'])) {
  $columns[$field_name . ':alt'] = $field_name . '_alt';
}

This means those fields will be checked for the alt rather than getting it from the field_n_data field as it should.

Same problem here, it is impossible to migrate field with alt enabled.

Same here, and my field is actually on the content type table, so I can't migrate the content type at all.

Line 104 in 'migrate_d2d/d6/node.inc'.

<?php
- (strpos($display_name, ':list') || strpos($display_name, ':description'))) {
+ (strpos($display_name, ':list') || strpos($display_name, ':description') || strpos($display_name, ':alt') || strpos($display_name, ':title'))) {
?>

This works for me, is this solution correct?

#11 worked for me!

A patch (for anyone who's in need of one) based on the commit from #4 (http://drupalcode.org/project/migrate_d2d.git/commitdiff/f87484fc53d036e...) and the fix in #11.

Just in case anyone else is looking for it.

Attached is a patch that does not include the changes that were already committed to the dev branch.

#15 solves the error SQLSTATE[42S22]: Column not found: 1054 Unknown column [error] 'f.field_image_title' in 'field list' for me.

Confirmed #15 fixes

Migration failed with source plugin exception: SQLSTATE[42S22]:      [error]
Column not found: 1054 Unknown column
'f.field_news_image_landscape_alt' in 'field list'

Thank you very much!

I had the same problem and has been solved by #15.
Thanks.

Confirmed #15 applies and resolved issue.

Committed, thanks.

I'm still getting Column not found: 1054 Unknown column [error] 'f.field_image_title' in 'field list' when the field "image" is in its own table in D6. We can't just call fieldExists("content_type_{$bundle}", "{$field_name}_title") when the column in question lives in content_field_image and not content_type_MYTYPE.

I've been trying to reproduce this issue without success. I've installed the latest filefield and imagefield modules on the D6 site, created two image fields on my blog content type - one single value so it's stored in content_type_blog, and one multi-value so it's stored in content_field_images. The one issue I did find was that the alt/title/description fields weren't being exposed as available source fields, but that shouldn't affect what happens at run time. Anyway, I mapped alt/title for both fields (no description field in D7) and migration successfully populated them without error.

There shouldn't be any recent change affecting this (since 11/13, anyway), but could you humor me and try it with the 2.6-rc2 version of migrate and latest -dev of migrate_d2d? Any more details to offer about your mappings and environment?

I have committed the fix to expose the fields.