326

(1 replies, posted in Juicebox-Pro Support)

If the caption area is positioned on the overlay (captionPosition="OVERLAY" or captionPosition="OVERLAY_IMAGE"), then the caption area will dynamically grow or shrink to accommodate the caption text up to a maximum height determined by maxCaptionHeight (default value 120px).

If the caption area is positioned anywhere else (captionPosition="BELOW_IMAGE", captionPosition="BOTTOM" or captionPosition="BELOW_THUMBS"), then the caption area will always be at a fixed height determined by maxCaptionHeight .

If you don't mind your caption text overlapping the images, then set captionPosition="OVERLAY" or captionPosition="OVERLAY_IMAGE" and increase the value for maxCaptionHeight.
(The overlay can be toggled on and off as long as showImageOverlay="AUTO").

For reference, short descriptions of all configuration options in bold above can be found on the Config Options support page.

If you want to actually change the font size for the caption text, then please see this forum post:
Changing font size of image titles and captions (and gallery title)

I hope this helps.

It might be a good idea if you alerted your other Customers to this issue; and perhaps provided some new downloadable Presets to address this problem?

It's certainly something for the developers to think about (I don't make design decisions around these parts), although the workarounds are simply to set either backButtonHAlign="CENTER" or useFullScreenExpand="FALSE" which are easy enough to implement.
Other more complex solutions, such as settings one of these configuration options conditionally (e.g. only in Mobile Safari on iPads running iOS 12 or later) can only be achieved through JavaScript and not simply through use of a preset.

Also, some people might actually like Apple's 'Exit Fullscreen' button! There are plenty of people on the internet who are vocal about it and want to try to disable it but it's probably only those who do not like it that have reason to post. Those that like the 'Exit Fullscreen' button are perhaps a silent majority.

In any case, this forum thread serves as a reminder of what can be done to work around the issue.
There should be enough keywords within this thread that anyone searching for the issue will end up here.

One other thing that i came across is that Adobe Dreamweaver is showing an Error on Line 14 of the JB Javascript.

The error that Dreamweaver reports is nothing to worry about.
An unnecessary semi-colon at the end of a line of JavaScript code will simply be ignored by browsers and is not a functional problem.
Also, it looks like the semicolon in question is actually being introduced by the packer we use to compile the JavaScript source code. (The semi-colon is not in our source code.)
The semicolon (line 14, column 246) comes after the closing '}' character of an 'if' block and immediately before the start of a 'while' loop.
If you enter any JavaScript code at all (e.g. var a;) into this online packer,, select the 'Base62 encode' checkbox and click the 'Pack' button, you'll see exactly the same thing (although at a different column number) in the packed output code.

So, essentially, it's nothing to worry about and nothing that we can do anything about unless we change our JavaScript packer (and one extra benign semicolon is perhaps not reason enough to change).

Thank you for reporting it, though. If it was a functional problem, we'd most certainly want to know.

You're welcome!

I'm really glad that you've found a solution that you're happy with.
Thank you for letting me know.

Just for clarification, it looks like Apple introduced Fullscreen API support (including the 'Exit Fullscreen' button) on the iPad in iOS 12 so, if you wanted to do a conditional check on the version of iOS being run, then iOS 12 or later is what you'd be looking for.

Here's a quote from Apple's Safari 12 Release Notes page:

Added support for viewing HTML elements in full screen on iPad.

I'm so sorry... I've just noticed there was a small but crucial error in the code I provided which might be causing some confusion.
I've corrected it in my post above (in case anyone copies it in the future).
The correct line of code should be:

var customPosition = isIPad() ? 'CENTER' : 'LEFT';

(Note the two brackets after 'isIPad'.)

I guess I was playing around with functions and variables before I decided on what to post and I ended up with a mismatch.
Anyway, if you change the line above, you'll find that the Back Button is centred only on iPads. On other devices (including desktops), the Back Button will be positioned to the left.

A couple of other notes which might help to clarify some things...

... and Apple's Horrible X has been obliterated!

The cross should not appear if you set fullScreenExpand="FALSE". If fullscreenExpand="TRUE", then the cross should appear, no matter what other configuration options are used.

However, the trade-off on a large-screen computer is that the images in a Gallery will no longer fill the Browser window (as you will see that they do in the original link to "Lemurs, Bronx Zoo" on the Landing-page.

I see no difference in the size of the images between your Bronx_Zoo and Bronx_Zoo-TESTING galleries (tested in a desktop browser).
Other than the position of the Back Button (which should be the same in both galleries after you change the code above), they seem identical to me.

It is probably not possible to further refine the Script to say, in effect:
"Ignore the Script unless the User is using Mobile Safari on a newer iPad" ?!!

It's possible to specifically target more recent versions of iOS but there seems to be no easy way to determine the version of iOS other than parsing the user agent string and there are many ways to do this.
There are several different examples on these pages:
https://stackoverflow.com/questions/757 … e/13549283
https://stackoverflow.com/questions/834 … javascript

I'm not sure in which version of iOS the fullscreen exit button was introduced but here's some code which should center the Back Button only on iPads running iOS 12 or greater you can change this version number in the code if you need to), with the Back Button positioned left in all other cases.

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

    function isIPad() {
        var agent = window.navigator.userAgent;
        return /iPad/i.test(agent);
    }

    function iOSVersion() {
        var agent = window.navigator.userAgent;
        var start = agent.indexOf('OS ');
        if (/iP(ad|hone|od)/i.test(agent) && start > -1) {
            var match = agent.match(/OS (\d+)_(\d+)_?(\d+)?/);
            var version = [parseInt(match[1], 10), parseInt(match[2], 10)];
            return parseFloat(version.join('.'));
        }
        return false;
    }

    var customPosition = isIPad() && iOSVersion() >= 12 ? 'CENTER' : 'LEFT';

    new juicebox({
        containerId: "juicebox-container",
        galleryWidth: "100%",
        galleryHeight: "100%",
        backgroundColor: "rgba(204,204,204,1)",
        backButtonHAlign: customPosition
    });

</script>

You could do likewise with the useFullscreenExpand configuration option (using the Fullscreen API on all devices except the iPad) if you like.

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

    function isIPad() {
        var agent = window.navigator.userAgent;
        return /iPad/i.test(agent);
    }

    function iOSVersion() {
        var agent = window.navigator.userAgent;
        var start = agent.indexOf('OS ');
        if (/iP(ad|hone|od)/i.test(agent) && start > -1) {
            var match = agent.match(/OS (\d+)_(\d+)_?(\d+)?/);
            var version = [parseInt(match[1], 10), parseInt(match[2], 10)];
            return parseFloat(version.join('.'));
        }
        return false;
    }

    var fullscreen= isIPad() && iOSVersion() >= 12 ? 'FALSE' : 'TRUE';

    new juicebox({
        containerId: "juicebox-container",
        galleryWidth: "100%",
        galleryHeight: "100%",
        backgroundColor: "rgba(204,204,204,1)",
        useFullscreenExpand: fullscreen
    });

</script>

I hope this helps.

To implement my suggestion, you'll need to modify the JavaScript embedding code in your gallery's HTML web page. (You can't add HTML or JavaScript code to the gallery's XML file which is why you need to insert the conditional configuration option into the embedding code instead.)

For example, for your 'Song Birds Of Costa Rica Gallery', you'll need to edit the web page into which the gallery is embedded, i.e.:
https://shelbourne-america.net/Birds_CostaRica/index.html

Then, you'll need to change the following embedding code (starting at line 24) from:

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

... to:

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

    function isIPad() {
        var userAgent = window.navigator.userAgent;
        return (userAgent.match(/iPad/i));
    }

    var customPosition = isIPad() ? 'CENTER' : 'LEFT';

    new juicebox({
        containerId: "juicebox-container",
        galleryWidth: "100%",
        galleryHeight: "100%",
        backgroundColor: "rgba(204,204,204,1)",
        backButtonHAlign: customPosition
    });

</script>

You can leave the entire 'juicebox-container' <div> (below the code above in your gallery's web page) completely unchanged.
Just change the code noted above and all should be well.

It is unfortunate that Apple see the need to overlay their 'Exit Fullscreen' button on top of the web page (with no way to disable it), obscuring what might be underneath it, when other browsers (e.g. Mobile Chrome) manage not to do this on the same platform.
Maybe they'll allow a way to hide the button in the future (or decide to remove it in preference to a different solution).

This is not the first time that Apple have tried to improve the fullscreen experience in Mobile Safari, only to backtrack later on.
Apple introduced the 'minimal-ui' meta tag in iOS 7.1 (as a way to remove the toolbars from the browser viewport) and web developers (including ourselves) adopted this practice at the time. However, Apple then decided to remove support for 'minimal-ui' in iOS 8. Try a web search for 'minimal-ui' for more information.

You can set Juicebox configuration options in the embedding code (please see here for details) so, with a little custom JavaScript code, you could specifically target the iPad and set a particular configuration option to a certain value, depending on whether or not an iPad is being used to view the gallery.

As an example (just to clarify), you could use backButtonHAlign="CENTER" for the iPad and backButtonHAlign="LEFT" for all other devices.

Options set in the embedding code take precedence over those in the configuration file ('config.xml').

Here's an example:

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

    function isIPad() {
        var userAgent = window.navigator.userAgent;
        return (userAgent.match(/iPad/i));
    }

    var customPosition = isIPad ? 'CENTER' : 'LEFT';

    new juicebox({
        containerId: "juicebox-container",
        galleryWidth: "100%",
        galleryHeight: "100%",
        backgroundColor: "#222222",
        backButtonHAlign: customPosition
    });
</script>
<div id="juicebox-container"></div>

You could do likewise for useFullscreenExpand (or any other configuration option) if you like.

If you wanted to target only Mobile Safari on the iPad and not other browsers like Mobile Chrome, then the JavaScript detection code would get rather messy as the user agent strings for Mobile Safari and Mobile Chrome are very similar to each other.
Take a look at this thread for inspiration.

There are browser-specific compatibility notes for the Fullscreen API here: https://caniuse.com/fullscreen

If you hover over "Safari on iOS",  "14.7" (released a couple of days ago), you'll see the following note, which seems pretty conclusive that there's no way to disable the cross.

Partial support refers to supporting only iPad, not iPhone. Shows an overlay button which can not be disabled.

It looks like the two best (and easiest to implement) workarounds would be to either:
(1) Not show the cross, by not implementing the FullScreen API when expanding the gallery from the Splash Space (by setting useFullscreenExpand="FALSE").
... or:
(2) Move the Back Button (e.g. backButtonHAlign="CENTER") so that the cross does not obscure it.

I hope one of these suggestions is suitable for your galleries.

Thank you so much for going to the trouble of posting screenshots (and for persevering with the forum software to do so!).

It is very interesting to see the cross that you are talking about.
It is curious to see that the cross and its background are not the same size as the Juicebox Back Button.
I suspect that the cross is actually covering up the Juicebox Back Button rather than replacing it.

Unfortunately I cannot update iOS on my old iPad 2 to test my theory but I suspect that the cross might actually be a feature of a later version of iOS on the iPad.

When you expand your gallery from the Splash Page, your gallery expands to fill the entire viewport, using the Fullscreen API (your gallery sets useFullscreenExpand="TRUE").
It looks to me like the cross might be Mobile Safari (on iPad only) presenting a way for the user to exit fullscreen mode.

This would explain why you do not see the cross in our demo galleries (they are not fullscreen, just full browser) and why I do not see the cross on my own iPad (it's too old).

It does not look like a coding fault (everything looks OK as far as I can tell) or even a fault of any kind. The cross looks intentional, like it's meant to be there (rather than an indication that something is wrong).

If my theory is correct, then if you set useFullscreenExpand="FALSE", you'll not see the cross.

Bingo!
https://dgrin.com/discussion/265876/ipa … e-x-button

Unfortunately, I've not found a way to disable the cross. (I'm not sure it's possible.)
It looks like the best course of action would be to either keep your BackButton centered or set useFullscreenExpand="FALSE".

Just to clarify a couple of your other points (which might now be somewhat redundant)...

I suppose that I could strip iOS completely from my iPad and get a fresh Install from Apple (if that is even possible?); and then re-install all of my personal data from a Back-up?

Yes. You can download the relevant iOS images from https://ipsw.me
The downloads come directly from Apple's update servers. (You'd need to back up your personal data first and it's a long process... not just a quick 5-minute job.)
You'll not need to do this, though. (It won't make a difference.)

I have just noticed something in my html coding which might be upsetting Safari:
I had TWO Head sections in the file!

It is certainly a good idea to fix any HTML errors in your web pages.
Some browsers may be less tolerant towards errors than others and a web page whose code validates correctly will be displayed with greater consistency and predicability across different browsers.
You can check your code with the W3C Markup Validation Service (and then fix any errors reported).
https://validator.w3.org/

Thank you very much for the additional information.
It's definitely very odd that the problem has only been seen in your own galleries in Mobile Safari on your own iPad.

The difference may be because I am using my index.html file to host a great many links to individual Galleries?

This should really not make any difference at all (and I can't actually see how it could make a difference).
However, as you are already aware, until we know what is causing the problem, we can't rule anything out.

I use iPower to host my Site and I am fairly sure that they don’t do anything strange which might affect the way that their Server delivers content to the Internet.

I agree. I do not think that your server is part of the problem. A Juicebox gallery really does not have much in the way of server requirements. A Juicebox gallery is basically just a collection of HTML, CSS and JavaScript files with a few other resource files (font and image files) and pretty much any regular web server should be able to handle this. (Only the Download Button and Password Protection require further requirements: PHP 5.2.0 or later.)

The icons in a Juicebox gallery are characters in a custom font. If there was a problem with the font files, then I'd expect all the icons (not just the Back Button) to be showing up as an 'X'.
As I was never able to see the problem for myself (even on my own iPad) and as the Back Button displays correctly when centered, I think we can definitely rule out corrupt font files as a possible cause.

I would still like to see the problem for myself (even if I can't experience it) so, if possible, please post a screenshot of the mysterious 'X'.

Maybe it's a really rare bug which just manifests itself in one particular browser on one particular device under a certain combination of gallery configuration options. It seems unlikely but not impossible.

I have uploaded a test gallery using exactly the same configuration options that you do (and the same version of Juicebox). I've copied the configuration options from your Hummingbirds gallery which still has the Back Button to the left. The only thing I've changed are the images so you'll not see an image on the Splash Page but the Back Button should display correctly and redirect to your site index.
Please take a look at this gallery and let me know if you see the Back Button or an 'X'. Thank you. (I'll take the gallery down after you've seen it.)

[Test gallery removed.]

I presume the problem occurs with the Back Button in all your galleries (even though they all use their own individual 'jbcore' folders).

Out of curiosity, does the problem also occur with the Back Button in this demo gallery on our own website?
https://juicebox.net/demos/pro/full/

I guess one possible solution might be to backup all your apps and personal data and perform a clean install of iOS 14.6 (and then restore your data afterwards). That should fix the problem but it's a pretty drastic measure to take and I can't even guarantee that it would work. I'd be hesitant to do this myself.

It's certainly an odd problem and one which I can't quite wrap my head around (let alone reproduce).
If I think of anything which might help, I'll be sure to post back here.

Are there any other Caches which I should clear?

If you have not yet done both of the following, then please try:

(1) Settings -> Safari -> Clear History And Website Data

(2) Settings -> Safari -> Advanced -> Website Data -> Remove All Website Data

If that fails, would changing the Config HTML for the Galleries to:

Unfortunately, there's not much else I can suggest. The code for your gallery looks fine and I cannot reproduce the problem on 3 separate Apple devices running 3 different versions of iOS (iPhone 5S iOS 12.5.4, iPad 2 iOS 10.3.3, iPhone 7 iOS 14.6).
The problem seems to be unique to your own iPad (rather than with the code for the gallery). If there was a problem with the code (or gallery settings), then I should be able to see the problem on my own devices.

You could certainly try changing the Back Button's position in your gallery's settings to see if this makes a difference.
Try setting backButtonHAlign="CENTER".
By doing this, you will at least be able to tell at a glance if your gallery's current 'config.xml' file is being used or if an older cached version is still in use. This might help to determine whether or not the cache has been completely cleared.

Also, maybe you could try viewing your gallery in a different browser (at least for testing and troubleshooting purposes).
Do you still see the broken Back Button if you view your gallery in Mobile Chrome?

Perhaps you could post a screenshot of the gallery on your iPad so that I can see what you are seeing.
I'm not sure that this will help but maybe I'm missing something that will become obvious when I see it.
Thanks!

I've just checked your Song Birds of Costa Rica gallery (the same one shown in your screenshot) in Mobile Safari on an iPad 2 running iOS 10.3.3 and the Back Button displays and functions correctly (see screenshot below).

I've also checked on an iPhone 7 running iOS 14.6 and the Back Button displays and functions correctly there, too.

I'm not sure what the problem is but the gallery files on your web server seem to be fine and everything seems to be working as expected on the devices I have tested on.

Try completely clearing your browser's cache before loading your website to see if this clears the problem.

338

(4 replies, posted in Juicebox-Pro Support)

@byuen

Please feel free to post in the Feature Requests thread, too! (Ideas may be overlooked in regular support threads.)
Thanks!

339

(5 replies, posted in Juicebox-Pro Support)

@byuen

Derek is a member of Fotomoto staff and only pops in here from time to time.
If you like, you could direct your queries directly to Fotomoto via their online Contact Customer Support page.
Fotomoto Contact Customer Support: https://support.fotomoto.com/s/contactsupport

I hope this points you in the right direction.

That's odd.
I've just created a test gallery on my own Windows 10 PC (using JuiceboxBuiler-Pro v1.5.1) with 'Large Images' selected (at the default size of 2048 x 1536) using source images of 2048 x 1536 and, as they are already within the maximum images bounds, they are copied across to the 'large' folder as expected.
I've also tried with images both smaller and larger than the maximum image bounds and everything seems to work as it should (at least for myself in my own tests).

Unfortunately, I'm not sure what might be causing your problem. It's not a known issue and not something that I remember anyone reporting before (and I cannot replicate the problem myself).

The only thing I can think of that might be causing the problem is if you maybe have the 'large' folder open in another program (perhaps to inspect the images) and the other program has a temporary lock on the folder preventing JuiceboxBuilder-Pro access to it.
Try running JuiceboxBuilder-Pro with no other programs active (other than the usual system processes) and make sure that you save your gallery to a new empty folder.

If this does not help, then a fresh install would certainly be the next thing to try.
Please try the complete uninstall/reinstall procedure noted as #11 in this forum thread.

If this does not help, then perhaps you could provide some of your source images (maybe upload them in a zip file to a file sharing service such as Dropbox or Google Drive) so that I can try to replicate the problem using the same files that you use.
If you don't want to make your images publicly accessible, then just let me know and I'll email you and you can send me a download link privately.
Also, if you could let me know exactly what settings you use in the JuiceboxBuilder-Pro interface, then I'll hopefully have a better chance of reproducing your problem. (A screenshot or two might be the easiest way to let me see your settings.)

Please let me know how you get on.
Thank you.

341

(1 replies, posted in Juicebox-Pro Support)

Can I simply use WP-Juicebox for WordPress to do my homework online?

I'm not sure what you mean by this. Maybe if you explain what your homework is, I might be able to help further.

And is there an example how to embed a gallery?

Instructions on how to use WP-Juicebox can be found on the plugin's support page here.

Also (after creating a Juicebox gallery): where can upload my gallery folder to?

If you use WP-Juicebox to create a gallery, WP-Juicebox also handles the embedding of the gallery (there is no gallery folder for you to worry about).
If, however, you create a gallery on your computer with JuiceboxBuilder-Pro, then you can upload the complete gallery folder to your web server and embed the gallery using the baseUrl method of embedding documented here.
Use a 'Custom HTML' Gutenberg block (in the 'Formatting' section) to paste your baseUrl embedding code.
It does not matter where on your web server you upload your gallery folder to as long as the two paths in the baseUrl (the path to the 'juicebox.js' file and the baseUrl itself, pointing towards the gallery folder) are correct.

342

(6 replies, posted in Juicebox-Lite Support)

Harman have now published the AIR v33.1.1.502 runtime for Windows, which fixes the problems found in v33.1.1.444, on their regular download page: https://airsdk.harman.com/runtime

When installing JuiceboxBuilder under v33.1.1.502, an 'unknown publisher' warning will be displayed. Please just click through this warning. This is a known issue, noted on the AIR runtime download page (link above), which Harman still have to address.
This has no adverse effect on JuiceboxBuilder, though, which will run with full functionality under v33.1.1.502.

Harman have now published the AIR v33.1.1.502 runtime for Windows, which fixes the problems found in v33.1.1.444, on their regular download page: https://airsdk.harman.com/runtime

When installing JuiceboxBuilder under v33.1.1.502, an 'unknown publisher' warning will be displayed. Please just click through this warning. This is a known issue, noted on the AIR runtime download page (link above), which Harman still have to address.
This has no adverse effect on JuiceboxBuilder, though, which will run with full functionality under v33.1.1.502.

344

(1 replies, posted in Juicebox-Pro Support)

Hi.

Please check your links. I cannot access your website with any of the links you provided. It looks like you might have edited your post and may have copied and pasted the last two links (as they show the text for the links that would be displayed in the forum rather than the actual links themselves).

With regard to playAudioOnLoad, due to recent browser restrictions, it is unfortunately no longer possible to automatically start the audio playing as soon as the gallery loads in all browsers.
Many browsers are blocking the automatic playing of audio (and video) by default and users now need to initiate the playing of audio (and video) files themselves.

In my own tests (on a Windows 10 PC), I find that playAudioOnLoad currently works only in Edge (Chromium) and Opera (but not in Chrome or Firefox).

As unfortunate as it is, there is nothing that can be done from within Juicebox-Pro to force audio to autoplay in browsers which feature these audio/video restrictions.
Users will likely have the option of changing their browser's settings (depending on the browser) to allow autoplay of audio (and video) but this is something that the user must do. (A user's browser settings cannot be changed from within a Juicebox-Pro gallery.)

However, as long as you display the Audio Button on your gallery's Button Bar (by setting showAudioButton="TRUE"), then users can start the audio track themselves by clicking the button.

Once your links are working, I'll take a look at your galleries and see if I can figure out your other issues.
Also, please let me know what version of Internet Explorer you are testing on.
Thank you.

345

(6 replies, posted in Juicebox-Lite Support)

Further Update:

Harman's link to AIR v33.1.1.502 has now expired, too.

I have asked Harman if they would be willing to re-upload a link to v33.1.1.385 (the last official working AIR runtime for Windows) but, until such a link is available, please download v33.1.1.385 from FileCroco using the following link:
https://www.filecroco.com/download-adobe-air/

The file from FileCroco is the official Harman release of AIR v33.1.1.385 (genuine, clean and safe to use).
I found the SHA256 hash for the 'AdobeAIR.exe' v33.1.1.385 file on a Harman web page archived by archive.org (search for "https://airsdk.harman.com/runtime" and select the page dated 26 January 2021) and it matches the SHA256 hash of the file from FileCroco.

Filename: AdobeAIR.exe
Filesize: 7,689,512 bytes
SHA256: d5c8659a712145cc19b4e23ff0c731c87fefc5c100d98c963a2689c5fd97a96c

Apologies, once again, for the inconvenience.
I hope it won't be too long before Adobe AIR is back on track as Harman certainly seem to have fixed the original problem with v33.1.1.502.

Further Update:

Harman's link to AIR v33.1.1.502 has now expired, too.

I have asked Harman if they would be willing to re-upload a link to v33.1.1.385 (the last official working AIR runtime for Windows) but, until such a link is available, please download v33.1.1.385 from FileCroco using the following link:
https://www.filecroco.com/download-adobe-air/

The file from FileCroco is the official Harman release of AIR v33.1.1.385 (genuine, clean and safe to use).
I found the SHA256 hash for the 'AdobeAIR.exe' v33.1.1.385 file on a Harman web page archived by archive.org (search for "https://airsdk.harman.com/runtime" and select the page dated 26 January 2021) and it matches the SHA256 hash of the file from FileCroco.

Filename: AdobeAIR.exe
Filesize: 7,689,512 bytes
SHA256: d5c8659a712145cc19b4e23ff0c731c87fefc5c100d98c963a2689c5fd97a96c

Apologies, once again, for the inconvenience.
I hope it won't be too long before Adobe AIR is back on track as Harman certainly seem to have fixed the original problem with v33.1.1.502.

347

(6 replies, posted in Juicebox-Lite Support)

Update:

Harman's link to AIR v33.1.1.385 has expired.

Until Haman publish a fixed version of AIR on their public download page, please use v33.1.1.502 from this page:
https://transfer.harman.com/message/yAj … vio19j765S

I have tested v33.1.1.502 myself and it works well (just like v33.1.1.385 did).

Update:

Harman's link to AIR v33.1.1.385 has expired.

Until Haman publish a fixed version of AIR on their public download page, please use v33.1.1.502 from this page:
https://transfer.harman.com/message/yAj … vio19j765S

I have tested v33.1.1.502 myself and it works well (just like v33.1.1.385 did).

349

(5 replies, posted in Juicebox-Pro Support)

v1.5.1.3 was the key.

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

Stephen, you can mark this SOLVED!

Will do!

350

(5 replies, posted in Juicebox-Pro Support)

You can download the latest version of WP-Juicebox (v1.5.1.3) from its own support page here.
Upgrading should fix your problem. The first bugfix listed on the Version History page for v1.5.1.3 is:

  • Fixed bug whereby 'Add Juicebox Gallery' button did not display for Gutenberg editor in WordPress 5.6