Closed (fixed)
Project:
Drupal-to-Drupal data migration
Version:
7.x-2.x-dev
Component:
D6-specific
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
7 May 2013 at 00:32 UTC
Updated:
13 May 2014 at 18:40 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
mikeryanNot at the moment, looks like we have to hack in support for this as we did for the body...
Comment #2
mikeryanDoesn't look too hard, please give this a try.
Comment #3
mikeryanHad a chance to actually test it, and that patch was incomplete. I've now committed a working implementation.
Comment #5
bkerwin commentedThanks Mike. I grabbed the latest dev version and I see code for it in d6/d6.inc. It doesn't seem to work for me; I should just be able to do:
$this->addFieldMapping('field_profile_name', 'field_profile_title');Where 'profile' is the Content profile content type on the source and field_profile_name is my destination field, correct?
Comment #6
bkerwin commentedComment #7
mikeryan"needs review" means there's a patch that needs review, "active" is what you set a support request to if you're expecting help.
If you go to the detail page for your user migration, on the Source tab, you should see 'field_profile_title' and 'field_profile_body' along with any CCK fields from the profile type (assuming the D6 site has titles and bodies enabled on that content type) - are you not seeing them?
Comment #8
bkerwin commentedMy bad on the issue status, still learning my way around.
I actually set up my migrations before the new UI for migrate_d2d existed so when I go there now it's asking for db credentials etc. This is what I get by doing drush mfs on this migration task (Users):
Somewhat relatedly to the other issue I have (https://drupal.org/node/1989466) the subfields for the location field don't appear which is probably why I can't get that to work.
Comment #9
mikeryanDon't go through the import wizard, go to the Migrate dashboard, click on the group name, then click on the name of the specific migration to get to its details page.
I can't explain why you're not seeing the profile title there, I would double check the content type's D6 configuration and make sure the title is enabled there. If that looks OK, all I can suggest is debugging the code to see why migrate_d2d isn't identifying the title.
Comment #10
bkerwin commentedAh ok.. when I go to admin/content/migrate/groups/default, I get the following messages in the error area:
Looking at that file, that's where it's checking for the title and body. The title and body are definitely enabled in the source content type.
The detail page for the group shows pretty much the same info I gave before with some additional details. Same list of fields, no field_profile_title or field_profile_body (the source content type is Profile).
Comment #11
mikeryanComment #12
shaundychkoI removed the has_body condition from the following since there's already a test for has_body a few lines later. The attached patch fixes the error in comment #10 which is a result of having a content_profile node type which has the body disabled, in which case $type_info is NULL since the content_profile type doesn't satisfy the has_body condition. This also fixes getting the content_profile node title since, in the case where the body is disabled, but the title is still used, $type_info would nevertheless still be NULL since, again, the has_body condition fails. Furthermore, it turns out that in my case using the content_profile node type doesn't sufficiently 'uniquify' the title field, so I appended '_node_type' to the $bundle name to enhance the uniqueness. There's also a check that $type_info is an object.
Comment #13
bkerwin commentedThank you very much Shaun! This patch did the trick and I have the profile titles migrating perfectly now.
Comment #14
igorik commentedpatch in #12 is working for me, please add it into dev version at least,
it is from July 19th....
Comment #15
pianomansam commentedPatch from #12 works for me as well!
Comment #16
oadaeh commentedI've modified the patch in #12 to check if the title and body are empty before performing their operations.
Comment #17
mikeryanCommitted, thanks.