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.

Please note that the 2 bugs above are unique to JuiceboxBuilder (and not Juicebox itself).
The problems occur during the creation of the gallery by JuiceboxBuilder and not during the display of the gallery by Juicebox.
As such, you might find that you get better results with WP-Juicebox (although this will depend on the image source and how the images are handled before they are fed to Juicebox).

Incidentally, if you want to embed a gallery created by JuiceboxBuilder into a WordPress page or post (without using WP-Juicebox), then I'd recommend using the baseUrl method of embedding documented here.
Essentially, once you have created a gallery with JuiceboxBuilder, you would upload the complete gallery folder to your web server and paste the baseUrl embedding code into the body of your WordPress page or post (ensuring that the method of entry is 'Text' rather than 'Visual'). It does not matter where on your web server you upload your gallery folder to as long as the two paths in the embedding code (the path to the 'juicebox.js' file and the baseUrl itself, pointing towards the gallery folder) are correct.

Of course, if you change the transparency of the images (to match the gallery's background color), this should avoid the problem completely, no matter how your gallery is being created. I realise that it is not ideal but I'm glad you've found a suitable workaround until the bugs are fixed.

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

It seems strange that activating WP-Juicebox would prevent your web site from triggering its mobile mode.
Usually, factors such as the device (browser user agent), screen size and screen resolution will be taken into account when deciding whether to use desktop vs mobile mode but, from what you say, your theme's logic seems to also be considering page content. Maybe your theme's author can help determine why your mobile mode is not being used when WP-Juicebox is active. Other than loading the 'juicebox.js' JavaScript file and having a <script> tag with the gallery's embedding code, all that WP-Juicebox inserts into the web page is a <div> container for the gallery.

Checking out your website in Mobile Safari (iOS 10.3.1), the big difference between gallery pages and other pages seems to be that most gallery pages have large text at the top (above the header) such as "North Hollywood, Malibu, CA: Iron Gates in Los Angeles" in the link you provided. It seems to be this text that is not being resized appropriately. The rest of the web page seems to be responsive (the header fits the width of the web page and the navigation menu is hidden under the icon).
It might just be that your theme is not taking this text into account when resizing content for mobile devices.

The "Error: No p element in scope but a p end tag seen." validation message seems to be coming from the following two sections of code surrounding the gallery's embedding code.

<p>[vc_row el_position=&#8221;first last&#8221;][vc_column][vc_tabs interval=&#8221;0&#8243; el_position=&#8221;first last&#8221;][vc_tab title=&#8221;Pictures&#8221; tab_id=&#8221;1357613662131-6-0&#8243;][vc_column_text]

[/vc_column_text][vc_column_text el_position=&#8221;first last&#8221;][/vc_column_text][/vc_tab][vc_tab title=&#8221;Glass Information&#8221; tab_id=&#8221;1368221702106-4-9&#8243;][vc_column_text el_position=&#8221;first last&#8221;]</p>

If you view the source of your web page in your browser, you'll see this code surrounding the gallery's embedding code.
The plugin only inserts the code between <!--START JUICEBOX EMBED--> and <!--END JUICEBOX EMBED-->. The code I posted above (including the <p> and </p> tags) are not inserted by WP-Juicebox.

WordPress can sometimes insert unwanted <p> (and <br />) tags but usually only when you enter HTML code directly into the WordPress editor (in 'Text' mode). (Maybe you've got some code other than the WP-Juicebox gallery shortcode in your editor.) This is usually due to WordPress's wpautop function.

You could try installing a third-party plugin to disable the wpautop functionality, for example Toggle wpautop or wpautop control.
Otherwise, you could perhaps implement the manual solution from this forum thread.

Alternatively, you could try installing the Raw HTML plugin and wrap any HTML code that you have in the WordPress editor in [raw] ... [/raw] tags. This should prevent extra markup (such as <p> and <br /> tags) from being added to the HTML code by WordPress itself or any third-party theme or plugins.

This might help with the <p> </p> tags but I do not know where the [vc_*] tags are coming from. They look like unprocessed shortcode tags (but I do not know their origin).

Incidentally, it looks like your theme's custom CSS is affecting the layout of your WP-Juicebox galleries.
When I view a gallery on a mobile device, the Splash Page image is offset (to the top left). This is more than likely to be due to some CSS which is being applied to all images on your web page (including those in your gallery).
Specifically, on line 1 of your 57901af0a3c58.css file, there is the following code:

img, video, .wp-caption {
    -moz-box-sizing: border-box;
    -webkit-box-sizing: border-box;
    box-sizing: border-box;
    max-width: 100%;
    height: auto !important;
}

These CSS rules are being applied to all images (<img> tags) on your web page and the WP-Juicebox gallery has no option but to inherit them. Ideally, those CSS rules should be applied to only those elements on your web page which require them through use of CSS selectors (classes or ids).

I hope these notes point you in the right direction.

I notice that your galleries currently use Juicebox-Pro v1.4.0.
Please try upgrading them to the latest version (v1.5.0) to see if this helps. There have been 7 releases since v1.4.0 fixing many bugs so upgrading might fix your problem without any further action. Please see the Version History for a list of changes between versions.
You can download the latest version using the link from your purchase email (the link always points towards the latest version rather than the version you purchased). If you cannot find your purchase email or your link has expired, then please fill in the Download Link Request Form and the admin team will send you a new link. (Full details for upgrading can be found here.)
Once you've downloaded Juicebox-Pro v1.5.0, just replace the 'jbcore' folder in your WP-Juicebox plugin with the version from the Juicebox-Pro v1.5.0 zip package ('juicebox_pro_1.5.0/web/jbcore/') following the instructions here.

If this does not help, then try fixing the HTML errors on your web pages.
You can check the code on your web pages using the W3C Markup Validation Service. Some browsers may be more or less tolerant towards HTML errors than other and once the code on your pages validates correctly, your pages should be rendered with greater predictability and consistency across different browsers.

I hope this helps.

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

I notice that you are using the Juicebox module for Drupal. Please note that the module is an unofficial plugin which was not written by ourselves, and as such, I am not overly familiar with its code, interface or inner workings.

The problem seems to be not with Juicebox itself (Juicebox will display captions as long as they are present in the gallery's configuration file) but with the module's ability to fetch the captions and write them to the configuration file).

However, the module is well supported by its author in the Drupal forum and I would highly recommend that you post your query over there where Ryan will see it and hopefully be able to help you further.
(Also, the module's online documentation might help.)

I realise that this does not directly answer your query but I hope that it points you in the right direction.

Thanks for the link.
There are quite a lot of z-index values in your 'style.css' file and it's not easy to see exactly which elements are going to be stacked on top others but it looks like just removing z-index: 100; from your #header CSS (on line 110 of your 'style.css' file) might be enough to solve your problem.

The problem is likely to be that the z-index value is not being applied to the correct elements in your menu.
If you could provide the URL to a page which demonstrates the problem, I'll take a look and see if I can find a solution.
Currently, the web page whose URL you provided has two lots of (the same) embedding code but the gallery does not display because the path to the 'juicebox.js' file is incorrect.
I realise that you might not want a dysfunctional web page live on your site but I'd really need to see the problem in order to troubleshoot it so perhaps you could create a test page somewhere on your site that is not linked to from anywhere else.
Thank you.