On Mar 11, 9:09 pm, "Paul.Degnan" <[email protected]> wrote: > Apologies in advance if I'm only contributing noise here. I openly > acknowledge that I have not drilled down into this to fully ascertain > cause, but I took a 1.5 hour outage tonight related to an update. I'm > assuming that I'll need to make changes to be compliant with the > latest version, but there was something weird regarding the v=2.s > option that I thought worth reporting. I'm getting ahead of myself and > posting about it in case anyone else sees anything similar. > > First user reports of an outage were at 10:15 EDT. (http://www.gmap- > pedometer.com) I confirmed the problem. Maps loaded just fine, > geocoding worked, etc. My site captures double-clicks and determines > distance between the last two points. I assume the problem has > something to do with the event handler on the double click -- all the > actions that were supposed to happen there were not, with no error > messages. > > Anyway, the weird thing is that the problem was *not* resolved by > switching to "v=2.s". I did that, but the problem persisted. It was > only when I pinned my code to "v=2.140" that it started to work again. > > I understand if my site breaks when a new version gets pushed into the > main "v=2" release. But it's my understanding that getting a stable > release with the "v=2.s" option is supposed to get me a version from a > few months back. If that's the case, then I should have seen today's > error back when that version was first released. I would think that > swapping from "v=2" to "v=2.s" is always safe, presuming your code > worked on past versions.
v2.s is currently pretty old (v2.73). Switching to that is only safe if your map doesn't use any feature introduced after that. Yours uses G_PHYSICAL_MAP which was introduced in 2.94... Current (v=2): 2.148 (note, the changelog doesn't reflect this yet) Latest (v=2.x): 2.149 Stable (v=2.s): 2.73 Switching to v2.140 looks like your best bet for now and reporting the issue: http://code.google.com/p/gmaps-api-issues/issues/list (preferably with a demonstrator so pamela can reproduce it) -- Larry > > So that's my $.02. Feel free to contact me for further details. I will > be looking into what happened to the doubleclick handler, and will > post again if I find anything that seems to have an explanation > outside my own crappy code. > > On Mar 9, 3:16 am, pamela fox <[email protected]> wrote: > > > Yesterday, we pushed 2.149 as v2.x. Currently, v2 is still set to > > 2.140, but we plan to set v2 to be 2.148 within the next day. > > > There were no changed issues in 2.149, and various interface changes > > related to the GoogleBar and its ability to serve ads. There will be a > > blog post about those changes this week. > > > The full changelog is available > > here:http://code.google.com/p/gmaps-api-issues/wiki/JavascriptMapsAPIChang... > > (If the groups interface cuts the link off, you can find it in the > > wiki tab of the issue tracker). > > > As always, please discuss anything in the forum > > (http://groups.google.com/group/Google-Maps-API/) that you think may > > be a regression and report it in the issue tracker if others confirm > > your suspicions. > > > - pamela --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
