For the most part, this is not actually coded into your album pages. The link to a slide image, for example, might be just slides/mydog.jpg. If you visit the site with regular http, all the links to folders and images automatically use http. And indeed, your site works just fine in Chrome. The browser doesn't force the use of a secure connection - https. If your copy of Chrome is doing that, it's an internal setting in the browser, or perhaps an extension that's doing it.
But converting your site to a secure connection is probably a good idea - http is on the way out, and https may be required in the future.
The first step is getting your web hosting set up to support https. This is something that has to be done on the server - you can't just "decide" to change. So, contact your web host and ask what you have to do to enable a secure connection. If your web host starts telling you about purchasing a certificate and installing it, start looking for another web host. Most web hosts now offer this for free, and it's often a simple matter of "turning it on" on your hosting account.
Once https has been enabled on your site, there are only a couple of things you need to do in jAlbum. Don't make these changes until your site is responding properly when accessed with https. Your project has http hard-coded in two places, and those should be changed. It's in Tiger > Sections > Custom content and Tiger > Footer > Custom content.
The other change will be in the jAlbum uploading settings. You will want to change the connection method. Tools > Upload/Manage, and switch to SFTP - your web host can tell you what port you should be using. Then connect to your web host, navigate to the directory where your domain is (probably something like public_html), and mark that as the web root (the little folder icon with a globe on it). That will tell jAlbum that it should use https whenever it's trying to figure out things like links for social media.
|