On Aug 16, 11:58 pm, lupo <[email protected]> wrote: > The problem is not being produced today. The error no longer appears > as long as I use "localhost" as the hostname (which also produced the > error yesterday).
Last I checked, there is no key checking when you specify localhost. If you specify an IP address, you need a valid key for the URL that appears in the browsers window. -- Larry > Previous to the release, when using an IP, I was > warned with a message but the api worked as Fredrik said. Now when an > IP is used the GSize warn arises and the map will not appear. > > Why I am using an IP instead of "localhost" is due to I work remotely > connected to a workstation in a datacenter and I use the ip of that > "remote" machine to test the development. This is much faster than > opening a FFox instance remotely. This way of working is no longer > possible at least by now. > > On 16 ago, 16:02, Fredrik <[email protected]> wrote: > > > > > > > > > I can't really link to a map that illustrates this since all versions > > of Google maps 2 url/key now seem to have been forwarded to 2.340. > > I.e 2.s->2.340 but also 2.193->2.340. > > > Several reports of malfunctioning Google maps were sent to us that > > coincided with the upgrade to 340 the 15:th. I'm also 100% that you > > previously could simply click "ok" on the warning and at least see the > > map tiles (the basic script would load, though I believe the geocoder > > didn't work for example). > > > It's perfectly ok if Google tightens the constraint on invalid keys > > but I don't think it should > > be done without notification. > > > "Something" has been tuned at Google maps recently since I can > > currently confirm different(ok vs error) behavior from different > > access points(region servers). Perhaps this is getting fixed? > > Hopefully just a very intermittent disturbance. Would be interesting > > to get more info though. > > > Regards > > / Fredrik Blomqvist > > > On Aug 16, 3:16 pm, Barry Hunter <[email protected]> wrote: > > > > You might get a better answer if link to your map. > > > > Lots of things change, but in stubtle ways, so you might of stumbled > > > on a edge case. With a link people can actully try your map and see > > > what happens. You then get a range of developers trying your map in > > > different browsers, and situations. They might help you spot the > > > problem. > > > > As far as I know invalid key has always stoped the map working > > > totally. If you where still getting the map, perhaps you have two API > > > loading tags in your code? One ok, one not. > > > > On Tue, Aug 16, 2011 at 10:52 AM, Fredrik <[email protected]> wrote: > > > > Hi, > > > > > According to the changelog v2.s was upgraded form 2.310 to 2.340 > > > > yesterday. > > > > Did something in the handling of map keys, or key warning messages, > > > > change in this upgrade? > > > > We've got some customer indications that keys has stopped working. Or, > > > > did perhaps the warning message about invalid key now stop all map > > > > loading? (previously you would still see a map after clicking "ok"). > > > > > Anyone got more information here? > > > > > Regards > > > > / Fredrik Blomqvist > > > > > -- > > > > 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.
