It looks like the key validation failure code is broken.

The API key is currently checked twice, once by the server (which is 
also responsible for deciding which error message to display for a 
failure) and once by the API Javascript code.

In this case the server considers your API key to be valid, and sets up 
no error message, but when the key is re-checked by the API Javascript 
it fails, and this code gets executed:

  if (!GValidateKey("30b0664c64f2b03d5be1d9dfd194f6f05bd81034"))
    {G_INCOMPAT = true;alert("");return;}

The blank alert is displayed. GBrowserIsCompatible() is set to return 
false. But the API code is not disabled, and the map still gets 
displayed.


There was a big change to GValidateKey in APIv2.156, so I suggest that 
you try using &v=2.155 or earlier. [It's also a good idea to add 
&sensor=false, but that doesn't affect this situation, that parameter is 
only checked on the server.]

Please keep your demonstrator page available, so that Google can take a 
look at the problem. Other people have previously reported similar blank 
alerts, but have been reluctant to provide links.

I'll raise it as an Issue.

Let us know if using 2.155 works.

-- 
Mike Williams
http://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
-~----------~----~----~----~------~----~------~--~---

Reply via email to