That's very strange.
I've never known this to happen and, as far as I can recall, no-one has reported such a problem before.
It is also strange that the plugin used to work fine for you but now does not.
Changing gallery configuration options should have no bearing on the image export process.

What happens if you try to export a gallery using a different web engine such as Classic Gallery or Grid Gallery (one of the default web engines)? Are the images exported successfully when using these web engines? Is the problem just with the Juicebox web engine?

If you find that the problem happens with all web engines, then I would suggest reinstalling Lightroom itself to see if this helps.

If the problem happens only with the Juicebox web engine, then perhaps you could zip your incomplete gallery folder's 'index.html' and 'config.xml' files and attach them to a post (or upload them somewhere and provide a download link) so that I can check them out. Maybe there are clues within the exported HTML and XML files as to why the export process has been incomplete. Also, with access to your gallery's 'config.xml' file, I should be able to see your gallery's configuration options and can then try to replicate the problem myself using the same options.

Thank you.

You're welcome!
I'm glad it solved your problem. Thank you for letting me know.

It sounds like JuiceboxBuilder-Lite is choking on a certain image (or images).
If you try to add a batch of images more than once, does JuiceboxBuilder-Lite stop processing then images on the same image number each time?

Here are a few things to check and try which should hopefully point you in the right direction.

(1) Try adding your images in small batches to try to find a specific image that JuiceboxBuilder-Lite fails to successfully process. You may have one or more images that are somehow corrupt (perhaps just even corrupt metadata could prevent JuiceboxBuilder-Lite from successfully processing images).

(2) If you find an image that causes the problem, then try resaving it in an imaging program (such as Adobe Photoshop) to see if this resolves the problem.

(3) Also, if you find a problematic image (or have a small batch of images that consistently fails), please zip the image(s), upload the file somewhere and provide a download link so that I can try to replicate the problem with the same images that you are using.

(4) Try creating a fresh gallery with a completely different image source (maybe a different camera or phone or perhaps just some sample images from the internet) to see if the problem still occurs.

These suggestions might not solve your problem but they should at least help to narrow down possible causes.

Unfortunately, there are no specifics that I can give you. The best that I can suggest is that you use some trial and error to figure out what is safe for your system. If you find that JuiceboxBuilder does not crash when adding 250 images at once (for example), then it would be safer to limit your batches to 200 images at a time (to factor in an element of safety). I realise that this is less than ideal but it should prevent the application from crashing when you near the end of adding your batches.

I expect the relevant factor is the total filesize of the images in the batch but this is just speculation on my part. I have no access to the JuiceboxBuilder source code and do not know the exact reason for the problem (so cannot easily figure out a 100% safe workaround).

The developer are aware of this issue but I do not know when it might be addressed.
To collect more data on the issue, please let me know how many images you can add before the application crashes and what the total filesize of the batch is.
Also, please let me know what platform (Mac vs PC), operating system/version (e.g. macOS 10.13 or Windows 10 1809) and architecture (32-bit vs 64-bit) you are using and how much RAM your system has.
Thank you.

No. As far as I am aware, the problem is a limitation specific to Adobe AIR (the platform on which JuiceboxBuilder runs).

There is no way to migrate configuration option values from JuiceboxBuidler to Lightroom but, once you have a gallery set up in Lightroom, you can save the settings as a template and apply the template to future galleries (just like a 'Preset' in JuiceboxBuilder).

To set a template in Lightoom:
Once you've got a gallery configured that way you'd like it to be in Lightroom (using the individual controls in the Lightroom plugin's interface), you can save the combination of configuration options as a Lightroom template by clicking the + sign to the right of the text 'Template Browser' (in the left panel of the 'Web' section) and selecting a name for the template.
At any time in the future, if you want to apply this combination of configuration options to a gallery, expand the 'Template Browser' control panel, scroll down to the 'User Templates' section and select the template.

A frame-driven website is likely to be less than optimal on mobile devices (as you have discovered) and, additionally, there are drawbacks to loading a Juicebox gallery into an frame. These drawbacks are noted here (scroll down to "2) Using an iframe").

If possible, it would be much better to layout your page using CSS rather than frames and to embed the gallery directly into the web page following the embedding instructions here.

If you are looking to have a web page with a side menu, then I would recommend taking a look at the View Resizable Gallery with Side Menu Example in the Using a Resizable Gallery support section.
You can view the source of the sample web page in your browser and copy/modify it to suit your own needs.

If you are looking for an automated way to create your complete website, you might be interested in another one of our products, namely Showkase.

Showkase is a PHP web application (installed on your web server instead of your computer) which allows you to create a complete portfolio web site (integrating multiple galleries) online.
Showkase has full support for Juicebox-Pro and the galleries can be created within the application itself in a web browser interface (or created with JuiceboxBuilder and imported).

You can create Gallery Index pages and have as many galleries listed on each Gallery Index page as you wish.
Each gallery is represented by a thumbnail image with the gallery title displayed below and the gallery is opened when the user clicks on the image.
Demo sites created with Showkase can be found here and a sample Gallery Index page can be found here.

Showkase can also create non-gallery pages (About, Basic and Contact pages) where you can add information about yourself (or any other content you like).
All of this is done automatically within the Showkase interface without the need for any manual coding at all.
You can check out the Showkase interface by logging into the Live Demo Admin.

Showkase comes with several different themes, (Boma, Kosel, Maribo) and Boma features a side menu (whereas Kosel and Maribo both feature a top menu). Here is a sample site created in Showkase with the Boma theme.

Showkase can be purchased as Showkase-Standard (which comes with Juicebox-Lite, the free version) or Showkase-Pro (which comes with Juicebox-Pro).
The only difference between Showkase-Standard and Showkase-Pro is the bundled viewer (Juicebox-Lite vs Juicebox-Pro).

I hope these notes help.

You're welcome.
I hope the workaround isn't too inconvenient.

This is possible only with Juicebox-Pro (but not Juicebox-Lite, the free version).

With Juicebox-Pro you can set the thumbsPosition (the position of the thumbnails: TOP, BOTTOM, LEFT or RIGHT) and maxThumbRows and maxThumbColumns.

When thumbsPosition is set to either LEFT or RIGHT, the number of thumbnail columns is fixed at the maxThumbColumns value whereas the number of thumbnail rows is variable (up to the maxThumbRows value) depending on the dimensions of the thumbnails and the space available in the user's browser.
Take a look at this demo gallery with 3 columns of thumbnails: https://www.juicebox.net/demos/pro/simp … umbRows=10

When thumbsPosition is set to either TOP or BOTTOM, the number of thumbnail rows is fixed at the maxThumbRows value whereas the number of thumbnail columns is variable (up to the maxThumbColumns value) depending on the dimensions of the thumbnails and the space available in the user's browser.
Take a look at this demo gallery with 3 rows of thumbnails: https://www.juicebox.net/demos/pro/simp … ion=CENTER

With Juicebox-Pro, you can create a Multi-Size Image gallery.
The Medium images will be displayed in the gallery and the Large images will be displayed when the images are opened on pages of their own.
If you do not want a Multi-Size Image gallery, then you can assign a unique linkURL for each image (which you could point towards a large image).

Set imageClickMode="OPEN_URL" (in JuiceboxBuilder-Pro's 'Customize -> Main Image' section).
If the image has a linkURL associated with it, then, when the main image is clicked, the linkURL will be opened in the linkTarget window (_blank, _self, _parent or _top). Otherwise, the largeImageURL will be opened and, failing that, the imageURL (the actual image used in the gallery) will be opened.

In Juicebox-Lite, you can use the Open Image button. (In Juicebox-Lite, it is not possible to change the image click functionality.)
Set showOpenButton="TRUE" (on JuiceboxBuilder-Lite's 'Customize' tab) to display the Open Image button on the gallery's Button Bar.
You can set a linkURL and linkTarget (click an image's thumbnail on the 'Images' tab to reveal the input fields at the bottom of the window) for each image.
You'll need to provide the large images yourself and ensure that your linkURL entries point towards them (with either absolute or relative paths).

I hope this helps to clarify things.
Please let me know if you have any further queries.

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.