This topic has 7 replies, 3 voices, and was last updated 9 years, 11 months ago ago by Eva Kemp
Hello!
I had some problems in the past with other themes, that had some ”mixed content” issues on the frontend, and by mixed content I mean the warning from Internet Explorer and Firefox caused by content on the page that was both http and https.
Another theme only after the authors removed the http hard-coded content from it, they managed to make it fully compatible with https / mixed content error free.
Is this the case also for Royal – is it fully https compatible? I’m asking because when I’m in the theme’s panel, the https bar in Google Chrome isn’t green anymore, so it’s clear that you still have some http elements inside the theme. The same goes for the demo content for the footer – if the elements are not disabled, I get a mixed content warning also on the frontend.
Thank you in advance for the answer and sorry if I was more elaborate than needed. I can provide you with admin credentials if needed, the website is installed in a fully https environment (unique IP & Comode SSL cert installed).
Hello,
please provide us with admin and FTP access in private content and we will double check if there are any http left. In addition you need to disable demo footer before launching site and create your own footer if needed.
Regards,
Stan Russell
Sure, look in the private content for an admin user, however I don’t have much content now, don’t know if it matters.
But yeah, please double-check, I’d hate it if the visitors would be “welcomed” by a browser warning for mixed content.
Thanks again 🙂
Any updates? I shouldn’t worry, right?
Thanks 🙂
Hello,
I’ve checked your site and there is no warning in Firefox and Chrome browsers. The certificate is verified.
Are you experiencing any issues with it?
Thank you.
Regards,
Eva Kemp.
Ok, thank you for your answer. I just wanted to be sure.
Ticket is closed for now, I’ll reopen it only if there will appear other problems when the site will be live.
Hello,
You’re welcome.
Regards,
Eva Kemp.
The issue related to '‘Quick question – is Royal fully https compatible?’' has been successfully resolved, and the topic is now closed for further responses