I have been unable to replicate the problem you have reported.
Using the current version of WP-Juicebox (v1.4.0.0), I can display a Juicebox gallery sourced by your Picasa Web Album images using the username and web album name that you do.
I see no problem with your gallery's configuration option settings.
Try re-uploading the WP-Juicebox files to your web server to ensure that all files are present and correct.
If you are in any doubt as to whether or not the existing files are being overwritten, try deleting them from your web server first before uploading the new files.
Also, you could try to display a different Picasa Web Album using the username 'picasateam' and the web album name 'VegasWeekend' to see if this sample web album displays OK.

If "small" and "large" mode are handled by smallImageURL and largeImageURL respective, what attribute is used to define the "medium" mode source, perhaps just imageURL?

The medium image source is handled by imageURL.

You say "large" mode (which I presume uses the source defined in largeImageURL) is "used in Large Screen Mode when opening image in a new window or when gallery is expanded". I originally thought this is what the linkURL attribute is for. Would you be able to clarify the distinction between these going forward along with best practices for backwards compatibility with old (pre 1.4) XML?

Large Screen Mode will use medium images in normal mode and large images in expanded mode and when opening an image in a new window. I have notified the developers of a couple of exceptions to this rule and will post back when I have more information.

Which source is used when generating a "splash" image in small screen mode? smallImageURL?

The smallImageURL is used for the Splash Page image in Small Screen Mode.

If XML generated for 1.4-PRO (using smallImageURL and largeImageURL attributes) is used in a pre-1.4 version of your javascript library, or 1.4-Lite, will there be any issues?

There should be no issues. Juicebox-Pro prior to v1.4.0 and Juicebox-Lite (all versions) will just use the imageURL entries as before and ignore the smallImageURL and largeImageURL entries.

3,878

(1 replies, posted in Juicebox-Pro Support)

Unfortunately, it is sometimes necessary to change the 'theme.css' file between versions (when bugs are fixed or new features are added). We are aware of this and have tried to make configuring a gallery as flexible as possible (for example with the available configuration options and the use of vector icon fonts) without the need to modify CSS (although I understand that some things may be achieved only with custom CSS).
Perhaps a solution to your problem would be to have your modifications in a separate CSS file and use the !important declaration to ensure that they override the CSS rules from the gallery's own 'theme.css' file.

Juicebox does, indeed, still support older versions of Internet Explorer. IE8 still has a small but not insignificant market-share and we do not want to alienate users by dropping support for older browsers too early.

There is only one version of Juicebox available and, therefore, I am unable to supply you with a version available which does not include support for older versions of Internet Explorer.

3,879

(2 replies, posted in Juicebox-Pro Support)

Juicebox v1.4.0 has just been released and introduces a new expandedBackgroundColor option so it is now possible to set different background colors for normal and expanded modes. Please see this blog entry for details.

3,880

(4 replies, posted in Juicebox-Pro Support)

Juicebox v1.4.0 has just been released and introduces a new expandedBackgroundColor configuration option so it is now possible to set different background colors for normal and expanded modes. Please see this blog entry for details.

3,881

(6 replies, posted in Juicebox-Pro Support)

Juicebox v1.4.0 has just been released and introduces a new expandedBackgroundColor configuration option so it is now possible to set different background colors for normal and expanded modes. Please see this blog entry for details.

This bug has now been fixed in v1.4.0. Please see this blog entry for details.

This bug has now been fixed in v1.4.0. Please see this blog entry for details.

3,884

(7 replies, posted in Juicebox-Pro Support)

When I adjust the stage padding it affects the buttons as well.

This bug has now been fixed in v1.4.0. Please see this blog entry for details.

This bug has now been fixed in v1.4.0. Please see this blog entry for details.

3,886

(9 replies, posted in Juicebox-Pro Support)

All the sharing icons and other icons appear overlapped.

This bug has now been fixed in v1.4.0. Please see this blog entry for details.

3,887

(5 replies, posted in Juicebox-Pro Support)

The bug I referred to in my last post has now been fixed in v1.4.0. Please see this blog entry for details.

3,888

(4 replies, posted in Juicebox-Pro Support)

Juicebox v1.4.0 has just been released and should hopefully fix the problems noted above.
Please see this blog entry for details.

This bug has now been fixed in v1.4.0. Please see this blog entry for details.

3,890

(2 replies, posted in Juicebox-Pro Support)

Issues (1), (2) and (4) from the original post above have now been fixed in v1.4.0. Please see this blog entry for details.

3,891

(2 replies, posted in Juicebox-Pro Support)

Juicebox v1.4.0 has just been released. Please see this blog entry for details.

3,892

(3 replies, posted in Juicebox-Pro Support)

This bug has now been fixed in v1.4.0. Please see this blog entry for details.

3,893

(4 replies, posted in Juicebox-Pro Support)

Juicebox v1.4.0 has now been released. Please see this blog entry for details.

3,894

(1 replies, posted in Juicebox-Pro Support)

Is this a real trouble for gallery loading on mobile devices ?

If you want to have a Juicebox gallery on your web page, then there is no option but to include the 'juicebox.js' file (which internally loads the 'theme.css' file). These files are too large to be included inline within a web page and this is not possible anyway as the structure of the 'jbcore' folder must be kept intact for Juicebox to know where its own resource files are located.
Loading the 'juicebox.js' file asynchronously may not work (the 'juicebox.js' file will have to have been fully loaded by the time the browser parses the embedding code <script> block) but if you would like to try it, please take a look at the suggestions in this forum thread.
(Incidentally, entering 'google.com' into Google's own own PageSpeed Insights results in a Mobile Speed result of 64/100.)

3,895

(4 replies, posted in Juicebox-Pro Support)

Unfortunately, I do not know for sure.
There is no release schedule for Juicebox and, therefore, no set release date for the next version. It will be released only when it is ready (although it should hopefully be sooner rather than later). However, any estimate I give you could turn out to be wholly inaccurate. I hope you understand.
If you would like to be notified when a new version is released, please join our mailing list at the foot of our homepage, follow us on Twitter @JuiceboxGallery or subscribe to our blog RSS feed.

3,896

(4 replies, posted in Juicebox-Pro Support)

@ckukshtel

All gallery files must be hosted on the same domain or subdomain as the HTML page containing the gallery's JavaScript embedding code. This is due to the same-origin policy. Knowing that you are using Shopify and that you are unlikely to be hosting your gallery on Shopify's own web servers, then this is like to be the problem that you are encountering.
Possible solutions would be to use an iframe  (as I mentioned in my post above) or you may be able to implement a Cross-Origin Resource Sharing (CORS) solution: http://www.w3.org/TR/cors/
Try adding the following to the .htaccess file in the root directory of the domain which currently hosts your gallery.

Header add Access-Control-Allow-Origin "*"

I'm glad your gallery now works as expected in IE8.
Thank you for posting back to let me know.

3,898

(1 replies, posted in Juicebox-Pro Support)

The gallery images are responsive, but since I have set the "Gallery Height" to 650px the space between the main images and the thumbs (which are below the main images) becomes bigger and bigger as the browser width  becomes smaller (I have three fixed layouts, narrow, normal and wide + mobile).

This happens because as the size and shape of the user's browser window changes, the aspect ratio of your gallery (specifically the image area within the gallery) changes but the aspect ratio of your main image does not. When using the default value for imageScaleMode (SCALE_DOWN), Juicebox will scale the main image within the image area and if the aspect ratios of the image area and the image itself do not match, then there will be space to the left and right or top and bottom of the image.

I thought I could use "Gallery Height"=100% if I set a container div (which contains the gallery, created in my case by Drupal) which has it height set to a  specific value for each of the four responsive layouts and also set "position: relative". But that didn't seem to work.

This will not work (as you have discovered). If you set your gallery's height to 100% but the gallery's parent container has a fixed height, then the gallery's height will also become fixed (e.g. 100% of 800px = 800px).

If you always want to fill the gallery's image area (so that there is minimal space between the bottom of the main image and the thumbnails), you can set imageScaleMode="FILL". However, your images may be cropped.

If you want your gallery's aspect ratio to always be constant (ie. for your gallery's width and height to both change when the user changes the browser's width), then please take a look at this forum post to see how this can be achieved with JavaScript. However, please bear in mind what whereas this is relatively easy to implement with a standalone gallery on a web page, it may be difficult to incorporate into a Drupal environment.

It looks like IE8 is choking on lines 255 and 256 of your 'PhotoGallery.html' page:

<script type="text/xml">
</script>

Remove these lines from your web page (the <script> section is empty and the 'type' should be 'text/javascript') and your gallery should hopefully display OK in IE8.

3,900

(3 replies, posted in Juicebox-Pro Support)

Thanks -- the error message was very clear in Chrome, with a link to further information that explained the background.

We plan to introduce a similar message (and link) for IE11 in the next version of Juicebox.

Would be great to have the landing page give an up to date list of browsers/versions that do/don't work for local preview.

We will merge the FAQs into one and list all major browsers which prevent the loading of XML files locally (IE11, Chrome and Opera) in the next site update.

One can hope that a mechanism of explicit approval of "trusted" local XML will be future browser feature.

That would certainly be ideal.

it would be very nice (save people time!) to provide an explanation whether the problematic restrictions in those browsers tied to URI scheme -- file:// versus http:// for example -- or intranet versus internet, or?

The problem (with Chrome and Opera at least) is specifically with the file:// protocol.