Program-loop?

Program-Loop?

Yesterday I inserted a zhgooglemap call with a wrong map-number. When i opended the page, I got a white space instead the map, and in the center of the map a turning "wheel". No change after correction of zhgooglemap call.

Problem: I can not stop that wheel:
- after closing / opening Firefox, the wheel is still shown, on all pages containig zhgooglemap calls on that web-site.
- after shut-down of client yesterday and restart today, that wheel is still shown, on all pages containig zhgooglemap calls on that web-site.

But maps are shown as expeced on that "problem" web-site
- using Firefox a different client machine
- using EDGE on "Problem" client machine

Firefox is my favorite browser. What can I do?

Hi.
Check browser console for errors.

Sorry, did not look at web console, i am not a developper..

Console info leeds to "mixed content", so realised that HTTPS is used (just tried to see if it works).
But now, whenever I try to use HTTP, Firefox automatically changes to HTTPS.

I still try to find a way to make it use HTTP again.

EDGE on this machine, and Firefox on other client still accept and use HTTP, so Googlemaps work fine on those envoroments.

Found no way to disable that redirecting from HTTP to HTTPS. All those hints I found with Google during the last two hours did not work for me....

But: selecting protocol HTTPS in Zh GoogleMap Manager Options solved my problem.

Regards
Ulrich

Hi Ulrich
I didn't understand you right.
When you open your page - and get constant loading image - it means error in map page definition.
Protocol (http / https) can't cause stop showing this image.
Do you have empty page with map and loading image?

As for Protocol option:
- if your site forced change to https (by site config settings) - you can get warning for mixed content. In this case you have to change protocol to https
In future I'll add setting to automatic detection protocol

The problem was caused by "Murphy's law": Two things happened at the same time:
- I changed site call from HTTP to HTTPS without careful testing everything (did not test Google maps on my pages)
- had a typing error on zhgooglemap number
Together this caused that loop, and I forgot to look a browser console....

Automatic detection protocol could certainly help those un-careful users to avoid problems of mixed content.

So sorry again for disturbing with a problem caused by myself