Update: The map appears because there is no GBrowserIsCompatible check on that page. That might seem like weird behavior, but that was the situation before this recent change, so we're sticking with it (http:// imagine-it.org/google/wrongkey.htm).
- pamela On May 8, 7:37 am, Andrew Leach <[email protected]> wrote: > On May 8, 7:49 am, pamela fox <[email protected]> wrote: > > > > > There was 1 fixed bug in v2.157. The resolution of that bug means that > > we now alert more granular messages when a script tag has been > > specified incorrectly - such as informing the developer that sensor > > has been mis-specified or that an incorrect client ID has been > > specified for a domain (for Enterprise customers). > > I can't test the Enterprise change. > > The sensor parameter seems to work although the hl= parameter is > ignored.http://www.xpeastbourne.org/test/wrongsensor.htmgets the > message in English, not Russian. > > The key parameter message does use hl. The English version still says > "This could be because the API key used on this web site was > registered for a different web site." but plagiarising a key is not > going to be the most common cause of the error. A better message would > be something like "This website needs a different key" which covers > all eventualities. > > The key message says "You can generate a new key for this web site at > %1$s" instead of providing a URL.http://www.xpeastbourne.org/test/wrongkey.htm > > What is rather surprising is that an API map is actually produced > after these error messages! > > Andrew --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
