It can't hurt to try.

A couple of other things to consider...

(1) Have you ever saved or tried to load a gallery in JuiceboxBuilder-Pro from a folder that is actively being synced with an online file sharing service such as Google Drive or Dropbox? This has been known to cause a persistent .tempGallery folder which JuiceboxBuilder-Pro cannot delete.

(2) Do you have any third-party security software installed (such as an anti-virus program or malware protection) which might somehow be interfering with the functionality of JuiceboxBuilder-Pro? If so, then try temporarily disabling it to see if this helps to resolve the problem.

You can use the Juicebox-Pro JavaScript API to determine the image that is currently being viewed and you can then take action accordingly.
Here's an example which will set a JavaScript variable (and display an alert) the first time that an image in position #10 or above is viewed.

<script src="jbcore/juicebox.js"></script>
<script>

    var jb = new juicebox({
        containerId: 'juicebox-container'
    });

    var flag = false;

    jb.onImageChange = function(e) {
        if (flag === false && e.id >= 10) {
            alert('Image #10 or above has been viewed.');
            flag = true;
        }
    };

</script>
<div id="juicebox-container"></div>

I hope this points you in the right direction.

The only way to have thumbnails and main images on separate pages is to use Small Screen Mode (by setting screenMode="SMALL" in JuiceboxBuilder-Pro's 'Customize -> General' section).

There are a few things to note, though.

(1) Using Small Screen Mode does not guarantee that all thumbnails will be displayed on a single thumbnail page.
The number of thumbnails displayed per page will depend on the size of the thumbnails, the number of images in the gallery and the amount of space available in the browser viewport.
If there is not enough space available to display all the gallery's thumbnails on a single page, then multiple thumbnail pages will be created (dynamically) and the user can navigate between them using the thumbnail paging arrows.

(2) Juicebox-Pro does not use a masonry style layout.
All thumbnails are the same size as each other, defined by the thumbWidth and thumbHeight configuration options.
In JuiceboxBuilder-Pro, these options are set on the 'Images' tab. Click the 'Change Sizes...' button in the 'Image size' control panel to reveal the 'Set Image Sizes' pop-up window where you can change the thumbnail dimensions.

There is no reason why a main image in Small Screen Mode will not be displayed as large as it would in Large Screen Mode.
In Small Screen Mode, the gallery will still occupy the same area on its web page as it would in Large Screen Mode and the main images will still be scaled according to the imageScaleMode value.
In fact, in Small Screen Mode does not support a TOP area and the main image pages display no thumbnails, so there might actually be more space for the images to be displayed in Small Screen Mode that in Large Screen Mode.
Just be aware that if you use the default value for imageScaleMode of SCALE_DOWN, then small images will not be scaled up (as this might decrease their visual quality).
In such a scenario, you could either set imageScaleMode="SCALE" (to scale down large images and scale up small images so that they are all displayed as large as possible within the gallery's image area whilst respecting their aspect ratios and without cropping) or leave imageScaleMode="SCALE_DOWN" and use larger gallery images (so that all images need to be dynamically scaled down slightly to fit within the gallery's image area).

This is probably more difficult than it sounds.
You'd need to use the Juicebox-Pro API and refer to some internal CSS classes.
It is not something that Juicebox-Pro was designed to do but you could try the following which should detect when the last image in the gallery has been reached (via AutoPlay rather than manual navigation) and then wait for a designated amount of time (to allow the image to be viewed) before displaying the thumbnail page.
Please note that you are certainly free to try (and modify) this if you like but as it is not within the design parameters of Juiccebox-Pro, it is not officially supported.

<script type="text/javascript" src="jbcore/juicebox.js"></script>
<script type="text/javascript">
    var jb = new juicebox({
        autoPlayOnLoad: "TRUE",
        containerId: "juicebox-container",
        screenMode: "SMALL",
        showAutoPlayButton: "TRUE",
        showSmallThumbsButton: "TRUE"
    });
    jb.onInitComplete = function() {
        var count = jb.getImageCount();
        jb.onImageChange = function(e) {
            if (e.id === count && $('.jb-bb-btn-auto-play').first().hasClass('jb-status-playing')) {
                window.setTimeout(function() {
                    // Last image in gallery has been reached via AutoPlay and 5000ms have elapsed.
                    $('.jb-bb-btn-de-show-list').trigger('click');
                }, 1000);
            }
        };
        $('.jb-bb-btn-auto-play').click(function() {
            var index = jb.getImageIndex();
            if (index === count && $('.jb-bb-btn-auto-play').first().hasClass('jb-status-playing')) {
                window.setTimeout(function() {
                    // AutoPlay button has been clicked on last image in gallery and 5000ms have elapsed.
                    $('.jb-bb-btn-de-show-list').trigger('click');
                }, 1000);
            }
            
        });
    };
</script>
<div id="juicebox-container"></div>

There is a lot going on in your web page so I cannot be sure that there are no influences outside the code you posted but the problem seems to be either an asynchronous or timing problem of some sort.
However, it might actually be enough to just change the size of the gallery's container without having to explicitly call the Juicebox-Pro API setGallerySize() function.
Try using just the following for your doLayout() function. In might just work fine without the additional code.

function doLayout() {
    setContainerHeight();
}

It's certainly worth a shot before we delve deeper into your web page's code.
I hope it helps.

That is correct. Only the Juicebox skin for jAlbum allows you to create multiple galleries at once

I have just created a test album in jAlbum and the Facebook sharing seems to work fine for me.
However, as I noted previously, due to the fact that the browser never leaves the 'index.html' page (and galleries are switched using JavaScript), there can be only one og:image for the entire album (and you need to add this manually by editing your 'index.html' file manually in a plain text editor).

That's right. The shareUrl configuration option is used only by JuiceboxBuilder-Pro (and not the Juicebox skin for jAlbum). However, adding an og:image to your album's 'index.html' should take less than a minute and, due to the way that the album works, only one og:image can be used anyway so it is not a long time-consuming task.
Even if the Juicebox skin for jAlbum used shareUrl, the entire structure of the skin's output would need to be changed to allow a different og:image for each gallery. Each gallery would need to be displayed on its own separate web page and the visitor would need to go back and forth between the galleries and the navigation tree page (unless the navigation tree was duplicated on every gallery page but, again, this would require a huge restructuring of the skin).

If you find that, even after adding an og:image to your album's 'index.html' page, the designated thumbnail does not show up in the Facebook share window, then try running your album's 'index.html' page URL through Facebook's online tools to refresh Facebook's own cache of the page's Open Graph information.
(1) Facebook's Sharing Debugger: https://developers.facebook.com/tools/debug/sharing/
(2) Facebook's Batch Invalidator: https://developers.facebook.com/tools/d … ing/batch/
(3) Facebook's Open Graph Object Debugger: https://developers.facebook.com/tools/debug/og/object/
(Click the 'Fetch new scrape information' button.)

If you continue to experience difficulties, please post the URL to your album's 'index.html' page so that I can take a look and hopefully help further. Thank you.

Unfortunately, the Download Button does not work on iOS devices so Juicebox-Pro automatically hides the Download Button on iOS devices. (However, the Download Button should still be visible and functional on Android devices.)

The best option for iOS devices would be to include the Open Image Button (by setting showOpenButton="TRUE" in JuiceboxBuilder-Pro's 'Customize -> Lite' section) so that the image can be opened on a page of its own where the site visitor can save the image using the browser's own 'Save Image' functionality.

The Facebook thumbnail functionality should be working fine in the current version of Juicebox-Pro (v1.5.1) as demonstrated in this sample gallery.

It should be noted that it is not possible to have the shared image's thumbnail displayed in the pop-up Facebook share window due to limitations imposed by Facebook on what data can be passed via their share URL. Only one thumbnail image can be used per web page. However, the shared link will still point towards the correct image within your gallery.

Facebook uses the data from Open Graph meta tags to populate the share window.

The thumbnail image displayed in the Facebook share window is determined by the og:image tag.
This specified image is displayed when any image in your gallery is shared.
You can think of the og:image as being representative of the gallery as a whole so you could use an image which best represents your gallery. (The og:image does not need to be an image from the gallery itself.)

When you create a Juicebox-Pro gallery with JuiceboxBuilder-Pro, Open Graph tags are included in the gallery's 'index.html' file (and the first image in the gallery is used as the og:image Facebook thumbnail).
The tags will looks something like this.

<!-- START OPEN GRAPH TAGS-->
<meta property="og:title" content="This is the Gallery Title." />
<meta property="og:type" content="website" />
<meta property="og:url" content="http://www.example.com" />
<meta property="og:image" content="http://www.example.com/images/IMG_0001.jpg" />
<meta property="og:description" content="This is the Gallery Description." />
<!-- END OPEN GRAPH TAGS-->

og:title uses the Gallery Title ('Customize -> Lite').
og:url uses the Share Url ('Customize -> Sharing').
og:image uses the Share Url and appends the relative path to the first image in the gallery.
og:description uses the Gallery Description ('Customize -> General').

If you embed your gallery into a custom web page (and do not use the 'index.html' file generated by JuiceboxBuilder-Pro), then you'll need to manually add an og:image meta tag to your web page. Please make sure that the content is in the form of an absolute URL (such as http://www/example.com/images/image.jpg) and not a relative URL.

If, after adding an og:image meta tag to your web page, you do not see the specified image displayed in the Facebook share window, then you might need to use one or more of the following online tools that Facebook provides.

(1) Facebook's Sharing Debugger: https://developers.facebook.com/tools/debug/sharing/
(2) Facebook's Batch Invalidator: https://developers.facebook.com/tools/d … ing/batch/
(3) Facebook's Open Graph Object Debugger: https://developers.facebook.com/tools/debug/og/object/
(Click the 'Fetch new scrape information' button.)

Running your web page's URL through these online tools should clear Facebook's cache of your web pages and fetch new scrape information from your gallery's web page.

Note for WordPress users
In a WordPress environment, the easiest way to include Open Graph meta tags in all your WordPress web pages is to use a third-party plugin such as the WP Facebook Open Graph protocol plugin.
Once activated, go to 'Settings -> Facebook OGP' (from the WordPress Dashboard), enter your 'Facebook User Account ID' and the URL of the image you want to use as the og:image in the 'Default Image URL to use' text field and select the 'Force Fallback Image as Default' checkbox (to ensure that this image is always used).
This is just a suggestion rather than a recommendation. Other plugins are available. Try a WordPress plugin search for terms such as "Facebook Open Graph meta".

I hope this helps.
However, if you continue to experience difficulties, please try to explain your problem in greater detail (I cannot be sure exactly what the problem is that you have encountered) and I'll hopefully be able to help further.
Thank you.

Thanks for buying Juicebox-Pro! I'm sure you'll get on well with it.
If you encounter any difficulties, just post a new topic in the Juicebox-Pro forum and I'll do my best to help you out.

@smohring

Thank you for your post.
I do not know why the information contained in the 'ELS/JuiceboxBuilder-Pro' folder is triggering the problem documented in this thread for some users but it is good to know that deleting the 'ELS/JuiceboxBuilder-Pro' folder (and allowing JuiceboxBuidler-Pro to generate a fresh one on its next run) seems to be solving the problem.

Set screenMode="LARGE" (in JuiceboxBuilder-Pro's 'Customize -> General' section) to display the gallery in Large Screen Mode on all devices and in all browsers.
More information about screen modes can be found in the Screen Modes section of the Gallery Tour.

I'm glad to hear that upgrading your gallery has resolved your iPhone 6 problem.
Thank you for letting me know.

However, I'm sorry to hear that you are still having trouble with your "Adobe.APS" problem.

Apologies, there was a slash missing from the path that I quoted. (I have corrected my previous post.)
The correct location should be:
~/Library/Application Support/Adobe/AIR/ELS/JuiceboxBuilder-Pro
... or:
/Users/Username/Library/Application Support/Adobe/AIR/ELS/JuiceboxBuilder-Pro

There will certainly be an 'ELS' folder (containing a subfolder named 'JuiceboxBuilder-Pro') somewhere on your hard drive and it should be in the path I corrected above.
If you cannot find the 'JuiceboxBuilder-Pro' subfolder by navigating towards it using the path, then try searching your hard drive for the term 'ELS'.
Once you have found the 'ELS' folder, delete the 'JuiceboxBuilder-Pro' subfolder within it (with JuiceboxBuilder-Pro closed).
This seems to have resolved the "Adobe.APS" problem for a couple of other users and I am hopeful that it will solve your problem, too.

Finding and deleting the 'JuiceboxBuilder-Pro' subfolder within the 'ELS' folder seems to be the key to solving the problem.
According to this Adobe forum post, the "Adobe.APS" problem is related to the Encrypted Local Store (ELS) API and deleting the ELS folder relating to JuiceboxBuilder-Pro (and allowing a fresh one to be automatically generated when the application is next run) should hopefully solve your problem.

With JuiceboxBuilder-Pro closed, please manually delete the following folders and try running JuiceboxBuilder-Pro v1.5.1 afterwards.
~/Library/Application Support/Adobe/AIR/ELS/JuiceboxBuilder-Pro
~/Library/Preferences/JuiceboxBuilder-Pro

This has worked for a couple of users in this forum thread.

If this does not help, then please try the "Fixing Mac EncryptedLocalStore database access error" procedure outlined in this Adobe forum thread. Please note that a couple of posts later in that thread, a user claims that it is necessary to reboot your computer after the deletions.

One other user who has reported such a problem (in this forum thread), discovered that a workaround was to uninstall Adobe AIR and then download and install an earlier version of AIR (from the Adobe AIR archive page).
I would not normally recommend using an older version of any software but if it helps to get someone back up and running, then it might be a useful piece of information.

I understand that you'd like to get JuicboxBuilder-Pro v1.5.1 up and running (and I hope that my notes above help) but please remember that you can upgrade your gallery without using JuiceboxBuilder-Pro by just replacing its existing 'jbcore' folder with the 'jbcore' folder from the Juicebox-Pro v1.5.1 zip package ('juicebox_pro_1.5.1/web/jbcore/').

No. stagePadding is a Large Screen Mode option only and there is no equivalent for Small Screen Mode. (Generally, browser viewports on mobile devices are small enough already and Juicebox-Pro does not feature an option to reduce the usable area of the gallery in Small Screen Mode.) If you want to introduce an unused area around your gallery in Small Screen Mode, you'd need to do so in your gallery's embedding web page using custom CSS (which is probably not as easy as it sounds in a 100% x 100% gallery which is designed to completely fill the web page).

As long as imageScaleMode is set to either SCALE_DOWN or SCALE, then all main images in the gallery should be displayed in their entirety without any cropping or stretching.
As far as I can recall, no-one else has reported such an issue with the current version of Juicebox-Pro (v1.5.1) so hopefully upgrading your gallery (and clearing your browser's cache before reloading your gallery's web page) will solve your problem.