A Juicebox gallery does not use or require PHP so this is not the cause of the problem.

Without being able to examine your .htaccess file, I do not know if there is any code in there which might be contributing to your problem. Take a look for any references to XML files. (Search the file for the term 'xml' and temporarily remove any entries found to see if this helps.)

Perhaps the best thing to do would be to contact your web host and ask them why your http://morethansnapshots.com/LRGallerie … config.xml file is not publicly accessible and why trying to access it in a browser results in an error 403 (forbidden) message.

Also, having seen that my galleries are embeds, do I need so put additional code into files?

No. For what you are trying to do (link directly to full-browser gallery pages), all you should need to do is:
(1) Create a gallery with JuiceboxBuilder-Pro (or whatever other method you like).
(2) Upload the complete gallery folder (not just the contents) to your web server (without making any modifications to the contents of the gallery folder at all).
(3) Link to the gallery's 'index.html' file (inside the gallery folder) from your main web page.

If your web server was allowing access to your gallery's XML file, then you would not be experiencing any problems.
Your web host should hopefully be able to quickly and easily determine the exact cause of your problem and fix it for you.

Thank you for the feedback and suggestion.
I would encourage you to post your ideas in the Feature Requests forum thread. This keeps all the ideas together and ensures that they are not overlooked by the developers. Thank you.

Whether you intend to display a Juicebox gallery in a web page alongside other content or just on a page of its own, it still needs to be embedded. When you create a gallery with JuiceboxBuilder-Pro or the Lightroom plugin, the gallery is automatically embedded into a page of its own (the 'index.html' page).

You should be able to create a gallery (with the method of your choice), upload the complete gallery folder to your web server and link to the 'index.html' page within the gallery folder.

Your problem is currently with the 'config.xml' file inside the gallery folder (your '/LRGalleries/TxCapSculptureJBX/' folder).
Try opening the 'config.xml' file directly in a browser: http://morethansnapshots.com/LRGallerie … config.xml
This bypasses Juicebox. You should be able to see the contents of the XML file in your browser. Instead, the following message is displayed.

This suggests that the permissions on the file (or on one of its parent folders) are still too restrictive and your web server is preventing the browser from being able to read the file.
Compare this to the 'config.xml' file in a working gallery: http://www.juicebox.net/demos/lite/full/config.xml

It is not a problem with Juicebox functionality but rather a problem with the XML file on your web server.
Please double-check the permissions on your gallery's 'config.xml' file and on all the directories that the file is nested within ('LRGalleries' and 'TxCapSculptureJBX').

If you continue to experience difficulties, then it would help if I had access to your web server so that I could investigate further.
If you are agreeable to this, please let me know and I will send you a message with an email address where you can send me your FTP login details.
Thank you.

Thank you for providing the URL to your gallery.
I have viewed your gallery and all 47 thumbnails displayed first time without issue and without the need to refresh the page (although they seemed a little slow to load).

If you view your gallery in different browsers (or in the same browser after clearing the cache each time), is it always the same thumbnails that do not appear or does it change from time to time?

If you find that you are getting inconsistent results then the problem may be due to either your web server or internet connection.
The code on your web page remains constant and browsers will always process this code in the same way each time the page is displayed.
The only other factors in the equation are the web server and internet connection (the means by which the code is passed to the browser). If the browser does not receive the complete code, then your web page may not be complete.
For example, if your web server is experiencing problems in serving the files in a timely manner, the browser may time-out whilst trying to load an image. Also, if you have an internet connection that drops-out occasionally, a similar thing can happen.
Please check with your web host to see if they have been experiencing any issues lately which might be contributing to your problem. Also, check that your internet connection is stable.

Maybe the problem is just a browser caching issue. Try completely clearing your browser's cache before reloading your web page to see if this helps.

I see the problem you are describing.

Default values are not written to gallery XML files as they should not be not necessary. If a configuration option is not explicitly listed in a gallery XML file, then its default value should be used.

However, the exception to this rule is that if you do not explicitly set an expandedBackgroundColor, Juicebox uses the backgroundColor (for consistency between the normal and fullscreen displays).

The workaround to this would be to ensure that you explicitly set an expandedBackgroundColor.

The only problem with this is that when you use an expandedBackgroundColor with transparency and set useFullscreenExpand="TRUE", the actual background color is dependent on the browser as different browsers use different background colors (black vs white) for the default fullscreen visual environment.

The best course of action to workaround both issues above would be to explicitly set an opaque expandedBackgroundColor.

I'm glad you've got JuiceboxBuilder-Pro up and running.
Thank you for posting back to let me know.

The default values for both backgroundColor and expandedBackgroundColor in JuiceboxBuilder-Pro are both '222222'. These values are noted as defaults in the Config Options page.
I've just double-checked this in my own installation. When I click the color box next to 'Background Color' (in the 'Customize -> Lite' section) or 'Expanded Background Color' (in the 'Customize -> General' section), '222222' is displayed as the default value.

Default values are not written into the 'config.xml' file but if you change both of these values to black ('000000' with opacity '1'), then the following values are written to the 'config.xml' file:

expandedBackgroundColor="rgba(0,0,0,1)"
backgroundColor="rgba(0,0,0,1)"

... and the following is also included in the embedding code in the 'index.html' page:

backgroundColor: 'rgba(0,0,0,1)'

If you do not see this behavior, then try uninstalling and reinstalling JuiceboxBuilder-Pro and make sure that you are using the most recent version of JuiceboxBuilder-Pro (v1.4.3) to ensure that any bugs present in previous versions which have since been fixed are not contributing to your problem. You can check which version you are using by going to 'Help -> About JuiceboxBuilder-Pro' from the drop-down menu at the top.
If necessary, instructions for downloading the current version and upgrading JuiceboxBuilder-Pro can be found on the Upgrading Juicebox support page.

If you set a gallery's background to be transparent (by setting its opacity to '0'), then, by default, the background will be white (the default background color of an empty tab/window in a browser) unless you have something else below the gallery the gallery using HTML and CSS.

Please note that if you set the expanedBackgroundColor to be transparent and also set useFullscreenExpand="TRUE", then the actual expanded background color might be white or black depending on the default color that the browser chooses to use when the Fullscreen API is used. (For example, Chrome uses white and Firefox uses black.) For consistency when using useFullscreenExpand="TRUE", I would recommend using an expandedBackgroundColor with an opacity of '1' (fully opaque).

Only JuiceboxBuilder-Lite has an 'Upgrade to Juicebox-Pro!' button. JuiceboxBuilder-Pro does not feature such a button.
I realise that you are unable to click 'New Gallery' or 'Open Gallery' but does the splash page read 'JuiceboxBuilder-Pro' when you start the application? Does the text on the application's title bar also read 'JuiceboxBuilder-Pro'? How about 'Help -> About...' from the drop down menu at the top?

It sounds like JuiceboxBuilder-Lite is somehow getting tangled up with JuiceboxBuilder-Pro although, under normal circumstances, JuiceboxBuilder-Lite and JuiceboxBuilder-Pro can be installed an run side-by-side on the same computer without issue.

I'm sure you've tried many things many times but I would give it one more go.
Make sure that you uninstall both JuiceboxBuilder-Lite and JuiceboxBuilder-Pro. (Delete the 'JuiceboxBuilder-Lite' and 'JuiceboxBuilder-Pro' files from the Applications folder and empty your Trash.)
Then search your hard drive for the term 'JuiceboxBuilder' (rather than 'JuiceboxBuilder-Pro' this time) and manually delete everything found.
Double-check that the following folders have been deleted:
/Users/your_username/Library/Application Support/Adobe/AIR/ELS/JuiceboxBuilder-Lite
/Users/your_username/Library/Application Support/Adobe/AIR/ELS/JuiceboxBuilder-Pro

Now try reinstalling only JuiceboxBuilder-Pro, allowing the application to install to the default location.

I'm glad to hear that it worked.
Many thanks for letting me know.

Unless your web page always fills the browser's height and width completely (no matter what its size and shape) with no vertical or horizontal scrollbars, then you could try giving your gallery a width of 100% but a fixed height. If your web page is responsive but allows for vertical scrolling, then this may be a quick and easy solution to your problem.

You could load the gallery when the page is loaded by calling the loadGallery() function in the $(document).ready(function() {}) section (alongside the click handler) e.g.:

$(document).ready(function() {
    loadGallery();
    $('#photo').click(function() {
        loadGallery();
    });
});

That's another possible solution.
You could just load the gallery once on your page (rather than using the loadGallery() function in my suggestion above), assign a variable name to your 'juicebox' object (such as 'jb' in the example below) and then use the Juicebox-Pro API setGallerySize() method to set the gallery size when the 'photo' tab is clicked. However, please note that setGallerySize() accepts only absolute pixel values (and not percentages) so you would have to use some custom JavaScript code to fetch the size of the gallery's parent container (and/or browser window dimensions) in order to determine what the gallery's actual size (in pixels) should be.
The structure (without the actual calculations for the gallery width and height which will be unique to your own web page's layout) for such a solution might look something like this:

<script src="jbcore/juicebox.js"></script>
<script>
    var jb = new juicebox({
        containerId: "juicebox-container",
        galleryWidth: "100%",
        galleryHeight: "600px",
        backgroundColor: "rgba(34,34,34,.5)"
    });
    $(document).ready(function() {
        $('#photo').click(function() {
            var galleryWidth; //Calculate gallery width here and assign value to galleryWidth variable
            var galleryHeight; //Calculate gallery height here and assign value to galleryHeight variable
            jb.setGallerySize(galleryWidth, galleryHeight);
        });
    });
</script>
<div id="juicebox-container">

It certainly sounds like your embedding code has been entered as plain text rather than as HTML code.
The most likely explanation for the embedding code being be visible on screen when you view your web page in a browser would be if Dreamweaver had modified the code (escaping the XML entities) which would happen if the embedding code had been entered as text rather than code, thereby preventing a browser from parsing it as code and resulting in it just being displayed instead.
Please double-check that you have entered the embedding code as raw HTML (to ensure that Dreamweaver does not modify the code at all) and if you continue to experience difficulties, please post the URL to your web page so that I can take a look at the problem for myself and help further. Thank you.