Ok I found the solution myself and I want to share with you because I think it's a common issue. The hint was Pamela posta about the new build being released. I found out that if you have v=2 in the parameters calling the GMAP API, every time a new build is released you load the new build (and the new bugs) as current API. I tryed to change it to 2.s (stable release) but maybe it was too far behind with functions, so I tryed putting a specific release and after some testing, 2.147 was enough to let everything work as usual, so there must be some bug in 2.150 wich developer are still not aware of. If you need help to find it I will create for you a page with my script and the currente 2.150 build for you (developers) to test and find out the bug for future releases, just let me know. In the meanwhile I'm happy with 2.147 :)
So for people who has those issues now and then, to be more clear, change the version to a stable or previous release in this string: <script src="http://maps.google.com/maps? file=api&v=2.147&key=xxxxxx" type="text/javascript"></script> Best wishes --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
