Closed (duplicate)
Project:
Migrate Extras
Version:
6.x-1.x-dev
Component:
Location
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
8 Mar 2010 at 07:40 UTC
Updated:
21 Jun 2011 at 01:19 UTC
see #459236: Location Integration
I still need location cck for importing data.
One crazy idea I have is to use the already written node location to import the data, and then to use rules with some php to copy the node location data to the cck location fields...
on getting a location cck migrate extra in, would a bounty help? I can contribute $100. Contact me.
Thanks.
Comments
Comment #1
yesct commentedtagging.
Comment #2
yesct commentedI wonder if this snippet, posted in a comment to the lullabot article, might help?
http://www.lullabot.com/articles/drupal-data-imports-migrate-and-table-w...
Comment #3
yesct commentedI tried making a module (called mymodule) and putting just the code from the lullabot comment in it, enabled it, did an import, but none of the location cck fields were filled in.
I did make sure the machine name for it was field_location.
do I need to replace TABLENAME_COLUMNNAME_city etc with specifically my column name?
Comment #4
yesct commentedif my tablename is grouplist
and my city column name is city,
then do I replace it with grouplist_city
or
grouplist_city_city?
here is what I have so far:
I'm unclear about the mcsid
Comment #5
yesct commentedI ended up with this:
and it seemed to work. I does assume the city and state are never empty...
Comment #6
yesct commentedI'm not sure if I need to test to see if the zip is empty...
I think this works just as well. note, I'm trying to test out a bunch of different ways to do future batches... so thus the 4 or 3 or 2 or 1 for the content sets.
this is related to #459236: Location Integration
and those tagged location importing http://drupal.org/project/issues/search/migrate_extras?issue_tags=locati...
Comment #7
stella commentedPatch at #459236: Location Integration comment #36 may fix this.
Comment #8
mikeryanMigrate and Migrate Extras V1 are no longer supported. Location support for V2 is now consolidated to the following issue:
#943178: Implementation of Location support for Migrate Extras V2