A gallery embedded manually will look and function exactly the same as a gallery created with WP-Juicebox (assuming both galleries have exactly the same configuration settings).

Using WP-Juicebox will embed the gallery automatically (avoiding any problem which can occur when embedding manually such as file locations and pathing issues). Also, if you have multiple galleries on the same page, WP-Juicebox will load the 'juicebox.js' file only once per page (rather than once per gallery). This is recommended. (Loading the 'juicebox.js' file multiple times in a single page can cause problems, especially if the 'juicebox.js' files being loaded are different versions.)

There are no advantages to embedding manually (but as long as the file locations and embedding code are correct, there are no disadvantages, either). However, if your WordPress site can display multiple posts containing Juicebox galleries on a single page, then there may be an issue with multiple 'juicebox.js' files being loaded. Using WP-Juicebox will avoid this potential problem.

Here are the steps required to achieve your manually embedded Flickr-sourced gallery.
(1) Create a Juicebox gallery (using Flickr as a source of images) using JuiceboxBuidler-Pro.
(2) Upload the complete gallery folder (not just the contents) to your web server.
(3) Paste the baseUrl embedding code into the body of your WordPress page (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.

In a WordPress site where you may have little or no control over the gallery's parent containers, I would recommend giving your gallery a fixed pixel value height (such as 600px) instead of the JuiceboxBuilder-Pro default value of 100%.
Please see this note regarding Using Percentage Heights. (Using a fixed height will avoid this potential problem.)

If you copied the entire contents of your gallery folder (but not the folder itself) to your root directory, then the 'juicebox.js' file would be in the correct location (according to your current embedding code). You could do this and you should see that your gallery displays OK.

I suspect that you may have already uploaded your gallery folder to your web server somewhere but I do not know where it might be. If you have already uploaded your gallery folder to your web server, then you can leave it exactly where it is and:
(a) Add a baseUrl line to your embedding code to point towards the gallery folder. The baseUrl an be relative (to the page containing the embedding code) or absolute.
(b) Adjust the path to the 'juicebox.js' file at the top of your embedding code (to point to the 'juicebox.js' file inside the 'jbcore' folder in your gallery folder. Again, this path can be relative (to the page containing the embedding code) or absolute.

Please see Steps #1 - #3 above.

I hope this helps to clarify things.

No. Direct linking still uses only the image index number.
It is easy to allocate each image in a gallery a unique number but it would be more difficult to allow image names to be used. Some kind of mapping (image name <--> image number) might be required.

You can still link directly to an image within a Juicebox gallery from Facebook (or any other web page) as long as you know the position of the image in the gallery (which should be fine as long as you do not set randomizeImages="TRUE").
Here is a link to the 7th image in one of our demo galleries: http://juicebox.net/demos/pro/full/#7
If you wanted to use a link like this on your Facebook page, just be sure to use the whole URL (including the '#7' part at the end).

If you like, please feel free to post suggestions for future versions in the Feature Requests forum thread.
This keeps all the ideas together and ensures that they are not overlooked by the developers. Thank you.

If the problem is intermittent, then the cause is likely to be either web sever or internet connection related.
The code on your pages will remain constant and should be rendered with consistency.

Juicebox will display the "Config XML file not found" error if the XML file cannot be reached in a timely manner.
The fact that the problem is intermittent suggests that a timeout error may be occurring (the time taken to fetch the XML file is too long).

I'm not sure it will help but you could try increasing your PHP set_time_limit directive to ensure that your PHP file has enough time to generate the XML file.
You could also increase your browser's default timeout value to see if this makes a difference. (You might need to do a web search to see if this is possible with your particular browser.) I realise that this will not help others viewing your web site but it might give us some insight into the nature of the problem.

I notice that your gallery's XML file is generated by a PHP file but the configURL (the URL for the PHP file) is first generated by a JavaScript function.
Also, your web page loads files from several different domains and includes approximately 40 external JavaScript files and 30 external CSS files.

I understand that you may need everything for your web site to function correctly but I can't help but think that you might have fewer Juicebox errors if things were simplified a bit.
If you have any plugins which you are not currently using, try deactivating them to prevent their files from being loaded into your page.

Try also deactivating W3 Total Cache and allow all files to be served from your own web server (instead of a Content Delivery Network). I do not know if this will make a difference but it might be worth trying so see what happens.

Another thing you might like to try is to hardcode the path to the PHP file in your gallery's embedding code (to see if there is perhaps a timing issue with the JavaScript function which builds the configURL which might be contributing to the problem).
Change:

configUrl: dsidx.details.GetConfigUrl(),

... to:

configUrl: 'http://mrtownhome.net/wp-content/plugins/dsidxpress/client-assist.php?action=GetPhotosXML&pid=147337406',

You might need to change this in one of your plugin's source files. I realise that this is not a solution (it will only ever show the images for a single gallery) but it might be interesting to see if it helps with the problem.

Unfortunately, I do not have a solution to your problem and some trial and error might be required but I hope the suggestions above point you in the right direction.

All XML entities within the Gallery Title (and any other configuration options in the gallery's XML file) need to be escaped. Otherwise they may break the structure of the XML file.

If you enter a Galley Title such as "France Bretagne<br />Normandy" into JuiceboxBuilder, the application will automatically escape the XML entities as required and the Gallery Title will become "France Bretagne&lt;br /&gt;Normandy" in the XML file.
However, if you edit your XML file manually, then you will need to escape the XML entitles yourself and enter:

galleryTitle="France Bretagne<br />Normandy"

I have changed the code in my previous post to reflect this. Sorry for any confusion caused.

Basically, if you have any of the following characters in any configuration options in your gallery's XML file and you edit the XML file manually, then you will need to replace them as follows:

& - replace with &amp;
' - replace with &apos;
" - replace with &quot;
< - replace with &lt;
> - replace with &gt;

Thank you for providing the URL to your gallery's web page.

There are <p> and <br /> tags scattered throughout your gallery's embedding code which are introducing empty space and line breaks above your gallery.
It looks like these are being inserted by WordPress's wpautop function.

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

Please note that you may need to re-enter your gallery's embedding code into your post (or manually remove the tags from the editor) after disabling wpautop (which should prevent the tags from being inserted in subsequent posts).

Alternatively, you could install the Raw HTML plugin and wrap the gallery's embedding code 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.

Yes. You can use HTML line breaks (<br />) to split your Gallery Title into multiple lines.
Please see this FAQ:
How do I add HTML formatting to the Gallery Title or Back Button?

You could use a Gallery Title such as:

galleryTitle="France Bretagne<br />Normandy"

Juicebox was not designed with this functionality in mind (the size of the gallery changing depending on the size of each image within the gallery). Ordinarily, a gallery's size will remain constant (unless the gallery is responsive and the size of the user's borwser window changes) and images will be scaled to fit within the gallery's image area.
However, you could perhaps use something like the following. The example gallery below has a fixed width and the height of the gallery changes when a new image is selected, depending on the height of the image (and adding 105 pixels to take into account the thumbnails).
If uses several Juicebox-Pro API functions.
To see this in action, create a sample gallery with JuiceboxBuilder-Pro and replace the gallery's 'index.html' file with the code below.

<!DOCTYPE html>
<html lang="en">
    <head>
        <meta charset="utf-8" />
        <style type="text/css">
            body {
                margin: 0px;
            }
            #wrap {
                width: 100%;
            }
        </style>
        <script type="text/javascript" src="jbcore/juicebox.js"></script>
        <script type="text/javascript">
            var widthInteger = 600;
            var jb = new juicebox({
                containerId: "juicebox-container",
                galleryHeight: "400",
                galleryWidth: widthInteger.toString(),
                imageScaleMode: "SCALE"
            });
            jb.onImageChange = function(e) {
                var index = e.id;
                var info = jb.getImageInfo(index);
                var url = info.imageURL;
                var image = new Image();
                image.src = url;
                var height = image.height;
                var width = image.width;
                var newHeight = Math.floor((widthInteger/width)*height) + 105;
                jb.setGallerySize(widthInteger, newHeight);
            };
        </script>
        <title>Test</title>
    </head>
    <body>
        <div id="wrap">
            <div id="juicebox-container"></div>
        </div>
    </body>
</html>

Unfortunately, you are currently loading your gallery into an iframe and it is a little more difficult to have the gallery (on the page being loaded into the iframe) control the iframe's height (on a different page) when a new image is selected.
You would need to give your iframe an 'id', for example:

<iframe id="target" src="http://borrowsynths.com/erika/galleries/landscape/index.html" frameborder="0" scrolling="no" style="position: absolute; top:0; left: 0; width: 100%; height: 100%;"></iframe>

... and then add the following code after the jb.setGallerySize(widthInteger, newHeight); line in the sample above (to change the height of the iframe).

window.parent.document.getElementById('target').style.height = newHeight.toString() + 'px';

I hope this points you in the right direction.

No problem. Just glad to hear that you've got it sorted. Thank you for letting me know.

The current version of WP-Juicebox (v1.4.4.2) should already support Google Photos.
Select 'Picasa Web Album' as the image source and enter your Google Account name in the 'Picasa User Id' input field (for example gallery123 from 'gallery123@gmail.com') and your Album Name in the 'Picasa Album Id/Name' input field.

In Juicebox-Lite, the image overlay disappears after 4 seconds of inactivity or when the mouse hovers outside the gallery and, by default, the Gallery Title is positioned on the overlay.

There are certain configuration options you could use to change this behavior but they are all available to Juicebox-Pro only and are not supported by Juicebox-Lite.

(1) You could change inactivityTimeout to change the auto-hide time period (or set it to zero to disable the auto-hide functionality).
(2) You could change showImageOverlay from its default value of AUTO to ALWAYS (to always show the overlay).
(2) You could use galleryTitlePosition to place the gallery title in a non-overlay position (TOP or ABOVE_THUMBS).

Whether you insert your gallery's embedding code manually or use the WP-Juicebox plugin to insert a Juicebox shortcode, the gallery will appear in the content section of your page or post.
However, the location of of the page or post content will be determined by your WordPress theme.
If you like, you could post the URL to your gallery's web page.
I'll be happy to take a look and see if there is anything that you can do to move the gallery up your page.

I'm glad you're getting on well with Juicebox-Pro!

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

Unfortunately, there is no configuration option that you can use to change the initial fade in of the gallery.
You could perhaps initially hide the 'juicebox-container' <div> using CSS and then show the gallery when Juicebox has completed initialization (when the Juicebox-Pro API onInitComplete event is fired).
Try something like the following. Create a sample gallery with JuiceboxBuilder-Pro and replace the gallery's 'index.html' page with the code below.

<!DOCTYPE html>
<html lang="en">
<head>
    <title>Juicebox-Pro Gallery</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" />
    <style type="text/css">
    body {
        margin: 0px;
    }
    #juicebox-container {
        display: none;
    }
    </style>
</head>
<body>
    <!--START JUICEBOX EMBED-->
    <script src="jbcore/juicebox.js"></script>
    <script>
    var jb = new juicebox({
        containerId: 'juicebox-container'
    });
    jb.onInitComplete = function() {
        $('#juicebox-container').show();
    };
    </script>
    <div id="juicebox-container"></div>
    <!--END JUICEBOX EMBED-->
</body>
</html>