TOPIC:

I administer the websites for three clubs - 1976054, 3692031 and 3746834

This morning I was updating meeting hours for one of the clubs in the Information / Directions tab and noticed that the map location shows the club has moved to Antarctica. I tried updating the embedding link (as per the instructions) without success.

Since two of the clubs share the same location I thought of copying the data from the other club website, only to discover that it had also moved to Antarctica. Both maps were OK last week and nothing was changed.

Just for fun I checked the third club and see it's also moved. I think this would imply that our entire city has relocated to Antarctica, which may explain why it's been colder than usual lately.

All three look ok to me.

Go to the bottom of the screen and click on the reload website link. See if that makes any difference

Already tried that, but I did it again anyway. No difference - we're still cold.

What browser and version are you using?

Good call Brian. I'm using Google Chrome, Version 39.0.2171.71 m

but after your question I tried it in Safari and got correct results.

Any idea on how we might fix this? Other users also have Chrome. I also don't recall doing an update in the last week but it's a little weird that Google maps don't work properly within the Google browser.

The Programmer will have to look at it.

We just take what you enter for the maps and send it to Google to make the map that we show.

Are you entering an address to get the map or are you entering the iframe code?

If you are entering an address, you should copy/paste to the Google maps website to make sure it still works for them.

Also, if you are getting the iframe code, you may want to re-fetch that from Google. They may have changed their iframe code.

I am seeing your map on one of your sites (I only looked at one) showing Kunming. I'm using Chrome as my browser.

Thanks everyone. I tried both chrome and ie on my main desktop. Both failed. Safari on the iPad worked ok so I tried a second system with chrome and it worked fine.
Both systems are running Win 7 ultimate 64 bit with the same version of chrome.

Please post what you entered for each map.

This is what's entered for clubs 1976054 and 3746834

<iframe src="www.google.com/maps/embed?pb=!1m18!1m12!...2sca!4v1417471780033" width="600" height="450" frameborder="0" style="border:0">

for club 3692031

<iframe src="www.google.com/maps/embed?pb=!1m14!1m8!1...2sca!4v1416905966484" width="600" height="450" frameborder="0" style="border:0">

remember that the maps work ok if I'm on another computer, but my main system fails with both chrome and IE.

allandpage wrote:

This is what's entered for clubs 1976054 and 3746834

<iframe src="www.google.com/maps/embed?pb=!1m18!1m12!...2sca!4v1417471780033" width="600" height="450" frameborder="0" style="border:0">

for club 3692031

<iframe src="www.google.com/maps/embed?pb=!1m14!1m8!1...2sca!4v1416905966484" width="600" height="450" frameborder="0" style="border:0">

remember that the maps work ok if I'm on another computer, but my main system fails with both chrome and IE.

I looked into this. The only suggestions that I can offer are to replace the iframe code with "fresh" iframe code or try to reinstall your Chrome browser. (I would try the former first.) Keep in mind that there are number of parameters and options embedded in the iframe code. It is possible that Google changed those and the resulting error is having an effect in Chrome but not other browsers. (If there was an error with the iframe code, which browser would most likely have an effect... think about it.)

I'm surprised I didn't think of another solution much sooner. When I sat back and tried to reason why the map would display on other systems, but not on this one (on any browser), I tried to figure out what was unique about this one computer.

At long last I tried something I have not done for far too long - that is clear all the browsing history, cookies and temporary internet files. With that task completed I tried the maps again - and THEY WORKED. It looks like it was a machine specific problem rather than any problem with FreeToastHost.

In any event, I appreciate your assistance as always. Keep up the good work.