Really appreciate it Barry, and it looks like Google fixed it
yesterday and now it's working properly. Thanks!

On Dec 10, 5:00 am, Barry Hunter <[email protected]> wrote:
> Reported as a bug 
> here:http://code.google.com/p/gmaps-api-issues/issues/detail?id=3772
> and acknowledged by Google.
>
> Just use an old key to load the main api directly, still available 
> herehttp://code.google.com/apis/maps/signup.html
> It will then of course fall though and be used for geocoding.
>
>
>
>
>
>
>
> On Fri, Dec 9, 2011 at 11:59 PM, Andrew <[email protected]> wrote:
> > I have an old V2 maps application which I am trying to put a new API
> > Console key in place of the old anonymous key. I don't have any
> > referral domain rules in place on the key I'm trying to use, but all
> > geocoding commands are returning a 610 error.
>
> > <script src="http://maps.google.com/maps?file=api&v=2&key=<?
> > php echo $APIKEY?>&sensor=false&amp;hl=<?=$language;?>"></script>
>
> > This is pretty much a copy and paste from the hello world example, and
> > it works just fine with the old key, just not the new API Console key.
> > I saw on another post that the geocoding service is not part of the
> > API Console, does that mean I have to serve up a different key for
> > loading in the JS and somehow another key to do the geocoding?
>
> > Any help would be greatly appreciated
>
> > --
> > You received this message because you are subscribed to the Google Groups 
> > "Google Maps API V2" 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 
> > athttp://groups.google.com/group/google-maps-api?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Google Maps API V2" 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.

Reply via email to