On 10/07/2009, Richard Davies <[email protected]> wrote:
>
>  Whoa! Hold on there Google! What about Issue 1243?
>  http://code.google.com/p/gmaps-api-issues/issues/detail?id=1243
>
>  You've just broken my web site and there's no known work around! This
>  is seriously uncool! The bug report was filed prior to your "migration
>  announcement", and it has been accepted... yet somehow this issue was
>  ignored when you decided to force users to upgrade.
>
>  This forced migration needs to be reversed immediately until this bug
>  is resolved because there is no work around. Please don't force people
>  to upgrade until you've fixed all of the regression bugs in the newer
>  version!!!!!!!!

What work arounds have you tried? I had a similar problem once, and
solved it by moving the map related functions to the frame with the
map.

(But equally you might be able to fix it by loading a dummy gmap in
the child frame (so that it loads teh required external modules))

Cant see a map on www.portlandmaps.com that uses iframes other than the demo




>
>  On Jul 9, 9:20 pm, "pamela (Google Employee)" <[email protected]>
>  wrote:
>
> > Hi developers-
>  >
>  > As originally posted here and on the forum several months ago, we
>  > have
>  > upgraded version 2.s to version 2.140, and all sites that are
>  > manually
>  > requesting versions less than 2.140 in the script tag will be given
>  > 2.140 instead.
>  >
>  > If you're suddenly experiencing an error now with your site, then
>  > it's
>  > probable that there is some bug or change in behavior in 2.140 that
>  > affects your code. Please first try upgrading to v=2 and seeing if
>  > that fixes your error. If not, look through the issue tracker for it,
>  > and if it is not there, please report it.
>  >
>  > There are 2 known issues that could affect you:
>  > * Issue 1412: Animated GIF as GMarker: null symbols in IE7
>  >  http://code.google.com/p/gmaps-api-issues/issues/detail?id=1412
>  >  To work around this, some code change is needed on developer's part
>  > * Issue 1126:   Bug: GLayer isn't clickable, gives JS error
>  >  http://code.google.com/p/gmaps-api-issues/issues/detail?id=1126
>  >  If you experience this, just change your map to use v=2, or anything
>  >
>  > >= 2.149
>  >
>
> > See the earlier post about this upgrade for more 
> > information:http://groups.google.com/group/google-maps-api-notify/browse_thread/t...
>
> >
>  > Thanks; we hope that we have provided sufficient notice for this
>  > upgrade and that it goes smoothly for you.
>  >
>  > - pamela
>  >
>


-- 
Barry

- www.nearby.org.uk - www.geograph.org.uk -

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to