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.

Thanks!!

Regards Andrea.

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

Please check module plg_jchoptimize. Because the requested URL was not found.

joomfreak

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.

Please re-try to access it at: www.elementotango.it/evento

Thank-you!

Regards Andrea.

Can you please send me the super admin access via private message system?

joomfreak

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:

Insecure URL: fonts.googleapis.com/css?family=Montserrat:400,700
Found in: www.elementotango.it/evento/

Insecure URL: fonts.googleapis.com/css?family=Russo+One
Found in: www.elementotango.it/evento/

Insecure URL: fonts.gstatic.com/s/montserrat/v7/zhcz-_...SvpkopQaUR-2r7iU.ttf
Found in: fonts.googleapis.com/css?family=Montserrat:400,700

Insecure URL: fonts.gstatic.com/s/montserrat/v7/IQHow_...6RMS0v1dtXsGir4g.ttf
Found in: fonts.googleapis.com/css?family=Montserrat:400,700

Insecure URL: fonts.gstatic.com/s/russoone/v5/RO6e96EC...f_cDxXwCLxiixG1c.ttf
Found in: fonts.googleapis.com/css?family=Russo+One

And this last one which I don't understand neither:

Insecure <form> call.
Found on line # 6 in file: www.elementotango.it/evento/index.html

Insecure <form> call.
Found on line # 11 in file: www.elementotango.it/evento/index.html

(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 ?

Any ideas of the <form> warning ?

Thanks again!!

Regards AG