migrate fields flawed for multi-lingual sites? [#1122062]

I'm using the latest CCK dev in a drupal 7 local dev site that I upgraded from drupal 6 for testing purposes.

I have an event node type with half a dozen fields: fee, instructor, subtitle, date, image, etc. I ran the migrate tool and it seemed that the fields migrated. some fields show on some nodes. There are database tables that reflect the fields and they have rows full of the correct field data. if i view a node in question, it shows the field data. but in the corresponding node edit form, the fields are blank. also blank in views live preview.

Is this a CCK problem or a fields in core problem, or a node edit problem? what information do I need to produce to figure this out?

Comments

Comment #1

cpelham CreditAttribution: cpelham commented 9 April 2011 at 21:07

This may have something to do with it:

http://drupal.org/node/1024174

investigating...

Comment #2

cpelham CreditAttribution: cpelham commented 10 April 2011 at 04:40

Title:	long text fields don't seem to migrate...or migrate but don't display	» migrate fields flawed for multi-lingual sites?
Priority:	Normal	» Major

I am reposting this as it may be a solution (the problem apparently being that migration does not work correctly for multi-lingual sites), but the solution below is definitely NOT a practical solution for large multi-lingual sites. I cannot go through thousands of tables and correct the language one by one. That would take forever! What is the programmatic solution?

I just had the same issue and
Posted by gnite on February 16, 2011 at 4:35pm
I just had the same issue and after a couple of hours i finally figured it out. It's the migration algorithm of cck. Now, fixing this a little messy:

1. Open your database with phpmyadmin
2. make a backup just in case
3. go to table field_data_field_something
4. look at the language column of the imported and new rows (create a new node with that field if you have only old ones). the imported ones will have a value of 'und' whereas new ones will have your language code

the next two steps need to be done for every single field_data_field_ table

5. delete duplicates in each table (when you edit a node with 'blank' fields they get stored in new rows)
6. change language value of each row to the one you get when creating new nodes. in my case it was 'pl' for polish
7. clear cache (important, could have saved quite some time if i had thought of that sooner)
8. everything should be fine now