I guess I have a similar problem. My map was working until friday (12/19/2008) evening. After reading your post I went back to 2.138f and it´s working again.
http://www.gobr.net/geoxml.htm - the one with problem http://www.gobr.net/geoxml138f.htm - after going back to v. 2.138f Leo On 19 dez, 20:40, Philip <[email protected]> wrote: > I have an app that has been running pretty reliably for several > months, and suddenly with the advent of 2.139e, it starts to get > javascript errors. Debugging gmap code is nearly impossible due to the > compaction. What is worse is that the bug is not consistent. > > http://pskreporter.info/pskmap139e.htmlhttp://pskreporter.info/pskmap138f.html > > If you use the first link, then sometimes the map does not display, > and you get > > Error: 'undefined' is null or not an object in function(a,b){var > c=this,d=c.sx[b],e=z(d.x+a.lng()*c.ux[b]),f=Qd(Math.sin(se(a.lat > ())),-0.9999,0.9999),g=z(d.y+0.5*Math.log((1+f)/(1-f))*-c.vx > [b]);return new K(e,g)} > > (if you are using IE). When I tried to debug it in IE, it appeared to > be as a result of an addOverlay call when I was adding a GMarker which > did have a valid latlng as far as I could tell. > > I actually have all the javascript errors logged to my server, and the > effect is quite dramatic: > > version: error count > 131f: 24 > 132e: 195 > 136d: 53 > 137c: 181 > 138f: 24 > 139e: 1210 > > Note that 139e has only been out for about 3 days. 138f was out for > about 8 days. 132e was almost a month. > > I have reverted to 138f for the time being. > > Philip --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
