Take a look at the short Adding a Logo support section for ideas as to how you could incorporate a logo into your Juicebox gallery.

If you use Suggestion #3 from the link above, then you can also make the logo into a link by using a Gallery Title such as:

<a href="http://www.example.com/index.html"><img src="mylogo.png"/></a>

As an alternative to using the Gallery Title, you could use the Back Button.
Set and backButtonUseIcon="FALSE" and the backButtonText will be used. instead of the 'home' icon. You can then set the backButtonText to be something like the HTML code above. (Also, be sure to set backButtonPosition to something other than NONE so that the Back Button appears in the gallery.)

For reference, a list of all Back Button options can be found here.
More information on using HTML formatting within the Gallery Title and Back Button can be found in this FAQ:
How do I add HTML formatting to the Gallery Title or Back Button?

I hope this helps.

@mustard

Technically, there really is no limit to the number of galleries that you can have on a single web page. (There is no hard-coded limit built into Juicebox.)

This sounds like a coding problem (maybe a duplicated baseUrl or configUrl).
Please post back with the URL to your web page so that I can see the problem for myself and hopefully help further.

Incidentally, when embedding multiple galleries, the 'juicebox.js' file should be loaded just once (i.e. once per web page rather than once per gallery). If you currently load the 'juicebox.js' file once per gallery, then leave the first instance and remove al others.

Thank you for the update. I'm glad you've been able to resolve your Lite/Pro problem.

You have two opening <script> tags one after another: one on line 97 and the other (after a few blank lines) on line 103.
After the initial opening <script> tag, the browser is expecting some JavaScript code but, instead, it encounters the '<' character of the next opening script> tag which is where the error is coming from.
Just remove one of these opening <script> tags and all should be well.

If you'd like to check your web page for any other HTML errors, you can feed your web page's URL to the W3C Markup Validation Service (and then fix any errors reported).

That's a strange solution, for sure, but I'm glad that it worked for you. Thank you for letting me know.

Incidentally, I just reinstalled Windows 10 myself last week (a clean install) and did not have to adjust my system clock to install JuiceboxBuilder-Pro so I'm really not sure what the cause of the problem is.
In any case, I'm glad you've got it working.

You're welcome!
I hope you get on OK with your other galleries.
I'll mark this thread as [SOLVED] but if you run into any further problems, just create a new thread and I'll do my best to help you out.

Yes, your gallery at http://davebreen.com/jhbsocber20.html now displays correctly. If you do not see your gallery at this address, then please completely clear your browser's cache before reloading your gallery's web page to ensure that your browser is fetching the current files from your web server (and not using older, cached versions from your computer's hard drive).
(The gallery is working so if you do not see it, the issue if most likely a browser caching issue.)

PHP is a server-side scripting language. Some web pages may contain PHP code. The PHP code is processed on your web server before the web page is delivered to the user's browser. This allows for a dynamic (rather than just a static) website.
If any of your web pages use PHP, then you'll need to have PHP installed on your web server.
For example, WordPress is a PHP web application which requires PHP. It will not work without PHP.
Juicebox-Pro requires PHP for two functions, namely the Download Button and Password Protection. PHP 5.2 or later is required for these functions but, if you do not use them, then your Juicebox gallery will run quite happily without PHP being available.

When you visit any URL which does not exist on your web server, your web server defaults to displaying the "WordPress Coming Soon" page as your site's error 404 (file not found) page. You can change this error 404 page if you like but you'll need to find out where it is being set on your web server. (Your web host should be able to help you out with this.)

WordPress is a PHP web application which allows users to create a website or blog online in a web browser interface.
You do not need WordPress installed in order to have Juicebox galleries on your website.
However, if you do use WordPress, then there is a dedicated Juicebox plugin for WordPress (WP-Juicebox) which allows you to create and embed galleries into WordPress pages and posts from within the WordPress interface (without having to build your galleries on your computer with JuiceboxBuilder).
If you do not want to use WordPress for your website, then there is absolutely no need for it in order to have Juicebox galleries.

If you installed WordPress through your online hosting account's control panel, then there may be a way to uninstall it through the control panel, too. I'd investigate this first (ask your web host, they'll know) before you start manually deleting any files.

From what I've seen of your website and the changes you've made, I do not see any evidence of server-side caching but if you make any changes and don't see them immediately, then it's just something to bear in mind which might be causing the problem.

As I mentioned above, your http://davebreen.com/jhbsocber20.html gallery is now displaying and functioning fine and if you don't see it yourself, then please try clearing your browser's cache before reloading your gallery's web page.

I hope my notes above help to clarify a few things.
If you are having trouble with any other galleries, just post links to them and I'll try to help further.

As far as I can recall, the minimum Adobe AIR requirement for JuiceboxBuilder is AIR v2.0 or later so you should hopefully be able to download the last version of AIR for Linux (v2.6) from the Adobe AIR archive web page and install JuiceboxBuilder under this version of AIR.
Here's a direct link to Adobe AIR v2.6 for Linux (from the link above).
I hope this helps.

It looks like the folder name on your server is still 'JHBsocBer20'.
If you are changing all path references to lowercase, then you'll need to change this folder name to 'jhbsocber20', too
Everything else looks to be in place and I don't think you should be having any issues specifically because of Blue Host.
Hopefully, once you rename your gallery folder to lowercase, your gallery should display as expected.

Thank you for the links to your galleries.

I see that you are using a custom PHP file (named 'config.php')  to dynamically generate your gallery's XML data.
The problem lies somewhere within this file (which is not part of the Juicebox package).
There is something within this file that is not compatible with PHP 7.2 onwards.

Unfortunately, I do not have access to your 'config.php' file to inspect its code but opening it directly in a browser reveals the following warning:

Your use of the PHP count() function (whatever it may be) on line 10 is listed in the 'Backward incompatible changes' on the 'Migrating from PHP 7.1.x to PHP 7.2.x' support page here.

In order for your 'config.php' file to be compatible with PHP 7.2 onwards, you'll need to find a new PHP method to count whatever it is that you are counting.

I hope this points you in the right direction.
If you continue to experience difficulties, then please zip and upload your 'config.php' file somewhere (and provide a download link) so that I can inspect the code and hopefully help further.
Thank you.

Yes. Please see the following link for details: Using an External jbcore Folder

Essentially, you can upload a single instance of the 'jbcore' folder to anywhere you like on your web server and then load the 'juicebox.js' file from within this folder at the start of each gallery's embedding code. (Details are in the link above.)

This has the added advantage of allowing you to upgrade all your galleries at once (when new versions of Juicebox are released) by just replacing a single 'jbcore' folder.

You're welcome!