• Registered: 2015-03-16
  • Posts: 3

Topic: Juicebox logo causing security problems when using HTTPS [SOLVED]

I have a JuiceBox Lite gallery working on a website, when I enable SSL the site is rated as a security risk as it contains unencrypted content.

The Juicebox logo embedded in the Lite gallery, found at this address http://juicebox.net/img/jb001.png is the cause of the problem, as it is pointing to an unencrypted HTTP URL.

How can I correct this issue? I need to amend this URL to point to a HTTPS address, otherwise I cannot secure my site with SSL. I have been unable to find a reference to this URL in any of the JuiceBox library files.

Kind regards,
TED

  • Registered: 2012-04-24
  • Posts: 5,924

Re: Juicebox logo causing security problems when using HTTPS [SOLVED]

The only way to solve this problem is to purchase and use Juicebox-Pro. Juicebox-Pro does not feature the Juicebox branding with the http:// link (which is present in all Juicebox-Lite galleries) and, when using Juicebox-Pro, your https:// site will be fully secure.

  • Registered: 2015-03-16
  • Posts: 3

Re: Juicebox logo causing security problems when using HTTPS [SOLVED]

Hi Steven,

Thanks for the reply! If I purchase JuiceBox Pro, what is involved in upgrading my Lite version to Pro? I wish to minimize any disruption to the production site and don't particularly want to have to re-configure everything again.

  • Registered: 2012-04-24
  • Posts: 5,924

Re: Juicebox logo causing security problems when using HTTPS [SOLVED]

All you need to do to upgrade a Lite gallery to Pro is swap your gallery's existing Lite 'jbcore' (on your web server) with the Pro 'jbcore' folder from the Juicebox-Pro download zip package ('juicebox_pro_1.4.3.2/web/jbcore/').
(Alternatively, you could open the Lite gallery in JuiceboxBuilder-Pro and save it on the 'Publish' tab.)
Full instructions for upgrading can be found here.

  • Registered: 2012-04-24
  • Posts: 5,924

Re: Juicebox logo causing security problems when using HTTPS [SOLVED]

Juicebox-Pro v1.5.0 has just been released and fixes the issue reported in this thread.
Please see this blog entry for details of the new version and the Version History for a full list of changes.
Details on how to get the latest version can be found on the Upgrading Juicebox support page.