Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen

My website won't load properly in FF but will in IE - tried solutions - didn't work

  • 2 Antworten
  • 4 haben dieses Problem
  • 1 Aufruf
  • Letzte Antwort von sugerray50

more options

I have 2 websites (1 cloned from the other) that both worked well in FF - until about a month ago. www.drydiapersplus.ca (landing page now loading properly in FF - but loads properly in IE) and www.drydiapersplus.com (loads properly)

When I try & open the .ca site - the left panel, top panel and right panel open up correctly - and the top text...but none of the images load up in the bottom 1/2 of the screen in the middle.

I've tried clearing cache, I've tried CNTRL F5 (hard refresh) - and none of it works.

This is the .ca site that DOES NOT load correctly in FF (but does in IE)

<a href="http://s43.photobucket.com/albums/e361/sugerray50/?action=view&current=casite.png" target="_blank">.ca site, .ca site not loading correctly in FF</a>


This is the US site that does load correctly in FF <a href="http://s43.photobucket.com/albums/e361/sugerray50/?action=view&current=USsite.png" target="_blank">.com site, .com site DOES load correctly</a>

edited by a moderator to fix the first two hyperlinks - Ed

I have 2 websites (1 cloned from the other) that both worked well in FF - until about a month ago. www.drydiapersplus.ca (landing page now loading properly in FF - but loads properly in IE) and www.drydiapersplus.com (loads properly) When I try & open the .ca site - the left panel, top panel and right panel open up correctly - and the top text...but none of the images load up in the bottom 1/2 of the screen in the middle. I've tried clearing cache, I've tried CNTRL F5 (hard refresh) - and none of it works. '''This is the .ca site that DOES NOT load correctly in FF (but does in IE)''' <a href="http://s43.photobucket.com/albums/e361/sugerray50/?action=view&amp;current=casite.png" target="_blank"><img src="http://i43.photobucket.com/albums/e361/sugerray50/casite.png" border="0" alt=".ca site, .ca site not loading correctly in FF"></a> This is the US site that does load correctly in FF <a href="http://s43.photobucket.com/albums/e361/sugerray50/?action=view&amp;current=USsite.png" target="_blank"><img src="http://i43.photobucket.com/albums/e361/sugerray50/USsite.png" border="0" alt=".com site, .com site DOES load correctly"></a> ''edited by a moderator to fix the first two hyperlinks - Ed''

Geändert am von the-edmeister

Ausgewählte Lösung

Currently, the .ca page looks fine, probably because you have a static image there rather than a Flash animation.

On the .ca, were you using the full path in the EMBED tag? On the .com site, that path uses the secure HTTPS protocol. You might be running into a problem with mixing secure content from one domain into the other domain. Try either getting them on the same domain or using the same protocol used in the page.

Diese Antwort im Kontext lesen 👍 1

Alle Antworten (2)

more options

Ausgewählte Lösung

Currently, the .ca page looks fine, probably because you have a static image there rather than a Flash animation.

On the .ca, were you using the full path in the EMBED tag? On the .com site, that path uses the secure HTTPS protocol. You might be running into a problem with mixing secure content from one domain into the other domain. Try either getting them on the same domain or using the same protocol used in the page.

more options

Turns out, after much going back and forth (and having them read your response) - that there was an issue with the security certificate and how the images were all 'secure' images..... so - the host reinstalled the security certificate - or whatever it was they did (I'd complained about this a month ago to my web developer - and was told it was my computer - but when a customer started having the same issues - they looked into it more - and found out it was a security certificate issue).

Thank you for your help - because it was your information that got my web developer to get on the host and get it fixed. :-)

Geändert am von sugerray50