Page 2 of 2
Re: Website problems
Posted: Mon Aug 26, 2019 3:11 pm
by phonojim
Not found on my android tablet either.
Jim
Re: Website problems
Posted: Mon Aug 26, 2019 3:15 pm
by melvind
I just tested the site using https instead of http. That makes it work. Your website provider and easily fix this by forcing all addresses to use https.
Re: Website problems
Posted: Mon Aug 26, 2019 7:00 pm
by Raphael
Thanks to all who responded. I submitted the URL for this thread to my website host. So far, they claim to be stumped.
I seem to have “solved” the problem myself by establishing a mobile website. So, for now at least, there will no longer be a blank screen showing on iPhones and iPads.
Cheers,
Raphael
Re: Website problems
Posted: Mon Aug 26, 2019 7:31 pm
by rgordon939
Works fine now.
Rich Gordon
Re: Website problems
Posted: Wed Aug 28, 2019 2:28 pm
by Raphael
Unbelievably, neither FatCow or Weebly have been able to resolve the problem for me. I sent all of the above suggestions to them and all they do is say they are hard at work on the issue. It's been one whole week since the trouble began.
I've tried to simplify everything so that when a mobile user gets shifted to my mobile site, there is no content except there is a button right there to switch over to the desktop site.
Thanks again to all who chimed in,
Raphael
Re: Website problems
Posted: Wed Aug 28, 2019 6:12 pm
by Bleachbit
It’s the Chinese.
If you haven’t noticed your “Click here to email us”
Click here to email us
请点击这里给我们发送电子邮件
Meanwhile, have your service-provider change your URL (Uniform Resource Locator) to mimic a secure-socket-layer https://
e.g.
https://www.musicaltreasuresofmiami.com/index.html
rather than a non-secure reference
e.g.
http://www.musicaltreasuresofmiami.com/index.html
The result will be a correct rendering of your pages on both desktop and mobile devices.
Until they can determine the real issue.
Re: Website problems
Posted: Wed Aug 28, 2019 6:35 pm
by Raphael
The Chinese email link has been there for several years without any issues, so I cannot see how that caused the recent problem. But I will forward your suggestions to FatCow. If nothing else, it provokes a response and keeps the issue alive.
thanks,
Raphael