Closed (outdated)
Project:
Geocoder
Version:
7.x-1.3
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
14 Oct 2012 at 20:26 UTC
Updated:
6 Mar 2018 at 12:31 UTC
Jump to comment: Most recent
Comments
Comment #1
benlagrone commentedI'm using the multistep module on the same form. maybe it's a problem?
-nope, I removed the multistep fields and it's still broken
Comment #2
benlagrone commentedSo I added a new content type with the same fields...
and it started working again?
the new node type and the old both started geocoding.
Comment #3
phayes commentedComment #4
agill commentedI noticed the same behavior.
Comment #5
simon georges commentedCould have it been a bug on the geocoding service's side? Did you try with several geocoding services?
Comment #6
simon georges commentedNo answer in a year. Please reopen if you still have the issue.
Comment #7
bluesman2014 commentedNot sure if this is exactly the same issue but it sounds similar:
I have a geofield on the user account which geocodes the user's address. When creating a new user with a new address, this works fine and the user's location can be seen at /map/user.
But when editing the user's address, the geocoding is deleted from the database. No update takes place, it simply removes the data.
Comment #8
bluesman2014 commentedJust updated to 7.x-1.3 but the issue persists
Comment #9
pookmish commentedI had a similar issue using feeds to import into an addressfield which is then geocoded into a geofield field. I had a total of nearly 1,000 rows with valid address data. After import, only about 600 of them were geocoded correctly. I solved it by clearing the cache_goecoder table after every node save. Maybe that will help you as well with a hook.
I understand the concept behind the cache, but perhaps it needs some work to improve its functionality.
Comment #10
pol