One possibility is that it's a cache issue. Because you're calling the API loader with an identical request, with even the key the same, then your browser is perfectly entitled to return the old version of the code from its cache.
That didn't matter in the past, because the key validation was performed in the main client side code, using the current value of window.location.host, and would succeed when rerun against the correct site. Recently, server side key validation has been introduced. If the server side validation fails, then the loader code that gets returned will display the error. A *fresh* call on the correct site will pass the key validation test, but if you run the old copy of the code from your browser cache, then it will still fail, because the failure message is burned into the cached code. Quick fix: When this occurs on one of your PCs, use Ctrl-Shift-Refresh to force a fresh fetch of the loader code. (Or use a browser that has less aggressive caching, like Firefox). If that works, but you're not satisfied with using that as a workround, then I suggest you raise it as an issue. Google could easily modify their Cache-Control settings in such a way that the loader code doesn't get cached. -- 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 -~----------~----~----~----~------~----~------~--~---
