On Apr 1, 1:10 pm, stefancaunter <[email protected]> wrote: > I moved a map to a live site last week and it worked. Error began > today. Switching to v=2 fixes it, but I don't recall this in the > documentation for versioning; iirc it said that 2.x would simply get > you the latest features without coding in 2.95 (or whatever is > latest).
http://code.google.com/apis/maps/documentation/index.html#API_Updates Says what it always has: You may instead obtain the latest release (including the latest features) by passing v=2.x instead. However, be aware that the latest release may not be as reliable as the v=2 release. We update the Google Maps API often (sometimes every week), at which point features within the v=2.x release are migrated into the v=2 release unless problems are discovered. Which certainly understates the issue... Do not use v=2.x in production sites unless you monitor them closely and can deal with issues like the current one. -- Larry > > Stefan Caunterhttp://mapguy.ca/ > > On Apr 1, 3:28 pm, stani <[email protected]> wrote: > > > Same problem here > > > On Apr 1, 6:24 pm, Billy <[email protected]> wrote: > > > > I have been using the Maps API for several weeks with no problem but > > > today I started getting the following error on multiple sites that I > > > have using the API. > > > > window.jstiming.Timer is null or not an object --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
