You could always embed the information within your images as IPTC data (using a program such as Lightroom or Photoshop) so that, no matter what the images are named, the information always travels with the images wherever they go (and can be read by most imaging programs).

JuiceboxBuilder-Lite can also extract IPTC data from images for use as the image titles (IPTC Document Title) and image captions (IPTC Description) via the 'Images -> Titles -> Use IPTC Title' and 'Images -> Captions -> Use IPTC Captions' options from the drop-down menu at the top.

However, please be aware that when JuiceboxBuilder-Lite resizes images, all metadata is removed for the resulting gallery images so, if you have IPTC data within your images and want this data to remain in the gallery images, then resize your images in an imaging program first, prior to feeding them to JuiceboxBuilder-Lite, and deselect the 'Resize Images' checkbox on the 'Images' tab (so that JuiceboxBuilder-Lite does not process the images further).

You're welcome.
I'll mark this thread as 'solved' but if you have any further trouble, just post back here and I'll do my best to help you out.

It certainly sounds like there might be a problem with certain images and, when JuiceboxBuilder-Lite chokes on them, the publishing process grinds to a halt, resulting in an incomplete gallery folder.
If you could upload the images that you are having trouble with (so that I can download them and use them in a test gallery), I'll certainly take a look to see if I can replicate the issue (and maybe find the root of the problem).

It seems very strange that you have re-saved the image in different formats and JuiceboxBuilder-Lite rejects them all.
Normally, if an image is corrupt, the best thing to do is find an imaging program that can open it and then just re-save it (without making any changes to it). The process of re-saving the image can sometimes fix any problems with it.

That's good to hear. Thank you for letting me know.

I notice that your image filenames are very long. The 4th image in your 1st gallery, for example, has 194 characters in it (not counting the file extension).
When working with these files on your computer, you might be reaching the Windows maximum path length (MAX_PATH) of 260 characters. Please see this Microsoft web page for details.
If your image is in your 'Pictures' folder (for example), then this could add approximately 20 characters to the path length (depending on your user account name) but if your images are stored in a deeper file structure, then you could quite easily be pushing the 260 character limit and this might be causing problems.
I would recommend that you reduce the number of characters in your image filenames to see if this helps with your problems.
Incidentally, as noted in the web page I quoted above:

The 4th image has not really disappeared. Your 'Test-5' gallery seems to be an incomplete copy of your 'Test-4' gallery. Your 'Test-5' gallery uses its own set of images (its own 'images' folder) completely independent of the images being used for your 'Test-4' gallery.)

In your 'Test-5' gallery, the 4th image does not appear to be present in your gallery's 'images' folder.
According to your gallery's 'config.xml' file, the 4th image should be located here:

http://www.sirnigelgresley.org.uk/PhotoArchive/Test-5/images/Peter Lane - 4498 on a photo run-through at Appleby on 25th September 1993. Cumbrian Mountain Express with headboard The New Inn Farewell. Photograph taken from far north end of station platform.jpg

... but going directly to that location in a web browser (taking Juicebox-Lite out of the equation) results in an error 404 (file not found).
Please double-check that the image is present in the correct folder on your web server.

The 5th image in your 'Test-5' gallery gives a different error when trying to view it directly in a web browser.

This seems to be due to the use of the '–' character in the image filename. This is not just a regular hyphen '-' but a special character that seems to be encoded as '–' on your web server.

As an image filename forms part of a URL when uploaded to a web server, it would be wise to use only web-safe characters within image filenames. Please see section 2.3 of this document for details.

I would recommend using only the characters noted in the quote above for your image filenames (and not other characters such as spaces, '&' and '–'). (JuiceboxBuilder-Lite can handle all images whose filenames use any or all of these unreserved characters.)

Using shorter, web-safe image filenames might help to solve your problems (both on your computer and on your web server).
I hope this helps.

Edit:
I was typing my reply whilst you posted your last response.
I'm glad that you've been able to figure out the cause of your problem. Thank you for letting me know.
Hopefully my notes above will give a little more information on the nature of the problem.

Please let me know if you're unable to resolve your issue with the blank thumbnail (let me know which gallery you are referring to) and I'll take a look to see if I can help further.

Take a look to see if you have a folder named '.tempGallery' (inside a folder named 'JuiceboxBuilder-Lite') in your 'Documents' folder.

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

If you find such a folder, try deleting it manually (whilst JuiceboxBuilder-Lite is closed).
This should hopefully fix the problem with the 'New Gallery...' and 'Open Gallery' buttons.

Normally, JuiceboxBuilder-Lite will delete the '.tempGallery' folder itself when the program closes but, if the program has crashed, then the '.tempGallery' folder may remain and prevent the 'New Gallery...' and 'Open Gallery' buttons from working.

With regard to the image sizing issue, there is unfortunately a known issue whereby JuiceboxBuilder-Lite will display an error message ("Error resizing image: ‘xyz.jpg’. Possibly the image was too large or invalid. Images must be smaller than 4095 x 4095 pixels.") if the resize dimensions are too large (even if the source images are well within the maximum image bounds).
The problem seems to happen when the Max Width and Max Height are somewhere within the range of between 2364px and 2504px.
The developers are aware of this issue and will hopefully be able to resolve the problem for a future version.
In the meantime, we can only work around this issue by doing one of the following:
(1) Ensure that the resize image bounds are lower than 2364px (or the threshold for your own scenario which is likely to be close to this value).
(2) Resize your images in an imaging program (such as Adobe Photoshop) prior to feeding them to JuiceboxBuilder-Lite and deselect the 'Resize Images' checkbox (on the 'Images' tab) to instruct JuiceboxBuilder-Lite to simply copy the images across to the gallery's 'images' folder (and not process them further).
(3) Create your gallery using a different method. Please see here for a list of plugins available for different programs.

I realise that this may be inconvenient but at least knowing about the problem, we can work around it until it is fixed.

I hope these notes at least help to explain things (even though I am unable to offer a direct solution to the image sizing issue).

No problem!
I'm glad you've got it working. Thank you for letting me know.

I'm very glad to hear that you have been able to resolve your server permissions problem and that all the Showkase Server Compatibility tests now pass OK. Thank you for letting me know.

That would be fine. In order to keep accurate licensing and transaction records, it would be best for you to purchase Showakse-Pro from the purchase page here and for us to then refund you in full for Juicebox-Pro.

There is no need to do this. When you purchase Showkase-Pro, you receive a Juicebox-Pro Single-Site License and the Juicebox-Pro files are exactly the same whether you purchase Juicebox-Pro or Showkase-Pro.

Just let me know when you've purchased Showkase-Pro and I'll get the refund for Juicebox-Pro underway for you.
Thank you.

Thank you for providing the additional information.
As you have uploaded a complete gallery folder ('ephemeralheaven') to your web server, then you can use the baseUrl method of embedding documented here.

In the original code you posted, you have the following line of code:

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

If you had kept this as is and just added the baseUrl entry I suggested, then your gallery would have displayed fine.
However, I notice that you now use:

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

... so the path to the gallery's 'juicebox.js' file is now incorrect.

Use the following embedding code (before your 'juicebox-container' <div>) and all should be well.

<script src="pics/ephemeralheaven/jbcore/juicebox.js"></script> 
<script>
    new juicebox({
        baseUrl: "pics/ephemeralheaven/",
        containerId: "juicebox-container",
        galleryWidth: "100%",
        galleryHeight: "100%",
        backgroundColor: "rgba(255,255,255,1)"
    });
</script>

This should hopefully resolve your problem.
Please let me know how you get on and if you need any further assistance.
Thank you.

Please see the following FAQ which deals with the "Config file not found." message and may help.
When I view my gallery I see the message 'Config file not found'. How do I fix this?

As you are currently using the regular embedding code (with no baseUrl or configUrl), then the gallery's 'config.xml' file should be in the same directory as the web page containing the embedding code. Please make sure that the 'config.xml' file is there.

Looking at your embedding code, it looks like your 'ephemeralheaven' folder might be a complete gallery folder.
If this is the case, then you should be able to use the baseUrl method of embedding (documented here) to point towards your gallery folder.
Try adding the following line to your embedding code:

baseUrl: "pics/ephemeralheaven/",

If neither of the suggestions above help, then please post the URL to your gallery's web page so that I can take a look at the problem for myself and help further.
Also, please let me know where on your web server you have uploaded your gallery files to.
Once I'm able to see your gallery's web page live on your web server (and know the location of your gallery files), I should hopefully be able to determine the exact cause of the problem and propose a solution.
Thank you.

If the folder contains only presets, then it is doubtful that removing the folder will help.
However, in the absence of knowing exactly what is causing your problem, I would not rule anything out quote yet.
Try temporarily removing the folder (either rename it and then rename it back to its original name afterwards or move it to a different location and move it back to its original location afterwards) whilst JuiceboxBuilder-Pro is closed to see if this helps.

No, this is not the problem. JuiceboxBuilder-Pro does not need a special code or use a serial number (although downloads are restricted to licensed users only and installing the application without a valid license would violate the terms of use).
As long as you have the JuiceboxBuilder-Pro.air installation file, you should be able to install and run JuiceboxBuilder-Pro successfully.

I'm glad that you have at least been able to upgrade the Photoshop plugin to Juicebox-Pro and get local viewing working in Safari 11. Thank you for letting me know.

Showkase is a PHP web application (installed on your web server rather than your computer) which is designed to create a complete portfolio website (integrating multiple galleries) in a web browser interface, although you could use Showkase in its Gallery Manager theme to just create and edit Juicebox-Pro galleries online (which you could embed into other non-Showakse pages throughout your website).
Showkase has full support for Juicebox-Pro and the galleries can be created within the application itself (or created with JuiceboxBuilder-Pro 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 take a look around the Showkase interface by logging into the Live Demo Admin.

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).
If you want to purchase Showkase-Pro (less expensive that purchasing Showkase-Standard and Juicebox-Pro separately), then we would happily refund you in full for your Juicebox-Pro purchase.

There is more information on the differences between Juicebox and Showkase in this forum thread.
If you have any further queries, please let me know.

Getting back to JuiceboxBuilder-Pro, have you tried creating a new administrative user account and installing and running JuiceboxBuilder-Pro under the new user account yet?
I still think this is worth a shot. It should at least let us know whether there is something about your present user account which is causing your problem or otherwise perhaps a system wide contributing factor.

Unfortunately, I really do not know what might be causing your problem.
If a clean install of both Adobe AIR and JuiceboxBuilder-Pro does not work, then it sounds like there might be something on your system (such as some security software) that is interfering with the functionality of the application.
Did you try creating a new administrative user account and installing JuiceboxBuilder-Pro under the new user account?

If you have successfully replaced the Lite 'jbcore' folder with the Pro version, then the plugin has no choice but to create Juicebox-Pro galleries. (The plugin will no longer contain the Juicebox-Lite files.)
You can check to see if your galleries are Lite or Pro by the presence of the Juicebox logo in the lower right corner of the galleries. The Juicebox logo is present in all Lite galleries but not in Pro galleries.
Please note that upgrading the plugin does not change the plugin's interface. The interface will look the same as before upgrading (only Lite options can be changed in the interface) but all galleries subsequently created by the plugin will be Pro galleries (with no branding or image limit). Galleries created with the plugin can be customized with Pro configuration options by opening them in JuiceboxBuilder-Pro (but I realise that you cannot currently do this).
Programs and plugins which feature all Pro configurations in their interfaces are JuiceboxBuilder-Pro, the Juicebox Lightroom Plugin and Showkase.

Juicebox galleries cannot be viewed locally in all browser due to certain security restrictions.
Please see this FAQ for details:
When I view my gallery locally, I see the message "Juicebox can not display locally in this browser". Why?

This issue is specific to viewing galleries locally (from your computer's hard drive) and there is no such issue once the galleries have been uploaded to a web server (where they can be viewed in any modern browser).

If you encounter the "Config file not found." message whilst trying to view a gallery locally in Safari 11, then please see this forum post for a full explanation and a workaround.

Unfortunately, Safari 11 (released 19 September 2017) introduced a new security restriction which prevents local viewing of Juicebox galleries by default. Selecting 'Disable Local File Restrictions' from Safari 11's 'Develop' menu (full instructions in the link above) should, once again, allow you to view your galleries locally in Safari 11.

You're welcome!

I'm glad that you've been able to resolve your problem.
Thank you for taking the time to let me know. It's most appreciated.

The 'height' attribute is, indeed, not allowed on a <div> element in HTML 5 but it seems that using the jQuery height(value) method on a <div> such as:

<div id="test"></div>
<script>
$(document).ready(function() {
    $('#test').height(600);
});
</script>

... actually sets the height using inline CSS via a 'style' attribute rather than a 'height' attribute (at least in my own tests) as follows:

<div id="test" style="height: 600px;"></div>

... which is valid HTML 5, so I'm not quite sure why using css(propertyName, value) works whereas height(value) does not.

In any case, I'm glad that you've been able to fix your problem.
Thank you for sharing your solution. It might certainly help others facing a similar problem.

The viewport meta tag will affect how your web page looks on mobile devices only. It will have no effect in desktop browsers.

Your gallery currently has a fixed width of 748px (galleryWidth: "748") so your gallery's width will always be 748px, regardless of the dimensions of other containers on your web page.
Instead, set your gallery's width to be 100% (galleryWidth: "100%") and your gallery's width will always fill the width of the gallery's parent container (no matter what the width of the gallery's parent container is).

This should hopefully solve your problem.