Posted by thekenshow on February 26, 2010 at 6:06pm
I'm posting this because I just spent way too long trying to figure out why all CCK fields were suddenly missing (absent, not showing up) as destination fields on the mapping page of a content set for the Migrate module. The answer is in plain site on the Migrate project page and discernible in the CHANGELOG.txt.
Migrate Extras. Optional, but for releases after Beta 4 you need this module to be able to migrate CCK fields, as well as other contrib modules previously supported natively in Migrate.
Of course, I didn't read either of those after a snap upgrade recently (drush makes it too easy) and I failed to turn up anything in the many searches I tried. Hopefully this post will save some other reckless admin a bit of time.
Comments
Thank you
I used about 2 hours on this problem untill I found your answer. Now it works. Only made an account now to thank you :D
Thank You!
Thank you!! I also just spent some 2 hours trying to figure that one out. Thanks sooo much!!
migrate requires migrate_extras module to support cck fields
Thanks for posting the solution :)
If your fields are still not
If your fields are still not showing, make sure you spelled the destination correctly! Surprisingly there's no error if you misspell it - just no CCK fields.
$this->destination = new MigrateDestinationNode('local_service');