No, nothing out of the ordinary. I've just checked and the actual store locator - www.udoschoice.co.uk/locator.html - is working fine. As is another locator located on the same server. Would these not be stopped too if the key was blacklisted? Well, at least the Udo's Choice one?
Regarding the key, I've just checked the newly generated key against the old one - it's a bit shorter : New: ABQIAAAAaMGhEnXdoeSxOcmuCqdq5hRsSfS1Tsow3GMSltnjato1kvvJ1RSNpThJiupwsIcvFn_zpwDqWGEScQ Old: AABQIAAAAaMGhEnXdoeSxOcmuCqdq5hT6LZ7kIYZaKoX50xVAx8p5LpkADBTXBtCfwoJBvVhvKgyPBxDgRmDiVw could this be the issue?? Terry - just had a look, it's "key" on mine, so that should be ok? Cheers Tony On Oct 16, 2:38 pm, Terry <[email protected]> wrote: > I just added to another post, but thought the input could apply here > too. I had Key=xyz in my url. I hadn't changed any code in this in > weeks, but I made it key=xyz and confirmed it now works. Someone is > playing around with those scripts and not ignoring case it seems. > > On Oct 16, 8:51 am, "[email protected]" <[email protected]> > wrote: > > > I've tried adding in "&sensor=true" to the end of the googlemaps query > > (not sure where else to put it) - but that still doesn't work. > > > It throws up this error: > > ********************************************** > > Warning: simplexml_load_file(http://maps.google.com/maps/geo? > > output=xml&key=ABQIAAAAaMGhEnXdoeSxOcmuCqdq5hRsSfS1Tsow3GMSltnjato1kvvJ1RSN > > pThJiupwsIcvFn_zpwDqWGEScQ&sensor=false&q=25+Kingland > > +Crescent%2C+%2C+Poole%2C+Dorset%2C+BH15+1TA) [function.simplexml-load- > > file]: failed to open stream: HTTP request failed! HTTP/1.0 403 > > Forbidden in /home/udoschoi/public_html/geocode.php on line 38 > > ********************************************** > > > If you copy/paste the URL out of there > > -http://maps.google.com/maps/geo?output=xml&key=ABQIAAAAaMGhEnXdoeSxOc... > > - and open it up, the XML seems to be fine and locatable..? > > > I've asked our hosts to check that the simplexml_load_file() function > > is working ok, and they said it was, but reset things to make sure. > > > Tony > > > On Oct 16, 1:01 pm, Mike Williams <[email protected]> wrote: > > > > You can also now also get a 610 error if your &sensor parameter is > > > incorrect. There isn't a separate "bad sensor parameter" error code for > > > the HTTP service. > > > > -- > > > Mike Williamshttp://econym.org.uk/gmap --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-maps-api?hl=en -~----------~----~----~----~------~----~------~--~---
