main header not showing with SSL enabled
24 May 2016 08:55 #8868
Hello there,
yesterday after getting the SSL certificate installed, I tried to switch the site to the https protocol. What I have seen, is that the main header would not show up anymore if I switched to https.
I have therefore reverted back it all to http (not secure) but I wanted to check with you to start with, if the template supports the https protocol, or if there are changes to be applied, so I know where to start from.
Re: main header not showing with SSL enabled
24 May 2016 16:07 #8869
Hey folks
I made some progresses with this and now I can see the header (i changed some jquery calls in JQueryEasy component, from http to https to fix it). But there is still a problem: the web browser reports that the site has some unsecure items, that it blocks. So, the main menu fonts and the fonts used in the main header, are different between the https and http versions. You see the live site in https here www.elementotango.it/evento
So, looks like the issue is with the fonts - but what ?
Thanks!!
regards Andrea
Last Edit: 25 May 2016 08:00 by andreagatti1[email protected]. Reason: corrected the URL which was mis-spelled
Re: main header not showing with SSL enabled
25 May 2016 07:59 #8872
Hi folks not sure what you mean.
JCHOptimize is a plugin used to compress JS, CSS and HTML. I have tried to disable or enable it, and nothing changes. Not sure this has to do with the issue.
What I believe is that there are some http calls instead of https ones somewhere, but I can't figure it out.
Re: main header not showing with SSL enabled
26 May 2016 11:17 #8885
Hey folks, thank-you. Unfortunately I can't right now, since this is the live system that is getting reservations live right now, I don't have it installed in a test environment like I used before
However, by using a resource at www.whynopadlock.com I received the following information on the causes of the broken https:
(Note: Chrome will show a security error for any secure page with an insecure <form> call on the page)
Would you be able to tell in what of the template components or modules/plugins are those google APIs calls done and font calls done, so I can try and convert them to their https equivalent ?