Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Upgrading to the beta5 patch has disappeared all location fields (even lat/long and the category) as mapping targets for my feeds.
I'd give more information, but now I'm encountering a separate problem after updating views to 2.3:
Fatal error: Class 'views_plugin' not found in //../sites/all/modules/feedapi_mapper/mappers/views/plugins/views_plugin_access.inc on line 9
Comment | File | Size | Author |
---|---|---|---|
#13 | 416052_feedapi_mapper_location.patch | 1.52 KB | geodaniel |
#11 | feedapi_mapper_location_fields.patch | 1.22 KB | geodaniel |
#10 | Picture 1.png | 60.29 KB | aterchin |
#1 | feed-item-example.JPG | 204.6 KB | Summit |
Comments
Comment #1
Summit CreditAttribution: Summit commentedFor me upgrading to Beta 5 or Beta7 loses also the location_fields to map to.
I do not see Locations in my available mapperlist anymore. I have location in my to be mapped contenttype. It worked in beta3.
While my feed item example give Lat/lon information. See attached picture for my feed-item example. Why is location mapper not available anymore please?
Thanks for going into this!
Greetings,
Martijn
Comment #2
Summit CreditAttribution: Summit commentedHi,
Installing feedapi_mapper.module,v 1.1.2.7.2.9 2008/12/02 got my location mapping back, so my settings must be ok.
But feedapi_mapper.module,v 1.1.2.7.2.23 2009/03/30 12:31:49 (the latest doesn't show my location mapper).
Investigation back, from Beta5 the location information is lost! While this is a security issue, I am not able to map to location anymore..Hopefully this is helpful for solving this issue.
greetings,
Martijn
Comment #3
Summit CreditAttribution: Summit commentedHi,
Any progress in location feedmapper unvisable issue please?
I now have a security issue when I enable feedapi_element mapper?
If you want more info from me, please ask.
Thanks for going into this!
Greetings,Martijn
Comment #4
alex_b CreditAttribution: alex_b commentedAs of beta 9 location mappers need to declare mapping targets themselves. These are the changes in question: http://cvs.drupal.org/viewvc.py/drupal/contributions/modules/feedapi_map...
Looks like these changes only allow mappings to CCK fields of type location, while previous versions of feedapi mapper were more liberal.
Comment #5
Summit CreditAttribution: Summit commentedHi,
Could these changes be reflected in the location_mapper, while I do not use cck-location, but location itself: http://drupal.org/node/265196#comment-1073099?
Thanks a lot in advance for considering this!
Greetings,
Martijn
Comment #6
Summit CreditAttribution: Summit commentedHi Alex,
Do you mean to say that from now on we need to use cck-location instead of location to have geo-mapping from feeds?
Thanks a lot in advance for your reply!
greetings, Martijn
Comment #7
SocialNicheGuru CreditAttribution: SocialNicheGuru commentedi had to switch back from cck location to locaiton module because cck location did not show up in views and there are myriad problems with it in views.
is there a way to have feedapi mapping work for both cck location and regular location fields?
Chris
Comment #8
alex_b CreditAttribution: alex_b commentedPlain location fields (non-CCK fields) are NOT supported ATM. Patches more than welcome here.
Comment #9
Summit CreditAttribution: Summit commentedHi, I finally got location mapper back through CCK, but now only longitude and latitude are supported, no country, province, city supported yet?
greetings, Martijn
Comment #10
aterchin CreditAttribution: aterchin commented...sorry if I missed something in this or one of the other issues, but is there any patch yet that works to include all the location CCK fields? using beta-9 and getting the same issue, with only lat and long supported, see attached.
Thanks, subscribing.
adam
Comment #11
geodaniel CreditAttribution: geodaniel commentedThe attached patch seems to work for me to transfer location fields when nodes are initially created, but it is losing the data on update. Not sure if that's the case with CCK address data too?
Comment #12
geodaniel CreditAttribution: geodaniel commentedThe problem on update is that the revision id (vid) in location_instance table is getting reset to 0 instead of the actual revision, but I've noticed this is only an issue when revisions aren't enabled for that node type you're saving to. If revisions are enabled, then all works fine and locations get updated instead of wiped out.
There is a remaining issue with the province field not being saved, but that should probably move to another issue, like with the country name.
Comment #13
geodaniel CreditAttribution: geodaniel commentedSorry, that patch didn't work if there were other fields on the node, but this one should.
Comment #14
alex_b CreditAttribution: alex_b commentedgeodaniel: I've started tor require tests for new mappers. This is a measure to protect ourselves from regression problems that keep appearing in a scenario where many modules are being integrated.
I know that this is an update to an existing mapper, but is there any chance to get tests for geo mapper with this patch?
Comment #15
jcamfield CreditAttribution: jcamfield commentedIs there any plan or hope to restore mapping to non-CCK Location module fields? Perhaps it should be removed from the project description if not?
Comment #16
stevestaso CreditAttribution: stevestaso commentedI'm very close to getting this to work.
I'm using 6.x.1.0
I'd like to use the native location fields (non-CCK)
I can map most of my csv elements to my target node fields.
But the native location fields are not getting populated.
I tried the patch in #13, but still not working.
If I add a CCK location field to the target node, I get
warning: Invalid argument supplied for foreach() PHP warning
When the save occurs. (Updates does not produce any errors).
But still, the location fields do not get populated.
So I'm having trouble with either type of location field.
Is the SimplePie parser needed for this?
Guidance on troubleshooting, please?
Comment #17
Summit CreditAttribution: Summit commentedHi, I think http://drupal.org/node/559744#comment-2045510 is more than related, may be duplication.
Would love to have a solution for location and cck_location related to rss-feed category fields.
greetings, Martijn
Comment #18
kirkcaraway CreditAttribution: kirkcaraway commentedI am having the same problem. I can't switch to CCK location, so I would need a solution that uses Location module. It seems from this thread that it worked at one time. Hopefully it will again. Thanks.
Comment #19
SocialNicheGuru CreditAttribution: SocialNicheGuru commentedHas this been resolved for regular location and cck location?
Thanks.