Robert, We have over 100 separate sites that have been operating for several years on different unrelated servers. All of which run the same component. On March 25, all of them simultaneously the outlines (polygons) and markers all disappeared and on all sites they all received the same error in chrome console. Nothing has been changed to those sites. So there is no doubt in our mind that it is because of Google's change on that day.
The question is how to resolve it. Also as noted in my post we are using API 2. The exact number was noted in our post. Also as noted the maps do show, its only the outlines and the markers that stopped working. So if the service was disabled nothing would show so whether they are on or off doesnt seem to relate to our issue. Also once again we have changed nothing so unless Google changed a setting for us without our conscent that would make no sense. Finally, when we originally created all the sites years ago there was no option for enabling or disabling the service as there is now. Hopefully someone with knowledge on what changed on the 25th can help resolve this issue. Thank you. On Tuesday, April 3, 2012 4:46:25 PM UTC-4, Robert Fletcher wrote: > > did you go to the services console and activate the google maps api v3, v2 > are enabled? > > I don't know if march 25 changes have any effect on your maps working or > not, thought i would throw this out there. > > > On Monday, April 2, 2012 11:39:59 AM UTC-4, heavymark wrote: >> >> We have over a 100 sites using a CMS that uses a Google Map Extension for >> the past several years. >> >> It has worked well since then by as of March 25th, though the Maps show, >> the markers and polygons no longer show on any of our sites. >> >> To note, the extension uses the API 2 (2.150) each with a unique long API >> key. >> >> The extension is no longer in active development so we are trying to see >> what Google changed that broke compatibility. While we realize API 2 is >> depreciated Google has mentioned we still have over a year of time where it >> should still work, during which time our CMSs will be updated to a version >> hopefully that will support the API 3 extensions. >> >> If there is anyone at Google we can email privately who might be of >> assistance that would be greatly appreciated. >> >> To note, we tried generating a new API Console key, but those do not >> appear to be accepted by the extension as valid even when we change the API >> version to 2.377. >> >> >> On Tuesday, January 24, 2012 9:56:15 PM UTC-5, Chris Broadfoot (Google >> Employee) wrote: >>> >>> Hi all, >>> >>> We're planning to update v=2.s on 25 March. >>> >>> There are two major changes: >>> - API Console keys will be supported, including Geocoding and Directions. >>> See here to obtain a key: https://code.google.com/apis/console/ >>> - All invalid keys will be rejected. >>> >>> Another reminder that the V2 Maps API is deprecated, and its deprecation >>> period is coming to a close. Please upgrade your maps to the V3 API. >>> >>> Get started with V3 today: >>> http://code.google.com/apis/maps/documentation/javascript/ >>> >>> Cheers >>> CHris >>> >>> -- >>> G+: http://chrisbroadfoot.id.au/+ >>> Twitter: http://twitter.com/broady >>> >>> -- You received this message because you are subscribed to the Google Groups "Google Maps API V2" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-maps-api/-/sEL804KK27YJ. 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.
