Hello there, we're expecting the same error at one of our customers pages.
We generates a key for the domain www.buz-ag.ch (which you'll find in the source code of the page): http://www.buz-ag.ch/metanavigation/kontakt.html The hack with the v=3.6 parameter doesn't work anymore for us. Has anyody heard something new about this? I think it might be a problem of the api console that doesn't update Googles cache fast enough (if they acutally have a cache for this). Thank you for your help! Greetings Tizian Schmidlin On Monday, June 4, 2012 2:51:31 PM UTC+2, Danny Pryor wrote: > > Here you go: http://fitnessforumgainesville.com/contact/directions-V3.php. > > > Realistically, I was only making a comment. I know the code is correct > because it's copied and pasted directly from Google, substituting only my > key in the code. However, if there is something that I'm missing, I'd sure > like to know it. > > Danny Pryor > Vice-President > Rodan Media Group > > www.rodanmedia.net > d...@rodanmedia.net > > PO Box 30136 > Fort Lauderdale, FL > 33303 > > T | 954-561-0600 > F | 954-333-6345 > > On Jun 4, 2012, at 6:30 AM, Andrew Leach wrote: > > > On 2 June 2012 05:24, Danny Pryor <d...@rodanmedia.net> wrote: > >> This issue seems to persist. We have a site we put together for a > client in > >> Georgia, and we also use the same code for a domain in Florida. The > Florida > >> test domain is working just fine, but the exact same code on the > Georgia > >> site does not, even though both domains are authorized, e.g.: > >> *.example.com/* and *.example2.com/*. What I suspect with the Georgia > site, > >> fitnessforumgainesville.com, is that we just threw the switch on a new > DNS, > >> and the domain is presently repropagating around the web. However, I > won't > >> know that for certain unless someone shoots down that theory (I'm not > >> certain that issue would even affect Google's read in anyway, as the > correct > >> code is loaded on both servers) or until I know the propagation is > >> absolutely concluded. > >> > >> Either way, this issue is one that I was able to duplicate on the > Florida > >> domain, then rectify later by reverting the code. Nothing I have been > able > >> to do fixes the problem on the Georgia domain, so I'm at a loss. If any > new > >> ideas have materialized since the last posts, prior to mine, I'd be > quite > >> grateful to hear some ideas. > > > > One idea is to give real urls which demonstrate the problem. There's > > nothing above which anyone can use to help -- what's particularly > > frustrating is having rooted around on the one real domain you quote, > > I find that you've removed the map code entirely. > > > > -- > > You received this message because you are subscribed to the Google > Groups "Google Maps JavaScript API v3" group. > > To post to this group, send email to > google-maps-js-api-v3@googlegroups.com. > > To unsubscribe from this group, send email to > google-maps-js-api-v3+unsubscr...@googlegroups.com. > > For more options, visit this group at > http://groups.google.com/group/google-maps-js-api-v3?hl=en. > > > > -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-maps-js-api-v3/-/7UaO33DcS9QJ. To post to this group, send email to google-maps-js-api-v3@googlegroups.com. To unsubscribe from this group, send email to google-maps-js-api-v3+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
