Closed (outdated)
Project:
Location
Version:
6.x-3.3
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
5 Sep 2013 at 09:06 UTC
Updated:
20 Jul 2016 at 11:52 UTC
Jump to comment: Most recent
I have several sites using the location module with geocoding enabled to populate the lat long based on the address fields entered. These include Drupal 6 and 7 sites with varying versions of the module.
Geocoding from Google for the UK seems to have stopped working on all of them recently.
Has anyone else had this problem?
Comments
Comment #1
Wouter Van den Bosch commentedSame issues with 2 sites that haven't had their code changed in a while.
As of today (might be yesterday) geocoding (in Belgium) returns a latitude of 180, resulting in a database error upon saving the values.
Nothing was changes on these sites in the past weeks.
I updated my API keys just to be sure, but to no avail.
Comment #2
crystaldawn commentedIt appears that the patches in the D6 version never made it to the D7 branch or they were removed for whatever reason. The following can still be found in the google.inc file:
This is the WRONG url to be using as defined here:
https://developers.google.com/maps/documentation/geocoding/?hl=fr
This is a major bug making the geocoding capabilities completely useless. It's like a car without wheels. The engine is on, but you're not going to be going anywhere anytime soon lol. Thus, the URL and the parameters need to be updated as soon as possible.
UPDATE: I just checked the latest stable and dev release manually, and this appears to be fixed. I dont know why but when I used drush to do the DL, it was not getting a version with these fixes. I had to DL these manually without using drush. Thats a headscratcher, what would cause that?
Comment #3
crystaldawn commentedAppears to be fixed, could be a possible drush issue though. IDK.
Comment #4
iancawthorne commentedI've re opened this with some more specific details I've just discovered today as this does not appear to be fixed in my case.
With the latest Drupal 6 release (3.3), if a "State" (or County as I'm in the UK) is specified, Geo coding is lost. Removing the value in the State field and the geo coding works fine.
I'm not sure why this would be the case when a) the chosen state is correct and b) In the geo coding options, I've set to zip code accuracy, so the state would be ignored in this scenario?
Comment #5
legolasboClosing old D6 issues as D6 is end of life