Active
Project:
Location Feeds
Version:
7.x-1.0-alpha1
Component:
User interface
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Anonymous (not verified)
Created:
28 Feb 2011 at 17:25 UTC
Updated:
28 Nov 2017 at 12:57 UTC
Jump to comment: Most recent
Comments
Comment #1
elliotttf commentedLocation CCK does not function yet. It's partially checked in on the dev branch but still has issues.
Normal node locations should be working though (and in fact I just fixed the simpletests which confirm they do work). In order for the mappers to show up though the content type that you are importing needs to have locations enabled (not through CCK).
If that doesn't work, can you list the versions of location and feeds that you are using so I can make sure there's not a new compatibility issue somewhere? Thanks.
Comment #2
elliotttf commentedLocation CCK is now functional in the 7.x branch.
Comment #3
summit commentedSubscribing, isn't CCK depreciated in D7? May be I am not getting it yet, just started with D7..
greetings, Mattijn
Comment #4
elliotttf commentedCCK still exists in D7 but only to support modules like location CCK, the base functionality of CCK is now included in core.
Comment #5
summit commentedI think with new way of thinking (fields) there is no need for Location CCK, right?
greetings, Martijn
Comment #6
fehin commentedDid anyone figure this out? My location field is not visible on the mapping list either.
Also according to location module page, location cck will be the only option available in the future.
From location homepage:
Comment #7
mastoll commentedI am using the Location module s.t. the location field prints a fieldset w/ separate cells for address, city, state, zip, etc..
Location was not mappable on the target side.
I installed Location Feeds, now I have oodles of location parameters on the target side, one for each of the fields in the fieldset.
On the source side, there are two location parameters i.e. Location and Location:ALTREP.
According to
http://code.google.com/p/calagator/wiki/IcalLocation, the Location parameter is the event venue in unstructured text. The Location:ALTREP is the URI of the event venue.There is not a place for either of those among the target Location fields.
I've managed to at least create nodes without errors by having the source Location parameter target the Location:title (a text field). But the location text doesn't always show up.
So, with with Location Feeds module, we at least have target fields . . . .