No problem! I'm glad you've been able to resolve your problem.

For others experiencing similar issues, instructions for resolving local viewing issues can be found in this FAQ:
When I view my gallery locally, I see the message "Juicebox can not display locally in this browser". Why?

... and in this forum post (stickied at the top of thein the 'Tips and Tricks' section).

(1) Juicebox-Pro has only one text color setting (textColor) which is used for all gallery text.
However, you could set a textColor for your gallery and then override the color for your Gallery Title by using CSS (in the album's 'index.html' page), e.g.:

/* GALLERY TITLE - LARGE SCREEN MODE & SMALL SCREEN MODE */
.jb-area-large-mode-title, .jb-idx-ssm-title-wrapper {
    color: #ff0000 !important;
}

textColor can be found in JuiceboxBuilder-Pro's 'Customize -> Lite' section (and should be entered in the Juicebox skin's 'Pro Options' text area).

For reference, a full list of all Juicebox-Pro configuration options can be found here.

(2) The position of the image's caption text is determined by the Pro configuration option captionPosition.
Possible values for captionPosition are OVERLAY, OVERLAY_IMAGE, BELOW_IMAGE, BOTTOM, BELOW_THUMBS and NONE. A short description of each of these values can be found in the Caption Options section of the Config Options page.
The only way to have the caption text displayed to the left or right of the image would be to set thumbsPosition to either LEFT or RIGHT and then set captionPosition to BELOW_THUMBS, like in this demo here.

I'm glad you've been able to answer your own question. Thanks for posting back to let me know.

I realise that, in theory, JuiceboxBuilder could be tweaked to allow certain non-web-safe characters but then you might encounter issues further down the road (for example, when the images are uploaded to a web server).

It really is best to stick with web-safe characters for image filenames when the images are intended for the web.
JuiceboxBuilder works with all web-safe characters and you shouldn't have any trouble with the image filenames in any program or on any web server.

Please try running JuiceboxBuilder-Pro with Rosetta.

Check out this forum thread for details: https://juicebox.net/forum/viewtopic.php?id=5289

Also, it's noted as a Known Issue on the Adobe AIR download page: https://airsdk.harman.com/runtime

This should hopefully resolve your problem.

@tonygamble

I'm glad you found the fix you were looking for!

Thanks for the update! I'm glad it's working.

Thanks for the update. At least you've found the root of the problem.
I see their documentation regarding this here:
Understand Managed WordPress security: https://godaddy.com/help/understand-man … rity-40956

I hope GoDaddy is willing and able to relax this security measure for your wp-content/plugins/wp-juicebox directory as it breaks the functionality of WP-Juicebox.

It sounds like this applies only to their Managed WordPress platform and not to a regular WordPress site hosted on their web server.
Maybe you could download and install WordPress on your web space yourself and then migrate your Managed WordPress site to the regular WordPress site following GoDaddy's own instructions here:
Move a Managed WordPress site to an unmanaged WordPress account: https://godaddy.com/help/move-a-managed … ount-19798

Otherwise, you could manually embed your Juicebox galleries into your WordPress posts using the baseUrl method of embedding documented here.
Here's an example:

Step #1
Create a gallery with JuiceboxBuilder-Pro (on your computer) and save it to a new empty folder named "my_gallery_folder".

Step#2
Upload the entire gallery folder (not just the contents) to the root directory of your web space (using an FTP program such as Filezilla: https://filezilla-project.org/.)
The root directory will likely be named something like 'public_html' or 'htdocs' (depending on your web server).

Step #3
Create a new 'Custom HTML' Gutenberg block in your WordPress post.
Click the '+' symbol in your WordPress post to create a new Gutenberg block. Scroll down to the 'Formatting' section and select the 'Custom HTML' block type.
Now paste the following embedding code into the 'Custom HTML' block.

<!--START JUICEBOX EMBED-->
<script src="/my_gallery_folder/jbcore/juicebox.js"></script>
<script>
    new juicebox({
        baseUrl: "/my_gallery_folder/",
        containerId: "juicebox-container",
        galleryWidth: "100%",
        galleryHeight: "600",
        backgroundColor: "#222222"
    });
</script>
<div id="juicebox-container"></div>
<!--END JUICEBOX EMBED-->

The leading slashes in the paths above denote your root directory so the code above will work without modification as long as your gallery folder is named "my_gallery_folder" and has been uploaded to your root directory.

You can, of course, name your gallery folder anything you like but you'll need to make sure that the correct gallery folder name is used in the two paths within the embedding code.
Also, you can upload your gallery folder to anywhere on your web server as long as the two paths within the embedding code (the path to the 'juicebox.js' file and the baseUrl entry itself, pointing towards the gallery folder) are correct.
I just used "my_gallery_folder" as the gallery folder name for this example and suggest that you upload the gallery folder to your root directory for convenience.

That's all you need to do to embed a Juicebox-Pro gallery into a WordPress post and you can replicate this process as many times as you like.
Of course, for subsequent galleries, you'll need to change the name of the gallery folder (so that each gallery folder has a unique name) and change the two instances of the folder name in the embedding code, but that's all.

I hope this helps.

@pholtzman

When I try to view your gallery's configuration file (dynamically generated by the 'config.php' file inside the 'wp-juicebox' folder), I should be able to see the XML data but, instead, I see just the following message:

If a browser is unable to see the data directly, then Juicebox will be unable to do so also, resulting in the "Config file not found." error that you reported.

In fact, I can't even view the 'readme.txt' file inside the plugin's directory, either. Again, I see an error 403 (forbidden).

Please check the permissions on the files directly inside your /wp-content/plugins/wp-juicebox/ directory.
Default file permissions of 644 should be fine. (You should be able to check and change file permissions either through your hosting account's online file manager or by using a dedicated FTP program such as Filezilla).

Also, please check your web server's security settings (perhaps via your hosting account's online control panel or a '.htaccess' file) to see if there is anything that might be blocking direct access to PHP and TXT files.

If you can't find the root of the problem, just ask your web host why the following URL results in a 'forbidden' error rather than displaying the text and they should be able to help you out further.

http://downtowngroup.com/wp-content/plugins/wp-juicebox/readme.txt

The new fix is also documented in this FAQ.

Thanks! I hope they can resolve the issues very soon.

I'm sorry to hear that you are still having such problems.
I swapped the AIR framework files on my Windows system (C:\Program Files (x86)\Common Files\Adobe AIR) with the new runtime files from the updated Harman AIR SDK with no problems or adverse effects at all, hence my suggestion for you to try it on your Mac. (I experienced no problems adding multiple images, no speed degradation populating the 'Images' tab, no problem opening existing galleries and no problems with the 'Save Gallery Folder As' dialog window.)

Until the new runtime is released, you might like to just revert to the current AIR runtime (v33.11.533) which you can download from here: https://airsdk.harman.com/runtime
At least then you can save each new gallery to a folder named 'juicebox_gallery' on your desktop and stay away from the 'Browse...' button in the hope that the new runtime will fix it.

From your description of how things stand at the moment, I'd recommend a complete uninstall of both JuiceboxBuilder-Pro and AIR. When the time comes, you should be able to use the new runtime installer to upgrade AIR (on top of the old version, without having to uninstall or reinstall anything further).