Wasn't it Thor who wrote: > >Compare the JS returned when the wrong key is used on a site with that >when the right key is used. The server side check will have added the >new alert and set G_INCOMPAT to true, but it gets added just *after* >the client side check. So if the client side check fails you will see >the existing message. Right now it's only when the client side check >succeeds and server side check fails that you see the new message, and >it's the cases where this should not have happened that we're working >to track down and address.
That's now the case. It wasn't the case earlier when I made my last check, but possibly I had an old version of the loader code in my cache from when I used that wrong key last night. With this latest version, when I use a bad key, after I get the "The Google Maps API key used on this web site was registered for a different web site." message, the map gets rendered. That wasn't the case earlier. Three hours ago, if the wrong key was used, the main.js API code didn't get loaded and the bad page failed with "GMaps2 is not defined". -- http://econym.org.uk/gmap The Blackpool Community Church Javascript Team --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
