It looks like you are using the regular embedding code (https://www.juicebox.net/support/embedd … -html-page) so your gallery's 'jbcore' folder should be in the same directory as the embedding page ('pumpkin-gallery-jb.html').

Therefore, your gallery's 'juicebox.js' file should be located here: http://www.pumpkingutter.com/jbcore/juicebox.js
However, going directly to that location in a browser results in an error 404 (file not found).

Upload your gallery's 'jbcore' folder to your root directory (alongside your 'pumpkin-gallery-jb.html' web page) and your gallery should display as expected.

Please let me know how you get on.
Thanks.

(Incidentally, I see a white screen in my desktop browser, too. It's the same problem, though, so the solution above should allow the gallery to be displayed in all browsers.)

The problem occurs because your gallery has a fixed size and shape (a fixed aspect ratio) but your images are of different shapes and sizes and, when using the default imageScaleMode (SCALE_DOWN), the images are scaled to fit within the gallery without cropping but if the images do not have exactly the same aspect ratio as that of the gallery itself, then there will be some space surrounding the images in the gallery (either to the left and right or the top and bottom, depending on the image's aspect ratio). The space surrounding the images will show up as the gallery's background color.

The solution would be to give your gallery a fully transparent background color (rather than the default grey color) so that the space surrounding the images is not visible.

In your gallery's embedding code on your 'chboxtester.html' page, change:

backgroundColor: 'rgba(34,34,34,1)'

... to

backgroundColor: 'rgba(0, 0, 0, 0)'

This should hopefully resolve your problem.

Incidentally, I notice that you do have a solid white backgroundColor set in your gallery's 'config.xml' file (which would also work as as it would invisibly blend in with your embedding page's background color which is also white) but configuration options set in the gallery's embedding code take precedence over configuration options set in the 'config.xml' file (as noted in the short Setting Config Options support section) and you still have the default grey backgroundColor set in the embedding code.

That's good to hear.

Indeed. I'll bounce some ideas off the decision makers. I don't know where it'll go but I'll be sure to post back here if I have any news on the subject.

Incidentally, the requirement to use Rosetta is listed as a Known Issue on Harman's AIR runtime download page: https://airsdk.harman.com/runtime

Update:

It looks like Harman is looking to replace WebKit with a new embedded browser, according to this comment:
https://github.com/airsdk/Adobe-Runtime … 1216482803

If/when Harman implements this, there would no longer be a need to stick to AIR v33.1.1.743.
Although there is no problem in sticking with AIR v33.1.1.743, it would mean that anyone could just grab the latest AIR runtime without running into the problem.

Fingers crossed this happens soon...

I'm glad you found it! Thanks for letting me know.

Juicebox and Showkase are two different products (with different download links).
I've reactivated the download link for your Showkase-Standard purchase and you should receive an email with the link.

Once you have downloaded the current version of Showkase (v1.7.6), full instructions for upgrading can be found here.

Notes:

(1) When upgrading your Showkase site, please be sure to make a complete backup of your existing site first, just in case anything should go wrong and you need to reinstate your original files at a later date. You should not encounter any problems upgrading Showkase but it would be wise to have a backup of your site should anything unexpected happen. Also, if you have made manual customizations to any Showkase source files, then please note that they may be overwritten when you upgrade and you'll need a backup in order to reinstate them afterwards.

(2) Please remember that Showkase-Standard comes bundled with Juicebox-Lite (the free version of Juicebox) so, after upgrading your Showkase site, you'll need to reinstate your Juicebox-Pro files by following the Installing Juicebox Pro instructions here.

Please let me know if I can be of any further assistance.

It is possible to have just a single gallery displayed on a web page and switch the gallery (using links).
Check out the 'Switching between Multiple Galleries using JavaScript' example in the Embedding Multiple Galleries support section.

I've made a single-page template using this method and have posted it here (with instructions).
You could use/modify it to suit your own needs (or, at the very least, examine the code to see how it works).

If you are looking for a fully automated way to create and list multiple galleries, then you might like to look into another of our products: Showkase.

Showkase is a PHP web application (installed on your web server rather than 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 or the Lightroom plugin and then imported via Showkase's 'Site -> Import' functionality).

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 (just like your current website).
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) from the Download Page.
The only difference between Showkase-Standard and Showkase-Pro is the bundled viewer (Juicebox-Lite vs Juicebox-Pro).
If you already have Juicebox-Pro, then you could purchase Showkase-Standard (if you wanted to) and integrate your Juicebox-Pro files by following the 'Installing Juicebox-Pro' instructions here.

I hope this information is helpful.

Hi.
I'm sorry to hear that you are having difficulty with Juicebox-Pro.
I hope my notes below help.

First of all, just in case you've not yet seen it, please take a look at the Embedding Multiple Galleries support section. There are several online examples (whose source you can view in your browser) which might help.

The key to embedding multiple galleries into a single web page is to keep the galleries separate from each other and, as you have already tried, embed each gallery into a container with a unique 'id'. (Make sure that the containerId in the embedding code matches the actual 'id' of the container <div>.)

The easiest way to do this would be to use the baseUrl method of embedding documented here. This allows you to keep each gallery in its own individual folder (and prevents gallery files from getting mixed up or overwritten).
The baseUrl embedding code is essentially the same as the regular embedding code but with a baseUrl entry pointing towards a gallery folder.

Also, you'll only need to load the 'juicebox.js' file once per page (not once per gallery), so just load the file from within one of your galleries.

Here's an example.

(1) Create two galleries with JuiceboxBuilder-Pro and save them to two different folders named 'gallery1' and 'gallery2'.

(2) Upload these two complete gallery folders to the root directory of your web server.

(3) Now use the following embedding code (which will display the galleries one below the other).

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

<script>
  new juicebox({
    baseUrl: "/gallery1/",
    containerId: "juicebox-container1",
    galleryWidth: "800",
    galleryHeight: "600",
    backgroundColor: "#222222"
  });
</script>
<div id="juicebox-container1"></div>

<script>
  new juicebox({
    baseUrl: "/gallery2/",
    containerId: "juicebox-container2",
    galleryWidth: "800",
    galleryHeight: "600",
    backgroundColor: "#222222"
  });
</script>
<div id="juicebox-container2"></div>

The leading slashes in the paths above denote your root directory so the code above will work (without modification) in any web page throughout your site as long as your gallery folders are named 'gallery1' and 'gallery2' and are located in your root directory.

You can, of course, name your gallery folders anything you like and upload them to any location you like, as long as the paths in the embedding code (the path to the 'juicebox.js' file and the baseUrl entries) are correct.
The baseUrl entries can be relative paths (relative to the web page containing the embedding code) or absolute paths (starting with http:// or https://).

I hope this helps.
However, if you continue to experience difficulties, please let me know and I'll try to help further.
If possible, please post a link to your web page so that I can see the problem for myself and hopefully determine exactly what the problem is and propose a solution.
Thank you.

Feature request from InVietDung (original thread):

I deleted my Documents folder and I can reproduce the problem; the "Upgrade to Juicebox-Pro!" message appears.
(I never doubted you, I just couldn't explain what was going on!)

I notice that as well as the "Upgrade to Juicebox-Pro!" message appearing, the embedded "JuiceboxBuilder-Pro" logo/image (usually at the left-hand side of the same top area that the 'upgrade' message is on) does not appear.

I guess that JuiceboxBuilder just errors out as soon as it tries to access a non-existent Documents folder and stops running its script (before the upgrade message is hidden and the embedded image is shown).

The moral of the story is that JuiceboxBuilder should check for the existence of the Documents folder before proceeding (and perhaps use an alternate location to store the working folder if the Documents folder does not exist) but, in the meantime, for anyone else reading this and experiencing similar issues, the best solution is just to make sure that your system has a valid Documents folder.

Thanks again for your notes. They've been most helpful in understanding what's going on.