3,151

(8 replies, posted in Juicebox-Pro Support)

The bug referred to above (whereby the caption for the first image fails to display) has now been fixed in v1.4.3. Please see this blog entry for more information on the latest version.

3,152

(6 replies, posted in Juicebox-Pro Support)

The bug referred to above (whereby the caption for the first image fails to display) has now been fixed in v1.4.3. Please see this blog entry for more information on the latest version.

3,153

(3 replies, posted in Juicebox-Lite Support)

This bug (whereby main images may not display when selected in IE8 and IE9) has now been fixed in v1.4.3. Please see this blog entry for more information on the latest version.

3,154

(16 replies, posted in Juicebox-Pro Support)

The bug referred to above (whereby scrolling down a page containing an embedded gallery on an iOS 8 device jumps to the top of the page) has now been fixed in v1.4.3. Please see this blog entry for more information on the latest version.

This bug (whereby scrolling down a page containing an embedded gallery on an iOS 8 device jumps to the top of the page) has now been fixed in v1.4.3. Please see this blog entry for more information on the latest version.

3,156

(4 replies, posted in Juicebox-Pro Support)

The bug I referred to above (whereby elements from the embedding web page may still be visible after a gallery has been expanded) has now been fixed in v1.4.3. Please see this blog entry for more information on the latest version.

3,157

(4 replies, posted in Juicebox-Pro Support)

This bug (whereby elements from the embedding web page may still be visible after a gallery has been expanded) has now been fixed in v1.4.3. Please see this blog entry for more information on the latest version.

3,158

(3 replies, posted in Juicebox-Pro Support)

This bug (whereby elements from the embedding web page may still be visible after a gallery has been expanded) has now been fixed in v1.4.3. Please see this blog entry for more information on the latest version.

3,159

(10 replies, posted in Juicebox-Pro Support)

The bug I referred to above (whereby elements from the embedding web page may still be visible after a gallery has been expanded) has now been fixed in v1.4.3. Please see this blog entry for more information on the latest version.

This bug (whereby elements from the embedding web page may still be visible after a gallery has been expanded) has now been fixed in v1.4.3. Please see this blog entry for more information on the latest version.

3,161

(5 replies, posted in Juicebox-Pro Support)

This bug (whereby elements from the embedding web page may still be visible after a gallery has been expanded) has now been fixed in v1.4.3. Please see this blog entry for more information on the latest version.

This bug (whereby elements from the embedding web page may still be visible after a gallery has been expanded) has now been fixed in v1.4.3. Please see this blog entry for more information on the latest version.

This bug (whereby elements from the embedding web page may still be visible after a gallery has been expanded) has now been fixed in v1.4.3. Please see this blog entry for more information on the latest version.

This bug (whereby elements from the embedding web page may still be visible after a gallery has been expanded) has now been fixed in v1.4.3. Please see this blog entry for more information on the latest version.

3,165

(5 replies, posted in Juicebox-Pro Support)

This bug (whereby elements from the embedding web page may still be visible after a gallery has been expanded) has now been fixed in v1.4.3. Please see this blog entry for more information on the latest version.

This bug (whereby elements from the embedding web page may still be visible after a gallery has been expanded) has now been fixed in v1.4.3. Please see this blog entry for more information on the latest version.

3,167

(2 replies, posted in Juicebox-Lite Support)

This bug (whereby elements from the embedding web page may still be visible after a gallery has been expanded) has now been fixed in v1.4.3. Please see this blog entry for more information on the latest version.

This bug (whereby elements from the embedding web page may still be visible after a gallery has been expanded) has now been fixed in v1.4.3. Please see this blog entry for more information on the latest version.

3,169

(1 replies, posted in Juicebox-Pro Support)

What exactly was the error message that you encountered? (Knowing exactly what it is might help in diagnosing the problem.)

If you were able to unzip the Juicebox-Pro zip file without any errors, then it is unlikely that the 'JuiceboxBuilder-Pro.air' file is corrupt or incomplete.
Please take a look at the Installation Issues in the JuiceboxBuilder User Guide to see if any of the troubleshooting tips help.

There is also a fairly comprehensive list of things to check and try in this forum thread.
Ideally, you should just be able to install JuiceboxBuilder-Pro by just double-clicking the installation file but as you are having difficulties, one of the suggestions in the forum thread (link above) might help.

If you continue to have problems, please post back with the exact wording of the error message you see so that I can hopefully help further.

3,170

(5 replies, posted in Juicebox-Pro Support)

Which page on your web site are you trying to embed your Juicebox gallery into?
I have checked your main 'Home' page and your 'Wedding Gallery' and 'Portrait Gallery' pages but do not see any Juicebox embedding code on any of these pages.
Please check that you have entered the embedding code correctly and have uploaded your gallery files to your web server following the embedding instructions here.

If you plan to embed multiple galleries to your site, I would recommend using the baseUrl method of embedding as documented here. This allows you to keep each gallery in its own folder on your web server which might help to keeps things organized.

As a Drupal user, you might also be interested in the dedicated Juicebox module for Drupal. It can be downloaded from this web page.
Please note that we did not write this module ourselves and support for the module (if you choose to use it) would be best directed towards the Drupal forum where the author of the module should be able to help you out.

3,171

(1 replies, posted in Juicebox-Pro Support)

JuiceboxBuilder-Pro does not integrate directly with WordPress but you can certainly create a gallery using JuiceboxBuilder-Pro and then embed it in a WordPress page or post using the baseUrl method as documented here.
Essentially, once you have created a gallery with JuiceboxBuilder-Pro, you would upload the complete gallery folder (not just the contents) 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.

If you select the 'Add SEO Content' checkbox (in the 'Customize -> Sharing') section, then the SEO code will be displayed as part of the embedding code that you would copy on the 'Publish' tab but, when pasting the code into your WordPress page or post, you might need to check that the paths to the images are correct (depending on the location of your gallery folder on your web server).

Alternatively, as a WordPress user, you might be interested in the dedicated Juicebox plugin for WordPress (WP-Juicebox).
Please see the plugin's support page for further details.
However, please note that the plugin does not include SEO functionality. This is a feature of JuiceboxBuilder-Pro only.

3,172

(2 replies, posted in Juicebox-Lite Support)

Unfortunately, there is currently a known bug whereby elements which have explicitly been assigned a CSS 'position' are not covered by the fullscreen gallery (they should be). This bug has already been addressed and will be fixed in the next version of Juicebox.

In the meantime, there are a couple of workarounds:
(1) Set useFullscreenExpand="TRUE".
... or:
(2) Set expandInNewPage="TRUE". When the gallery is expanded, it will be displayed on a page of its own rather than on top of the embedding page. Please note that this option is available in Juicebox-Pro only (and not in Juicebox-Lite).

Both Juicebox-Lite and Juicebox-Pro support embedding multiple galleries on a single web page or on multiple web pages.
Please see the Embedding Multiple Galleries support section for details where there are also online examples.

3,174

(1 replies, posted in Juicebox-Pro Support)

The fullscreen expand functionality seems to work OK in the two demo galleries you quoted in Safari 5.1.7 on my own PC.
Try clearing your browser's cache before reloading the galleries to see if this makes a difference.

Also, do you see the problem in any other browser or just in Safari 5.1.10?
I notice on this web page that Safari 5.1 has only partial support for the Fullscreen API (which Juicebox uses to expand the gallery fullscreen when useFullscreenExpand="TRUE"). Full support for the Fullscreen API was not introduced in Safari until version 6. This may be a contributing factor to your problem.

3,175

(11 replies, posted in Juicebox-Pro Support)

Unfortunately not. The code which handles the toggleThumbs() method is in the 'juicebox.js' file which is packed and obfuscated and cannot be modified.

The only other option would be to determine (using a browser's developer tools) which container you would need to show and hide and then manually use custom JavaScript code (perhaps with a jQuery animation effect) to slide the thumbnails in and out as required. However, you would likely encounter pitfalls in doing so as Juicebox would not know what was happening behind the scenes. Juicebox might think the thumbnails are being displayed when they are actually hidden (which could cause problems when the Thumbnail Button is clicked) and the main image may not expand to fill the available space if you hide the thumbnail container manually. Things might get messy quite quickly.

Probably best to wait for the bugfix to be implemented.