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.
