VISIT AND LIKE OUR PAGE ON FACEBOOK
TAKE A LOOK AT OUR TWEETS ON TWITTER
SUBSCRIBE TO THE JOOMFREAK RSS FEED
VISIT OUR CHANNEL ON YOUTUBE

Account Details

Change your name, email, password or permanently delete your account. Change settings

We offer several ways you can get support from our experts: Support ForumKnowledgebaseNewsletter

Your Forum Posts

No posts to display.


joomfreak-logo

It's time to pass this project on to someone passionate about continuing its journey. joomfreak offers a unique opportunity to build upon a well-established platform and keep providing the Joomla community with quality templates and tools.

If you're interested, we'd love to hear from you!
[email protected]

Welcome, Guest
Username Password: Remember me

main header not showing with SSL enabled
(1 viewing) (1) Guest
  • Page:
  • 1
  • 2

TOPIC: main header not showing with SSL enabled

Re: main header not showing with SSL enabled 27 May 2016 02:51 #8889

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 ?

You can edit template file templates/jf_event-up/index.php, module jfslideshow modules/mod_jfslideshow/helper.php.

joomfreak
The following user(s) said Thank You: [email protected]

  • Posts:2940
  • isupport
  • Moderator
  • OFFLINE
  • Karma: 0

Re: main header not showing with SSL enabled 27 May 2016 09:32 #8895

Hey folks, thanks to your suggestions, I have solved it.

In the template's index.php there were 2 calls made using http:// and in the helper file you indicated there are 26 calls. I replaced all of these using theur https:// equivalents, which solved it, and Chrome now is not complaining about the site anymore.

One interesting aspect: I have read somewhere that it could be possible to execute these calls with the resource called like this:

//resourcename.domain.com

instead of using http:// or https://

they claim that using //resource would then be converted into http or https, depending on the protocol being used, so not causing any errors, in any case.

I haven't tried this myself to be honest. I went straight to the https:// replacement, but I wanted to ring this bell in case you guys want to make some tests and then decide upon.

Again thanks for the help, issue solved !!

Regards AG
  • Page:
  • 1
  • 2
Time to create page: 0.55 seconds
Saturday 09 November 2024

joomfreak is not affiliated with or endorsed by the Joomla Project or Open Source Matters.
The Joomla logo is used under a limited license granted by Open Source Matters the trademark holder in the United States and other countries.