Cannot get any location other than the default?

Given how old this is, please confirm you are still experiencing this bug and I will look into it. Thanks.

Gonna presume this is no longer an issue.

I'm having the same problem. No matter what I change the longitude/latitude reset to the default values. I'm on Drupal 5.15.

Hmm... well, better open this again then.

Got the same problem. Used to work.

Dave

I figured out where it is breaking but not why. The code looks good.

In gmaplocation.module, line 173, we have:
$page = @file_get_contents( $url, false, $context );

If I change it to this, it will work:
$page = @file_get_contents( $url, false );

I can't find anything wrong the the $context variable. May be someone else can.

Dave

This might be an issue with Google resolving the address. The module will revert the lat & lon if it doesn't get anything back from Google.

I ended up in the ocean several times before getting Google find the address.

Try entering a comma separated address: XXX Street, City, State, Zip.

I wonder if this is the same bug as #496796: Validate point to the wrong function. I am not running Drupal 5. Is anyone able to check—it was a simple fix.

JaredAM is right—I've now confirmed this is to do with gmaplocation just sticking with the current coordinates (which will initially be the default ones) if it does not get a useful answer back from Google. Comma-separated addresses are good, but also try dropping out suburb and state information as this worked for me in one situation.

This will be fixed in due course. And since it applies to 6.x as well, I'm marking it against that version, although I'll try to backport any fixes.

Moving this up to current -dev. This one will be backported when fixed.

Added warning message when geocoding fails:
6.x-2.x: http://drupal.org/cvs?commit=238906
6.x-1.x: http://drupal.org/cvs?commit=238946
5.x-1.x: http://drupal.org/cvs?commit=238910

When geocoding fails, default coordinates are used even if there were other coordinates. This issue will remain open as a feature request until I modify that behaviour so it sticks with previous coordinates instead.

In 2.x when geocoding fails, previous coordinates are now maintained rather than being replaced by the defaults. Where coordinates have not previously been set the (new) default coordinates are inserted. Updated message presented to user to explain what has happened. http://drupal.org/cvs?commit=240480

Backported improvements to 5.x-1.x: http://drupal.org/cvs?commit=243008

Backported to 6.x-1.x: http://drupal.org/cvs?commit=243640
Released in both 6.x-1.1 and 5.x-1.1.