Unfortunately, Harman, the current developers of AIR, have recently removed support for WebKit (the embedded browser which JuiceboxBuilder uses for the live gallery preview on the Customize panel) from the AIR runtime package.
The symptoms you describe in your quote above (content from the Customize tab obscuring content on the Publish tab) are a result of using the very latest version of AIR (v50.2.1.1) which does not include WebKit support.

The solution is to use the most recent version of AIR with WebKit support. This is currently AIR v33.1.1.744.
Harman have made this available at the foot of their AIR runtime download page: https://airsdk.harman.com/runtime
Here are direct links to AIR v33.1.1.744 (I include the Windows link for any PC users reading this thread and encountering similar issues):
Mac: https://airsdk.harman.com/assets/downlo … obeAIR.dmg
Windows: https://airsdk.harman.com/assets/downlo … obeAIR.exe

Please be sure to uninstall AIR v50.2.1.1 first before installing AIR v33.1.1.744.

Incidentally, I have noted this in sticky posts at the top of both the JuiceboxBulder-Pro and JuiceboxBuilder-Lite forums:
JuiceboxBuilder-Pro: https://juicebox.net/forum/viewtopic.php?id=5318
JuiceboxBuilder-Lite: https://juicebox.net/forum/viewtopic.php?id=5319

According to this comment (over in the Harman Github Issues pages), it looks like Harman are currently looking to replace WebKit with a new embedded browser: https://github.com/airsdk/Adobe-Runtime … 1216482803

If/when Harman implements this, there will no longer be a need to use AIR v33.1.1.744, although there is no problem in sticking with AIR v33.1.1.744 as JuiceboxBuilder actually requires only AIR v2.0 or later to function fully.

Unfortunately, I'm really not sure what might be triggering these warnings. We've not had reports of similar warnings from any other users.
Using AIR v33.1.1.744 should hopefully resolve your problem, though.

Please let me know how you get on and if I can be of any further assistance.
Thank you.

As I'm sure you're aware, there is no actual limit to the number of galleries you can have on a site (or a page) but finite resources in a real world scenario could prove to be a restrictive factor.

Unfortunately, every server is different (with different limits) and each user's galleries are different (with different numbers of images at different filesizes) so it's really difficult to give you a number as to how many galleries is too many.

Having said that, if you only have one gallery per page, then there really shouldn't be a problem at all.
The browser will just be parsing one page at a time (as and when they are viewed) and, thus, only one gallery will be consuming resources at any one time. Galleries on other pages should have no bearing on this problem.
As far as I can see, a problem regarding gallery numbers would only occur if you were displaying multiple galleries on a single page, (i.e. multiple galleries were all being loaded at the same time and many images would be preloaded at once).

Do you maybe have any plugins which preload web pages throughout your site before they are viewed (maybe preloading pages which are linked to from any particular page)? This could potentially cause a large server load (loading a lot of gallery pages in the background).

I notice that you already use imagePreloading="NEXT" in your galleries, preloading just the next image rather than all the images on the current thumbnail page (PAGE) or all the images in the gallery (ALL), so that's good. There's no need to change that.

There's really no other gallery confirmation options you could change that would help with such a problem.
Storing your images locally (instead of using Flickr) might make a difference but I realise that it would be a mammoth task to switch over to this method of image storage (and, to be honest, I really don't know if it would help... it's just something you could theoretically try).

Check your plugins, though. There's may be something there that's contributing to the problem.
As I mentioned above, if you only have one Juicebox gallery per page, then there really shouldn't be a problem (at least where Juicebox galleries are concerned).

That's odd... I've just uploaded some images to a completely empty Flickr account, created an album/set (using just a couple of the uploaded images) and used the album/set id (grabbed from the URL) as the Flickr Set Id in JuiceboxBuilder-Pro. The album/set displayed as expected.

The only thing to note is that it took a good 5 or 6 minutes after uploading the images before they actually appeared in my Photostream but everything worked fine without a hitch.

The functionality certainly seems to be working OK (art least for me) but there are a couple of things you can do to try to troubleshoot your problem.

The first thing to do is to make sure that your images are public (and not private).

The next thing to do is to head on over to Flickr's own API Explorer (link below), enter your album/set id into the 'photoset_id' box (the second one down) and click the 'Call Method...' button.
There should be one <photo> tag for each and every image in your album/set shown in the output box.
If there are no images found, then there's definitely something wrong with your album/set at Flickr's end (if Flickr cannot find your images using the album/set id, then JuiceboxBuilder-Pro will not be able to do so either) and you might need to contact Flickr's own support team to figure out what's wrong.

Flickr API Explorer - flickr.photosets.getPhotos: https://www.flickr.com/services/api/exp … .getPhotos

I hope my notes above at least reassure you that the functionality should still be working OK (as it does for myself) and point you in the right direction.
If you continue to experience difficulties, then please let me know and I'll try to help further. (Are your images super-small or super-large? Maybe their size (in both filesize and/or resolution) has something to do with this? Perhaps you could try again with different images to see if this makes a difference.)

@tbs04

I'm sorry to hear that you're experience difficulties with JuiceboxBuilder.
However, to avoid cross-posting, I'll try to help you out in the other thread you created here: https://juicebox.net/forum/viewtopic.php?id=5383
Thanks.

It's most likely a caching issue (your browser is maybe still using an older version of your gallery's 'config.xml' file prior to the change to backButtonText having been made).

try completely clearing your browser's cache before reloading your web page to see if this resolves the problem.
Otherwise, try viewing your web page in a different browser (one that has never been used to view the web page before) to see if the backButtonText is as expected.

If the problem persists, then perhaps your web server has some server-side caching enabled which is still serving the older 'config.xml' files prior to you uploading the new version. If this is the case, then please contact your web host and ask if they can disable server-side caching on your hosting account.

I hope this helps (as your configuration looks OK).
However, if you continue to experience difficulties, then please post back with the URL to your web page so that I can see the problem for myself live.
Once I'm able to see the problem live on your web server, I should hopefully be able to determine the exact cause of the problem and propose a solution.
Thank you.

You're welcome.

I feel your pain. Sometimes re-installing Windows is the less arduous option.

Yes. Unfortunately, the preview is not 100% perfect, as noted in the Known Issues section of the JuiceboxBuilder User Guide.

Thanks for the updates. I'm glad you're making progress!

Your gallery's Button Bar displays OK in my own desktop browsers and on my Android phone.
If you don't see the Button Bar yourself, then try clearing your browser cache before reloading your gallery's web page to ensure that the browser is loading the gallery's 'confg.xml' file fresh from your web server (with the new setting for buttonBarPosition) instead of using an older, cached version.

Incidentally, on mobile in portrait orientation, there's not much room for the Button Bar (due to the length of the Gallery Title) so the Button Bar spills over onto several lines. Try shortening the Gallery Title.
Also, in Small Screen Mode (on mobile devices), please note that the Button Bar is displayed only on main image pages and not on thumbnail pages.

@ioannis.stavrou

The audioUrlMp3 path must lead to an actual MP3 file (yours currently leads to a web page into which an audio file has been embedded).
Point your autioUrlMp3 directly to an MP3 file (just upload an MP3 file to your web server and use its absolute path) and all should be well.

I'm sorry to hear that you're having trouble with JuiceboxBuilder-Pro on your Windows 10 machine.
Thank you for the report, though.

Unfortunately, I do not currently have access to a Windows 10 machine to test on.
Searching through the forum, I found a similar issue (regarding a different version of the 'KERNELBASE.dll' file back in 2019) here: https://juicebox.net/forum/viewtopic.php?id=4814
An odd solution was found (to install an older version of Adobe AIR and then upgrade) which might be difficult to do now as older versions of AIR are no longer easily available online (and the current version of JuiceboxBuilder-Pro will no longer install under the last version of Adobe's AIR (v32)).
I thought I should link to the thread though, in case it somehow helps or points you in the right direction.

Incidentally, you are the first (and only) person to have reported this. That's not to say that it's not going to be a widespread problem on Windows 10 (as it certainly seems to be related to the most recent Windows update) but I thought you'd like to know that we've not received any other similar reports yet.

Also, I should note that, similar to your own results, JuiceboxBuilder-Pro v1.5.1.2 still runs fine on my Windows 11 machine (OS Build 22621.1555) under AIR v33.1.1.744.

What you are describing is the Splash Page.
The Splash Page is an image placeholder for the gallery which, when clicked, will expand the gallery to fill the browser viewport (to give the gallery as much room as possible).
By default, the Splash Page will be displayed on mobile devices when a gallery is embedded in a web page alongside other content (where the gallery might be too small to use).
Check out the Gallery Tour where there is a short section about the Splash Page.

Please check out the Splash Page configuration options here.

By default, Juicebox uses the first image in the gallery as the Splash Page image. You can change this if you like via the splashImageUrl option (in JuiceboxBuilder-Pro's 'Customize -> Splash Page' section).
You could also choose to not use the Splash Page at all by setting showSplashPage="NEVER".

Whether you use the Splash Page or not, on a mobile device, the gallery will be displayed in Small Screen Mode (check out the Gallery Tour link above for details) where thumbnails and main images are displayed on separate pages (to give the main images more room).
If you'd rather have the gallery displayed in Large Screen Mode (where thumbnails are displayed alongside the main images) on all devices and in all browsers, then you can set screenMode="LARGE" (in JuiceboxBuilder-Pro's 'Customize -> General' section).

Your gallery currently sets maxCaptionHeight="70".
Try increasing the maxCaptionHeight (at least to the default value of 120) to give your captions more room. You'll find maxCaptionHeight in JuiceboxBuilder-Pro's 'Customize -> Caption' section.

Also, your gallery's first caption is:

<caption><![CDATA[</font><font color="#CCCCCC">Projet: Pecquencourt - Production: <font color="#0066FF"><a href="https://mw-architecture.fr/">MW Architecture </a><font color="#CCCCCC"> - Date: Novembre 2022  </font><br><font color="#0066FF"><a href="http://www.vincefx.com">www.vincefx.com </a><font color="#CCCCCC"> vincefx@free.fr tel:06.98.72.06.93]]></caption>

For a valid HTML 5 page, I'd recommend changing <font> tags for equivalent <style> tags as noted here (a little bit of work would be required but the resulting code would be HTML 5 compliant). Also, there's no need to start the caption with a closing </font> tag and you're missing a few </font> tags throughout your caption text.

Your gallery's embedding page actually has two galleries embedded into it (two lots of embedding code with with same 'juicebox-container' id).
I expect that you're just trying to embed one gallery so you should be able to remove one set of embedding code.
If you are trying to embed multiple galleries into a single web page, then you only need to load the 'juicebox.js' JavaScript file once per page (not once per gallery) and each gallery should be loaded into a <div> with a unique id.

I hope my notes above point you in the right direction.