If I go to https://picasaweb.google.com/data/feed/ … 8088651929 I am presented with an RSS feed of all your albums so 117363164378088651929 is certainly a valid Google User Id.
However, the Google Album Id 6315232953461261745 (from the URL in your last post) does not appear to be a valid Google Album Id for that account. That Google Album Id does not appear anywhere within the RSS feed data.

I do not know which album you are trying to display but if you use a Google Album Id from the links in the RSS feed page, the corresponding gallery should display fine.

You're welcome.
I'm glad your getting on well with Juicebox and your web site.

In case you're interested, I find the Mozilla Developer Network is a good reference for all things HTML, CSS and JavaScript.
You might also like to check out W3Schools. It's maybe not as comprehensive as the Moz Dev Network but it's often easier to navigate through their web pages (less information to trawl through) and find something quickly.
I also use the jQuery JavaScript Library a lot. It can simplify the code required for complex JavaScript tasks.

This is due to captionBackTopColor having different default values for Small Screen Mode and Large Screen Mode.
Please see my posts in this forum thread for more information.
The solution is to ensure that a captionBackTopColor value is explicitly set in your gallery's configuration options (and this value will be used in both Small and Large Screen Modes).
Just set captionBackTopColor="rgba(0,0,0,0)" (in JuiceboxBuilder-Pro's 'Customize -> Color' section) and all should be well.

Initially, none of your buttons have the class 'selected'.
All you need to do is give a button the class 'selected' either directly via CSS, e.g.:

<li><a href="javascript:;" id="button-1" class="selected">Catwalk Vibrant Colours</a></li>

... or via (jQuery) JavaScript:

$('#slideNav li a:eq(0)').addClass('selected');

... where 'eq(0)' represents the first button, 'eq(1)' represents the second, etc.

Try setting your gallery's background color in the JavaScript embedding code instead of just in the 'config.xml' files.
Try changing:

function loadGallery(a, b, c, y, z) {
    new juicebox({
        containerId: "juicebox-container",
        baseUrl: y,
        galleryHeight: z,
        maxThumbColumns: a,
        maxThumbRows: b,
        thumbsPosition: c
    });
    tracker = true;
}

... to:

function loadGallery(a, b, c, y, z) {
    new juicebox({
        backgroundColor: "rgba(255,255,255,1)",
        containerId: "juicebox-container",
        baseUrl: y,
        galleryHeight: z,
        maxThumbColumns: a,
        maxThumbRows: b,
        thumbsPosition: c
    });
    tracker = true;
}

This should hopefully help.

You're welcome.
Thanks for testing the fix.
I'll make sure that it's included in the next version of WP-Juicebox.

I think I've found a solution to the problem.
Open the plugin's 'config.php', jb-config.php' and 'save-gallery.php' files in a plain text editor and change all instances of:

include_once $wp_path . 'wp-blog-header.php';

... to:

include_once $wp_path . 'wp-load.php';

(There is just once instance near the top of each file.)
I'd be very grateful if you could test this proposed solution in your own WordPress site and let me know if it works.
Thank you.

It looks like certain permalink structures are causing the internal URLs used by WP-Juicebox to be rewritten (breaking the plugin).
My own tests suggest that using 'Plain' or 'Post name' permalinks works fine but using any of the others does not.

I'll investigate further and post back with my findings.

Maybe these links will help:
Embedding With Adobe Muse: http://www.juicebox.net/support/embeddi … adobe-muse
Alternate Adobe Muse Embedding Instructions: http://www.muse-themes.com/blogs/news/6 … adobe-muse

This sounds like a Muse-specific problem. I am not sure how (or if) this relates to Juicebox.

This is certainly a Juicebox problem and suggests that there is a problem with the path to the gallery's XML file.
Please see this FAQ:
When I view my gallery I see the message 'Config XML file not found'. How do I fix this?
Also, see note #1 below.

I do not see anything technically wrong with your embedding code.
However, there are a few things to bear in mind.

(1) Using absolute paths in your embedding code (starting with 'http://'), the gallery will display only when uploaded to your web server. Otherwise the 'Config XML file not found.' message will be displayed. If you want to check your gallery locally, use relative paths instead. (I do not know your file structure so cannot give you correct relative paths to use.) Please also note this FAQ when viewing galleries locally:
When I view my gallery locally, I see the message "Juicebox can not display locally in this browser". Why?

(2) I have navigated to the 'http://www.joshblank.photo/Gallery/Mexico/jbcore/juicebox.js' location in a browser (the path from your embedding code) but the 'juicebox.js' file is not there. Make sure that you have uploaded your gallery files to the correct location on your web server. It looks like the contents of your gallery folder should be uploaded to your '/Gallery/Mexico/' directory.

(3) If you hardcode the 'www' subdirectory into your embedding code paths, then the gallery will work on 'www.joshblank.photo' but may not work on 'joshblank.photo'. Please see this FAQ:
My gallery works on 'www.example.com' but not on 'example.com' (or vice versa). Why?
Use paths with a leading slash to denote your root directory, such the following, and your gallery should work on both 'www.joshblank.photo' and 'joshblank.photo'.

<script src="/Gallery/Mexico/jbcore/juicebox.js"></script>

baseUrl: '/Gallery/Mexico/',

Essentially, your current embedding code should work absolutely fine as long as your the contents of your gallery folder are uploaded to the '/Gallery/Mexico/' directory on your web server and you view your gallery via a URL starting with 'htitp://www.joshblank.photo/'.

If you continue to experience difficulties, then the best thing to do would be to upload everything to your web server and post a link to the non-functioning gallery. Once I can see the problem live on your web server, I should hopefully be able to pinpoint the exact nature of the problem and help further.

You're welcome.
I'm glad you've got it working.

If there is a value for captionBackTopColor in the gallery's XML file, then this will be used for both Small and Large screen modes.
However, if you leave captionBackTopColor unchanged from the default value shown in the JuiceboxBuilder-Pro interface, then captionBackTopColor will not be written to the gallery's XML file and the two different default values (for Small and Large Screen Modes) will be used.

As long as captionBackColor and captionBackTopColor are both exactly the same (color and opacity) and set to non-default values (which ensures that they will be written to the gallery's XML file), then there should not be a caption gradient in either Small or Large Screen Mode.

As far as I can recall, captionBackTopColor is the only configuration option which has different default values for Small and Large Screen Modes, so you should hopefully not encounter any other oddities like this.

For reference (and any other users reading this thread), we have an FAQ regarding browser caching here:
When I update my gallery I don't see my changes online. Why?

Set both captionBackColor and captionBackTopColor (in JuiceboxBuilder-Pro's 'Customize -> Color' section) to exactly the same values (color and opacity).

captionBackTopColor has different default values for Large Screen Mode (rgba(0,0,0,0)) and Small Screen Mode (rgba(0,0,0,0.3)) so if you do not change captionBackTopColor in JuiceboxBuilder-Pro's interface, a captionBackTopColor value will not be written to the gallery's configuration file and the two default values will be used.

If you want to ensure that a single captionBackTopColor is used in both screen modes, change its color or opacity slightly from its default value. Then, to remove the gradient, set captionTopColor to exactly the same color and opacity as you've used for captionBackTopColor.

Click on the small color box next to each color option and you'll see the exact hexadecimal color code that corresponds to the chosen color.

Unfortunately, the integrated browser which comes bundled within JuiceboxBuilder-Pro does not support certain CSS3 properties (such as gradients and shadows) so the live preview will not be 100% accurate.
This is a known issue and is noted as such in the JuiceboxBuilder-Pro User Guide. Please view the gallery in a browser for a more accurate preview.

Set imageNavPosition ('Customize -> Main Image') to STAGE rather that its default value of IMAGE. The main image navigation arrows will then be positioned relative to the stage rather than the images. However, please bear in mind that if the images take up a lot of the gallery's image area (which will depend on the gallery, image and browser window sizes), the navigation arrows may still be overlaid on top of the images. If this is the case, then you might like to compensate for it by increasing the imagePadding ('Customize -> Main Image').

Unfortunately, I really do not know when this issue will be fixed or when the next version of Juicebox will be released.
There is no set release schedule and any estimate I give you could turn out to be wholly inaccurate.
It is unlikely to be a matter of days but if I said it might be a few weeks, it could turn out to be a few months (or vice versa).
I'm sorry I can't give you a better idea of how long you might have to wait.

If it's any consolation, Multi-Size Image support is not completely dysfunctional and still works OK on Apple-branded 'Retina Display' devices (both mobile and desktop), where the term 'retina' refers specifically to Apple's 'Retina Device' trademark.
However, Juicebox-Pro is not currently recognizing other, non-Apple, high-density pixel ratio devices which is the nature of the problem and the reason for the bug report.

Thanks for your help.
I've been able to replicate the problem in a test gallery of my own and a bug report has now been logged.
Hopefully the problem will be fixed for the next version.