You're welcome! I'm glad it helped.

No. This is not the reason. The Juicebox Plugin for Lightroom will work find on subscription versions of Lightroom Classic CC.

What version of Lightroom do you have? Do you have Lightroom CC or Lightroom Classic CC (and what version number)? (You can check by going to 'Help -> About Lightroom...' from the drop-down menu at the top of the program.

You'll need Adobe Lightroom 4, 5 or 6 or Lightroom Classic CC 7 or higher.
Lightroom CC (not Classic) 7 and higher does not support plugins or web engines.

If you have a compatible version of Lightroom but still experience difficulties, then please let me know what operating system you have (Mac vs PC) and how far into the installation process you get (and what, if any, error messages you encounter along the way).
Thank you.

I've sent you a new download link for your Juicebox-Pro (Single Site License) purchase (to the email address in your post above).
If you ever need a new download link in the future, just fill in the online Download Link Request Form and we'll send you a new one.

You'll find the Juicebox-Pro Plugin For Lightroom inside the Juicebox-Pro zip file in this location: juicebox_pro_1.5.1/adobe-lightroom-plugin/juicebox_pro.lrwebengine

Instructions for installing the plugin can be found on the plugin's own support page here.
First of all, extract the Juicebox-Pro zip file to your hard drive and then...
Mac: Double-click the juicebox_pro.lrwebengine package.
Windows: Drag-and-drop the juicebox_pro.lrwebengine folder onto your Lightroom desktop icon.

If this fails, then you can install the plugin manually by copying the juicebox_pro.lrwebengine folder/package to your Lightroom 'Web Galleries' folder.
Mac: Users/username/Library/Application Support/Adobe/Lightroom/Web Galleries/
Windows: C:\Users\username\AppData\Roaming\Adobe\Lightroom\Web Galleries\

I hope this helps.
If you get stuck with anything, please let me know and I'll try to help further.
Thank you.

Note regarding Lightroom CC vs Lightroom Classic CC:
In late 2017, Adobe split what was then known simply as Lightroom CC into two separate products.
Lightroom CC became Lightroom Classic CC and Adobe released a new version of Lightroom under the name Lightroom CC.
Unfortunately, the new Lightroom CC does not accept third-party plugins or web engines so it is not possible to use the Juicebox-Pro Plugin for Lightroom with this version.
You would need to have Lightroom Classic CC in order to use the Juicebox-Pro Lightroom Plugin (or any other plugin).

Audio will work fine in an embedded gallery so the problem is , as you suspect, most likely a path problem.
The value for the audioUrlMp3 configuration option can be a relative path (relative to the web page containing the gallery's embedding code) or an absolute path (starting with either http:// or https://).

In a WordPress environment where web pages are created dynamically, it can be difficult to know the location of the web page containing the gallery's embedding code (and it will depend on the permalink structure you set in WordPress's dashboard) so it might be easier to just use an absolute path for your audioUrlMp3 , e.g.:

audioUrlMp3="http://www.example.com/audio/track_0001.mp3"

I hope this helps.
However, if you continue to experience difficulties, then please post back with a link to your gallery's web page so that I can see (or hear) the problem for myself and hopefully help further.
Thank you.

The 'juicebox.ttf' and 'juicebox.woff' font files are generated by the IcoMoon App and contain glyphs used as gallery icons (such as those on the Button Bar).
You can check out the contents of these font files using the online FontDrop service.

Juicebox does not use its own custom font for gallery text. The 'juicebox' font is used only for gallery icons.
Juicebox sets the font for gallery text in the 'theme.css' file (on lines 61 and 1179) to:

font-family: "Helvetica Neue", Helvetica, Arial, sans-serif;

Roboto is very similar to Helvetica so maybe this helps to explain things.

For reference, more information on the use of custom icons can be found in the Using Custom Icons support section in the Theming Guide.

Please note that the line numbers above refer to the current version of Juicebox-Pro (v1.5.1).

It has certainly been a long time since the last version was released.
I'd like to see a new version sooner rather than later myself.
All I can say at this stage is that Juicebox is still alive and that work has started on the next version (although progress is slow and I do not know when it will be released).

Looking at the code from your other post (which is different to the code you posted here), it seems that your 'quebeccity' folder may be a complete gallery folder.
If this is the case, then you can point towards this gallery folder (without the need to rename or move any gallery files) by using a baseUrl configuration option in your gallery's embedding code.

<script>
    new juicebox({
        baseUrl: "photogallery/quebeccity/",
        containerId: "juicebox-container",
        galleryWidth: "100%",
        galleryHeight: "100%",
        backgroundColor: "rgba(34,34,34,1)"
    });
</script>

When using a baseUrl, Juicebox looks for a file named 'config.xml' inside the baseUrl folder.

For reference, short descriptions for both configUrl and baseUrl can be found in the Embed Options section of the Config Options page.

If there is no configUrl (pointing towards a configuration file) or baseUrl (pointing towards a gallery folder) in your gallery's embedding code, then Juicebox looks for a file named 'config.xml' in the same directory as the web page containing the embedding code.
If your gallery's configuration file is not named 'config.xml' or is not in the same directory as the web page containing the embedding code, then you'll see the "Config file not found." message.

You can either:
(1) Rename and/or move your gallery's configuration file so that it has the default name ('config.xml') and is in the default location (alongside the gallery's web page).
... or:
(2) Use a configUrl in your gallery's embedding code to point towards your gallery's configuration file, e.g.:

<script>
    new juicebox({
        configUrl: "path/to/my_own_configuration_file.xml",
        containerId: "juicebox-container",
        galleryWidth: "100%",
        galleryHeight: "100%",
        backgroundColor: "rgba(34,34,34,1)"
    });
</script>

Please note that if your gallery's configuration file is not in the default location, then you might need to adjust the imageURL and thumbURL paths within the file.

Another reason why you might be seeing the "Config file not found." message is if the file itself is somehow corrupt and the browser cannot read it.
Open the 'config.xml' file directly in a browser (drag and drop the file into a browser window or enter the address to the file into the browser's address bar) and you should see the XML code.
If there is a problem with the file (such as a control character in an image's caption which is breaking the XML syntax), then the browser should note the problem and the line in the file at which the problem occurs.
You should then be able to open the 'config.xml' file in a plain text editor and fix the problem.

I hope this points you in the right direction.
However, if you continue to experience difficulties, then please email me back with a link to your gallery so that I can see the problem for myself and hopefully help further.
Thank you.

No, sorry. Thanks for checking in but I'm afraid I have no news at the moment.
I really don't know when the next version will be released (or if the rotation bug will be addressed for the next version).
All I can say with any certainty is that the bug has been officially logged and the developers are aware of it.
Sorry I don't have any better news just now.

The most likely cause of unresponsive "New Gallery..." and "Open Gallery..." buttons is a persistent '.tempGallery' folder.

JuiceboxBuilder-Pro creates a temporary folder (named '.tempGallery') whilst a gallery is being created or edited. This folder is automatically deleted on closing JuiceboxBuilder-Pro.

However, if JuiceboxBuilder-Pro is unable to delete the '.tempGallery' folder on closing the application, then the "New Gallery..." and "Open Gallery..." buttons may become unresponsive the next time the program is used.

The most likely cause of a persistent '.tempGallery' folder is the use of an online synced file-sharing folder so we do not recommend saving a gallery to (or opening a gallery from) a folder being synced to an online file-sharing service such as Dropbox or Google Drive.

On a Windows system, the '.tempGallery' folder is located here:

C:\Users\Username\Documents\JuiceboxBuilder-Pro\.tempGallery

With JuiceboxBuilder-Pro closed, please check to see if your own system has a '.tempGallery' folder in this location and, if so, manually delete it before re-opening JuiceboxBuidler-Pro.

Also, try completely disabling any third-party security software that you might have installed (e.g. Avast or AVG), including real-time protection and ransomware detection in case this may somehow be interfering with JuiceboxBuilder-Pro's functionality.
(Please do so at your own risk and be sure to disconnect from the internet first.)

Finally, I know that you say that you have already tried reinstalling JuiceboxBuilder-Pro but it might help to try the complete uninstall/reinstall procedure from this forum thread (Suggestion #11).

I hope this helps.

Thank you for the additional information.
There was a bug in older versions of Juicebox-Pro (fixed in Juicebox-Pro v1.4.0) whereby links in image titles and captions were not clickable).
It's just a hunch but this could be connected to the scrolling issue. It seems that image titles and caption might actually require a link in them for the caption area to be scrollable.
Whatever Juicebox-Pro does behind the scenes when a link is detected within an image title or caption might also need to be done to allow the caption area to become scrollable and the easiest way to achieve this for an image title or caption which does not already contain a link is simply to add one (e.g. a blank one such as <a href="#"></a>).
Adding an empty HTML <a> tag to an image title or caption is certainly something worth trying.
You'll still need to use the following CSS as well, though:

.jb-caption {
    overflow: auto !important;
}

For a vertically-scrolling caption area, try adding the following CSS to the end of your gallery's 'jbcore/classic/theme.css' file (or to the <head> section of your gallery's web page within <style> ... </style> tags).

.jb-caption {
    overflow: auto !important;
}

Otherwise, you could use the Juicebox-Pro API (specifically the getImageInfo() method) to fetch the currently-displayed image's title and caption and then use JavaScript to display the text elsewhere on your gallery's web page (outside the gallery).
Here's a basic example which displays the image title and caption in a container below the gallery.
To see the example in action, create a sample gallery in JuiceboxBuilder-Pro and use the following code as the gallery's 'index.html' file.

<!DOCTYPE html>
<html lang="en">
    <head>
        <meta charset="utf-8" />
        <meta name="viewport" id="jb-viewport" content="width=device-width, initial-scale=1.0, minimum-scale=1.0, maximum-scale=1.0, user-scalable=0" />
        <style type="text/css">
            body {
                margin: 0px;
            }
        </style>
        <script type="text/javascript" src="jbcore/juicebox.js"></script>
        <script type="text/javascript">
            var jb = new juicebox({
                containerId: "juicebox-container",
                galleryHeight: "400",
                galleryWidth: "600"
            });
            jb.onImageChange = function(e) {
                var index = e.id;
                var info = jb.getImageInfo(index);
                var title = info.title;
                var caption = info.caption;
                $('#text').html('<p>' + title + '</p><p>' + caption + '</p>');
            };
        </script>
        <title>Test</title>
    </head>
    <body>
        <div id="juicebox-container"></div>
        <div id="text"></div>
    </body>
</html>

I hope these suggestions help and point you in the right direction.