Every gallery needs to have a separate configuration file (default name 'config.xml').
You can certainly set Config Options in the embedding code (please see here for details), but image data cannot be set in the embedding code and must be set in the configuration file.
Even if you use a Flickr account as a source of images and set the Flickr Options in the embedding code, the gallery still needs a separate configuration file (even if it is just a dummy file with only a <juiceboxgallery /> tag) to function correctly.

Please note that if a configUrl is not explicitly set in the embedding code, then Juicebox will look for a file named 'config.xml' in the same directory as the web page containing the embedding code.

I don't know what your goal is or if it will help you out but you could use a PHP script (or use some other server-side scripting language) to generate XML content on-the-fly when the gallery is displayed. Please take a look at this forum post (scroll down to the answer to Query #3) which has an example of how this could be achieved to display all images in a designated folder. (You could change the code to pull in image data from a database or whatever image source you choose to use.)

I appreciate you taking the time to post your suggestions in the forum.
However, if would be much better if you posted them in the Feature Request forum thread (a dedicated thread for ideas) where they will be seen by the developers and are less likely to get lost in amongst all the other support threads.
Thank you.

Incidentally, captions appear and disappear with their corresponding images so you might like to try setting imageTransitionType to either FADE or CROSS_FADE and then increasing the imageTransitionTime from its default value of 0.3 to something larger (although this will affect all image transitions, not just the initial image fade in).
Still, it might be worth trying a few different combinations in case you find something close to what you are trying to achieve.
(Both the configuration options in bold above can be found in the Main Image Options section of the Config Options page.)

You're welcome.

All you need to do to upgrade an existing gallery from Juicebox-Lite to Juicebox-Pro is replace the gallery's Lite 'jbcore' folder with the Pro 'jbcore' folder from the Juicebox-Pro zip package ('juicebox_pro_1.5.0/web/jbcore/'). This will instantly remove the image limit and branding and any Pro configuration options in the gallery's configuration file will become active.

You can also load a Juicebox-Lite gallery (using a local copy of the gallery on your computer) into JuiceboxBuilder-Pro (the desktop application to create and edit Juicebox-Pro galleries), configure the gallery with Pro options if you like (on the 'Customize' tab) and re-save the gallery on the 'Publish' tab. The gallery will be upgraded to Juicebox-Pro and you can then re-upload the gallery to your web server.

There is no way to change the imageURL prefix in JuiceboxBuilder-Pro. Images are always placed in a folder named 'images' and the imageURL paths always start with "images/". There are no user-changeable configuration options to change the name of the image folder or to set a different prefix for the imageURL. The code which handles this is compiled and cannot be modified.

If you want to use a different gallery structure to that created by JuiceboxBuilder-Pro, then you'll need to edit your gallery's 'config.xml' file in a plain text editor to change the imageURL paths.
However, if you use a text editor such as Notepad++, you'll be able to change all instances of "images/" to whatever you like across multiple files (if you have many galleries to change) in a single global search and replace action which should take just a matter of seconds.

You could modify the template 'index.html' file that JuiceboxBuilder-Pro uses to generate the gallery's 'index.html' file.
On a Windows PC, this template file is located here: C:\Program Files (x86)\JuiceboxBuilder-Pro\template\index.html
Try replacing the contents of this template file with the following. (I would strongly suggest that you take a backup of the original template file first, just in case anything goes wrong and you need to reinstate it at a later date.)

<!DOCTYPE html>
<html lang="en">
<head>
    <title>%%TITLE%%</title>
    <meta charset="utf-8" />
    <meta name="viewport" id="jb-viewport" content="width=device-width, initial-scale=1.0, minimum-scale=1, maximum-scale=1, user-scalable=0" />
    <meta name="description" content="%%DESCRIPTION%%" />

    <!-- START OPEN GRAPH TAGS-->
    <meta property="og:title" content="%%TITLE%%" />
    <meta property="og:type" content="website" />
    <meta property="og:url" content="%%GALLERY_URL%%" />
    <meta property="og:image" content="%%IMAGE_URL%%" />
    <meta property="og:description" content="%%DESCRIPTION%%" />
    <!-- END OPEN GRAPH TAGS-->

    <style type="text/css">
    body {
        margin: 0px;
    }
    </style>
</head>
<body>
    <!--START JUICEBOX EMBED-->
    <script src="jbcore/juicebox.js"></script>
    <script type="text/javascript">

        var purchaseURL;

        var strWindowName = 'Shopping Cart';
        var strWindowFeatures = 'menubar=yes,location=yes,resizable=yes,scrollbars=yes,status=yes,width=600,height=400';

        var jb = new juicebox({
            containerId: "juicebox-container",
            galleryWidth: '%%WIDTH%%',
            galleryHeight: '%%HEIGHT%%',
            backgroundColor: '%%COLOR%%'
        });

        jb.onInitComplete = function() {
            $('.jb-bb-btn-fotomoto').off('click');
            $('.jb-bb-btn-fotomoto').click(function() {
                var windowObjectReference = window.open('about:blank', strWindowName, strWindowFeatures);
                $.get('config.xml', function(data) {
                    var index = jb.getImageIndex();
                    purchaseURL = $(data).find('image').eq(index - 1).attr('purchaseURL');
                }).done(function() {
                    windowObjectReference.location.replace(purchaseURL);
                }).fail(function() {
                    windowObjectReference.close();
                });
            });
        };

    </script>
    <div id="juicebox-container"></div>
    <!--END JUICEBOX EMBED-->
</body>
</html>

A spinning logo usually indicates that an image cannot be found (perhaps due to an incorrect path in the gallery's XML file or a missing image on the web server).

If your gallery was working fine but now is not (and you have made no changes), then this suggests that something might have happened on your web server to cause the problem.
First of all, check that the paths to the images in your gallery's XML file are correct and that your images are present in their correct locations on your web server.
You might like to also contact your web host to ask if they have changed anything or have been experiencing any issues lately which might be contributing to your problem (maybe they have had some reason to reinstate your website from an incomplete backup).

If you continue to experience difficulties, please post back with the URL to your gallery's web page so that I can see the problem for myself and hopefully help further.
Thank you.

It sounds like your problem might be due to incorrect or missing MIME types (for the font files) on your web server.
If this is the case, then you may have to contact your web host to ask if they can add the font file types (.eot, .svg, .ttf, .woff) to the list of MIME types (so that browsers know what to do with them).

Also, try viewing your gallery in different browser to see if the problem occurs in them all or just in certain browsers.
For example, if you see the problem in just Internet Explorer, then make sure that Compatibility View is not enabled.

I hope these notes help.
However, if you continue to experience difficulties, please post the URL to your gallery's web page so that I can take a look at the problem and hopefully help further. Thank you.

If your link looks like www."website"/NewMexico2017/index#27, then there could be 2 problems.

(1) If you want to use an absolute path, start the link with http:// (or https://), otherwise, the link will be seen as a relative path (relative to the web page containing the link).

(2) If 'index' is actually a web page named 'index.html' then use 'index.html#27' instead of 'index#27'.

Also, make sure that your gallery sets enableDirectLinks="TRUE" (in JuiceboxBuilder-Pro's 'Customize -> General' section).

If these notes do not help, then I would really need to see the problem live on your web server in order to help further so, if possible, please post back with the URLs for the page with the link and the gallery itself. Thank you.

I'm glad it worked for you. Thank you for letting me know.

We are actively working on the next version just now but, unfortunately, I do not know when it will be released. There is no set release schedule and it'll be released only when we feel it's ready. Any estimate I give you could turn out to be wholly inaccurate. I hope you understand.
However, if you'd like to be notified when new versions are released, you can join our mailing list at the foot of our homepage, keep an eye on our Facebook page, follow us on Twitter @JuiceboxGallery or subscribe to our blog RSS feed.

Juicebox was not designed to initially display the expanded version of a gallery.
If a web page is loaded and a gallery on the page is initially expanded, then the other content on the web page alongside the gallery would not be visible (and the user would have no knowledge that it was even there).
If you really want to expand a gallery on load, please see this forum post for a couple of suggestions.

If you just want your gallery to fill a browser window without the need to expand it, then perhaps the best solution would be to embed your gallery in a web page with dimensions of 100% x 100% and make sure that there is no other content on the web page. (The Splash Page is not displayed by default if a gallery has dimensions of 100% x 100% and is the only content on the web page.)

Alternatively, if your gallery is embedded in a web page alongside other content and you still want the other content to be visible, then you can choose to not use the Splash Page (and just have the gallery displayed where the Splash Page would normally be) by setting showSplashPage="NEVER" (in JuiceboxBuilder-Pro's 'Customize -> Splash Page' section).
Alternatively, you could force your gallery to always be displayed in Large Screen Mode (which does not use the Splash Page by default) on all devices and in all browsers by setting screenMode="LARGE" (in JuiceboxBuilder-Pro's 'Customize -> General' section).

Whatever you choose to do, you can disable the Expand Button if you like by setting showExpandButton="FALSE" (in JuiceboxBuilder-Pro's 'Customize -> Lite' section).

I hope this gives you a few ideas to try.

Placing the code from the FAQ at the end of your .htaccess file (as you have done) is fine. (Anywhere outside the existing <IfModule mod_rewrite.c> ... </IfModule> section is fine.)

The layout of your web page is controlled via CSS and I expect there are likely going to be media queries and screen width breakpoints (and perhaps even some JavaScript code to determine whether or not the mobile layout will be used). Being that I am not familiar with the code or internal workings of your current theme, troubleshooting is quite difficult.

If it were my own site, I'd probably try using a different theme (at least for testing purposes) to see how things look on mobile versus desktop. Maybe try one of the default themes (such as Twenty Sixteen or Twenty Seventeen) to see how you get on.

I'm pretty sure that the answer lies somewhere within your current theme's code but without knowledge of exactly how your theme works (and decides to lay out your web page), I cannot answer the question of why the presence of a Juicebox gallery on your web page changes your web page's layout on mobile devices.

Knowing that CSS is probably somehow involved, you might also like to try changing your gallery's width from 100% to a fixed pixel value (such as 800px). I realise that this is not a long term solution to the problem (it'll mean that your gallery is no longer responsive in the horizontal dimension) but it might give you some insight into the nature of the problem. Giving a gallery a width of 100% means that it will fill the width of its parent container. However, its actual width (in pixels) might somehow be calculated incorrectly and seen by your theme as being large enough to warrant using the desktop layout. Using a fixed pixel value for your gallery's width might make a difference. It's a long shot but something I'd try for myself just out of curiosity. (I'm really just thinking out loud at this stage.)

Unfortunately, without knowing exactly what is causing the problem, trial and error seems to be the way forward.
I would certainly try a few different themes (to see if the answer lies somewhere within your current theme's code) and some fixed width galleries (maybe try a few different fixed widths) so see what happens.

I hope this at least points you in the right direction.

Edit:
I've just taken a look at the headers for your websites.
The 'no-transform' Cache-Control header is correctly set up and active on your http://dev.mulhollandgates.com/ website but not currently on your http://gateslosangeles.com/ website.

Also, I notice that WP-Juicebox in both of your websites still uses Juicebox-Pro v1.4.0.
I would strongly encourage you to upgrade your galleries to v1.5.0 (see details in my first post above).
I still think that this might help with your problem.