You should be able to use a relative path for assets like a Splash Page image or an audio track.
If you just use the regular gallery structure and embedding code (nothing fancy), then you should be able to just upload the file in question to the gallery folder (alongside the 'index.html' and 'config.xml' files) and then just use the filename as the path, e.g.:

splashImageUrl="IMG_9999.jpg"

... or:

audioUrlMp3="track-01.mp3"

Take care with case sensitivity (uppercase vs lowercase), especially with filename extensions as, on a web server, 'abcdef.jpg' is not the same as 'abcdef.JPG'.

If you continue to experience difficulties, please upload the gallery (if possible) and post a link so that I can see the problem for myself. (Or perhaps zip the gallery folder, upload it somewhere and send me a download link.)
Once I'm able to see the problem for myself, I should be able to determine the exact cause of the problem and propose a solution.
Thank you.

Thank you for the update. I'm glad you've finally got JuiceboxBuilder-Pro working but I'm sorry to hear of the hassle you had to go through.

Just for the record, since the release of Juicebox-Pro, I've used JuiceboxBuilder-Pro with every iteration of Windows without issue and I've never signed into Windows with a Microsoft account. I've always (even now, on Windows 11) used a local account and I never even bothered with a password until Microsoft enforced it. I never encountered the KERNELBASE issue (although, admittedly, all my local accounts were admin accounts).

Anyway, I'm glad you've got it working. Thank you for letting me know.

Thank you for the update and additional information.

That is, indeed, very strange.

Here are two things you could try:

#1
With the odd resolution to the problem in the forum thread I linked to, you could maybe try the following:
(1) Install Harman AIR v33.1.1.744
(2) Install JuiceboxBuilder-Pro
(3) Uninstall Harman AIR v33.1.1.744
(4) Install Adobe AIR v32.0.0.125

You'll not be able to install JuiceboxBuilder-Pro under Adobe AIR v32.0.0.125 any more but JuiceboxBuilder-Pro should run under Adobe AIR v32.0.0.125 if it's already installed.

I have no idea if this will work but it shouldn't take long to try and if something similar worked for a different user (albeit with a different version of the 'KERNELBASE.dll' file, an upgrade of AIR rather than a downgrade and it was years ago). Upgrading AIR would be tricky (what with the lack of an AIR archive download page to find different versions to try) but maybe my suggestion is worth a shot.
I've uploaded Adobe AIR v32.0.0.125 here if you want to give it a try (it's the only Adobe version of the AIR runtime I have): [Link removed.]

#2
Create a new admin user profile on your computer and then try installing Harman AIR v33.1.1.744 and JuiceboxBuilder-Pro under the new user account in case a corrupt user profile is somehow part of the problem.

I hope this helps.
Please let me know how you get on. Thanks.

At the moment, your gallery looks good in both portrait and landscape orientations in Mobile Safari on my iPhone and in Mobile Chrome on an Android device.
If things look a little odd, then try clearing your browser's cache before reloading your gallery's web page to see if this helps to resolve the problem.

It's usually a good idea to set screenMode="AUTO" (the default value) and allow Juicebox to determine whether to display the gallery in Large Screen Mode or Small Screen Mode (depending on the device being used to view the gallery).

In Small Screen Mode (whether you are in Fullscreen Mode or not), you can display the Thumbnail Button on the gallery's Button Bar (to allow the visitor to view the thumbnail pages) by setting showSmallThumbsButton="TRUE" (in JuiceboxBuilder-Pro's 'Customize -> Thumbnails' section).
You will need to display the Button Bar in your gallery, though, in order for the Thumbnail Button to be displayed (and your gallery currently hides the Button Bar by setting buttonBarPosition="NONE").

Your first image's caption is currently the following:

</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

You could change it to this to be HTML 5 compliant:

<p><span style="color: #cccccc;">Projet: Pecquencourt - Production: </span><a href="https://mw-architecture.fr/" style="color: #0066ff;">MW Architecture</a><span style="color: #cccccc;"> - Date: Novembre 2022 </span><br><a href="http://www.vincefx.com" style="color:#0066ff;">www.vincefx.com</a><spa style="color: #cccccc"> vincefx@free.fr tel:06.98.72.06.93</span></p>

This is HTML 5 compliant but it might not make a visible difference. Most browsers will likely still render the <font> tag OK and may be quite tolerant towards things like missing end tags.
If you don't see a visible difference, then you might not want to bother changing all your captions just now (as it is quite a large task) but it would be a good idea going forward (especially as your web page uses the HTML 5 Doctype Declaration).

Yes. The embedding page is your 'ImagesArchi.html' file.

I never actually saw two galleries on the page but there were two sets of embedding code (both embedding the same gallery into the same container).
Your web page only has one set of embedding code now, so that's good.

It's certainly strange that nothing show up in search results, especially if Google claims to have indexed the gallery.
Unfortunately, only Google really knows how their indexing and searching algorithms work.

Your gallery's SEO code is in place and looks fine so I don't think there's anything you can do there that would improve matters.
Perhaps the best thing you can do is ask Google to recrawl your site: https://developers.google.com/search/do … to-recrawl

However, as Google says:

With regard to the image in our own gallery labelled 'Next Step', it might not be showing up in search results due to the two words being very short and generic (and not being very descriptive). It's just a hunch, though.

Hopefully asking for a recrawl will help with your situation.

Thank you for your notes and help in tracking this down.

In order to fix this within WP-Juicebox, I'd need to fetch the corresponding thumbnail URL for each individual image rather than hardcoding "thumbs_" as a prefix for each thumbnail (which NextGen Gallery always used to do until v3.21) and then appending the image filename.
This sounds simple enough until I discovered that there is no thumbnail-related entry in the individual NextGEN image properties.

I could fetch the global value for NextGEN's "Use dashes instead of underscores when generating new image files" switch but I would just have to apply this to all images in all galleries and it would break all thumbnails created if/when the switch was in one position or the other (just like the current status when using dashes). As far as I can tell, there's no way to programmatically determine which galleries were created with the switch in any particular position. In fact, it's entirely possible that a single gallery could have thumbnails with both underscores and dashes (for example, if you were to upload a few images to a gallery with the switch set to 'Underscores' and then upload a few more images afterwards with the switch set to 'Dashes'). I'd really need to determine the corresponding thumbnail URL for each individual image and this does not seem to be possible.

I think all I can do is either:
(1) Feed WP-Juicebox the full-sized NextGEN images to be used as the Juicebox gallery's thumbnails and have Juicebox dynamically resize them when the gallery is viewed.
... or:
(2) Give the WP-Juicebox user the option to set the NextGen separator to either 'Underscore' or 'Dash' on a per gallery basis (in each WP-Juicebox gallery settings window) and trust that the NextGen user does not have a gallery which uses both. At least this will use the dedicated NextGEN thumbnails as the Juicebox thumbnails.

I'll think it over for the next version of WP-Juicebox.
In the meantime, I'm glad that you've found the cause of your problem and found a suitable workaround.
Thanks, again, for taking the time to document this issue. It's most appreciated.

That's odd. I've just created a gallery using WordPress v6.1.1, WP-Juicebox v1.5.1.4 and NextGEN Galery v3.35 (a WP-Juicebox gallery using a NextGEN gallery as the source of images) and both the main images and thumbnails appear as expected.

Being that I'm not able to reproduce the error, could you please post a link to your dysfunctional gallery's web page so that I can investigate and hopefully help further? Thank you.

No worries!

@petax

Thanks for sharing your solution.
This method does require Showkase but for Showkase users, it's great!

Thank you for purchasing Juicebox-Pro.
I'm sorry to hear that you are having difficulty with JuiceboxBuilder-Pro, though.

Please take a look at this forum post entitled "Unresponsive New Gallery and Open Gallery buttons in JuiceboxBuilder": https://juicebox.net/forum/viewtopic.php?id=5295
It should hopefully help to resolve your problem.

I hope this helps but, if you continue to experience difficulties, then please post back to let me know what you've already tried from the forum post suggestions and I'll do my best to help further.
Thank you.

First of all, I should probably clear up some of the terminology.
The Juicebox Plugin for Lightroom is actually a web engine and not a plugin as Lightroom defines a plugin.
As such, the Juicebox Plugin for Lightroom cannot be installed as a Lightroom Plugin but should, instead, be installed as a Lightroom Web Engine.
Sorry for any confusion this causes.

You should be able to install the Juicebox Plugin for Lightroom by simply double clicking the 'juicebox_pro.lrwebengine' package inside the 'adobe-lightroom-plugin' folder (from the extracted Juicebox-Pro zip file), as noted in the installation instructions here.

If this does not work, then the manual instructions in the link above should definitely work.

That's not unusual. The automated method of installing should create a Web Galleries folder for you but if you install using the manual method, then you'll need to create a 'Web Galleries' folder yourself and then copy the 'juicebox_pro.lrwebengine' package inside it.

On a Mac, navigate inside the Users/username/Library/Application Support/Adobe/Lightroom/ folder and create a new folder there named 'Web Galleries'. Then copy the 'juicebox_pro.lrwebengine' package inside the 'Web Galleries' folder.

You should now be able to access the Juicebox Plugin for Lightroom from the Lightroom Web module (click the 'Web' module shortcut/link near the top right of the Lightroom window or go to 'Window -> Web' from the drop down menu at the top).

I hope this helps.

I'm sorry to hear that there's been no easy fix for you to reinstate all your galleries.
I'm really not sure what could have wiped out what appears to be your entire 'wp-content' folder.
I hope that rebuilding your galleries doesn't take as long as you think it might.
Best wishes, and I'm sorry that I couldn't be more of a help.