Hi all.  I am not a web developer but was able to build my company's 
website by referencing great resources like the community here at google 
groups.  I went "live" this afternoon and an now up against a critical 
issue with the google map api v3 on the live site.  I feel there should be 
a simple explanation but I cannot find any relevant information so I'm 
inclined to ask a new question.

I created a new development subdomain (www2) and google maps had been 
working fine. This afternoon, I went "live" by changing the A record for 
the www subdomain to point to the same IP as the www2 subdomain.  I have 
left the www2 subdomain active for now. 

Now that the DNS change has propagated, my new site is available at 
www.sonahomes.com.  However, all the map divs are blank and i get js errors 
that things like LatLng, maptype, etc are "not a constructor".  However, I 
can accessing the *same pages* through www2. everything works fine!

Example
Working: http://www2.sonahomes.com/virginia/
Broken: http://www.sonahomes.com/virginia/

I am using the same API key as I was in development.

I thought I had everything covered by:
 -updating all URL references in the code from www2. to www. 
 -configuring the google API console "allowed referrers" to: " 
*.sonahomes.com/* "

I'd appreciate any help figuring out what I'm missing!  In the meantime now 
that the site is live, should I setup a temporary 301 redirect to point 
www.sonahomes.com/virginia to www2.sonahomes...? 

Thanks for any direction on this issue

-- 
You received this message because you are subscribed to the Google Groups 
"Google Maps JavaScript API v3" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-maps-js-api-v3+unsubscr...@googlegroups.com.
To post to this group, send email to google-maps-js-api-v3@googlegroups.com.
Visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to