We have just released a hotfix version of v1.4.0 which includes a fix for the problem you reported.
Please re-download Juicebox-Pro using the link from your purchase email and upgrade your gallery following the instructions on the Upgrading Juicebox support page.

3,852

(6 replies, posted in Juicebox-Pro Support)

Thank you for providing the URL to your gallery via email.
It looks like the data for your gallery's XML file is being generated correctly so all the correct files are in place and not corrupt.
However, the problem seems to be that the XML declaration in the dynamically generated XML file (the <?xml version="1.0" encoding="UTF-8"?> line) is not at the very top of the document. There is a blank line before the XML declaration which should not be there and this is very likely to be the cause of the problem.

I cannot be certain but I suspect this may be a bug in the version of PHP which is installed on your web server.
(What version of PHP is installed on your web server and has your web host recently upgraded the version of PHP or changed any PHP settings?)
Please try the following suggestion which should hopefully solve your problem:

Open the module's 'juicebox/includes/JuiceboxGallery.inc' file in a plain text editor and change line 171 from:

return $dom->saveXML();

... to:

return $dom->saveXML($juicebox);

Please note that the line number above refers to the recommended release of the module (dated 2014-Jan-28) which is available from this web page.

3,853

(1 replies, posted in Juicebox-Pro Support)

As you are aware, there is no 'Check for updates...' functionality within JuiceboxBuilder-Pro.
If you would like to be kept informed of new releases, then please join our mailing list at the foot of our homepage, follow us on Twitter @JuiceboxGallery or subscribe to our blog RSS feed.

3,854

(6 replies, posted in Juicebox-Pro Support)

It has been working just fine until the other day.

Something must have changed for this to happen.
If you did not change anything yourself, then check to see if any automatic updates to your Drupal installation were installed.
Also, check with your web server to see if they have changed anything recently (such as upgrading the version of PHP installed or changing any PHP settings) which may be contributing to your problem.

It would be much easier to troubleshoot your scenario if you were able to provide the URL to the gallery in question so that I could take a look for myself. Without seeing your gallery's embedding code, I have no way of knowing how the path to your gallery's XML file is defined.
It sounds like the PHP file within the Drupal module which dynamically generates the XML data may have somehow become corrupt or missing but, if this were the case, then re-uploading the module's files to your web server (which you have already tried) should solve the problem.

It doesn’t mention what to do with images/ , thumbs/, config.xml, index.html.

These files and folders are unique to each individual gallery and it is not necessary to copy them into the module's own file structure. (The module deals with these files and folders each time you create a gallery.) Only the 'jbcore' folder should be integrated within the module.

As we did not write the module ourselves (and the problem you are encountering seems to be related to the gallery's embedding code which is generated by the module), you might also like to post in the Drupal forum where the author of the module should be able to help.

However, if you continue to experience difficulties, please post back with the URL to your gallery and I will certainly try to help further.

3,855

(1 replies, posted in Juicebox-Pro Support)

Yes. Instructions for embedding a Juicebox gallery into a web page can be found here.

If, for example, you wanted your gallery to appear in the middle light-grey area on your web page, then you would paste your gallery's embedding code between the <section class="section-wrapper"> and </section> tags (on line 76) and you would also need to copy the contents of your gallery folder into your http://www.bigmusicgeek.com/gallery/ directory.

3,856

(12 replies, posted in Juicebox-Pro Support)

I have found that sometimes when it stops, I can get it working again by sending the "presets" folder to the trash.

If/when this happens again, please zip the 'presets' folder and email it to me (I have sent you a message regarding another forum query so you should have my email address) before you trash it so that I can take a look for myself and try to replicate the problem. Thank you.

3,857

(3 replies, posted in Juicebox-Pro Support)

Please check your email. I have sent you a message.
Thank you.

Unfortunately, there is no quick and easy solution to your problem.

It is certainly not possible to change the way JuiceboxBuilder-Pro generates the SEO content code.

If the data you wanted to use for your SEO content code were embedded in the IPTC Document Title and Description fields within your images, then you could have JuiceboxBuilder-Pro use this information to automatically populate the image titles and captions respectively (using 'Images -> Titles' and 'Images -> Captions' from the drop-down menu at the top). The image titles and captions (sourced from the image's IPTC fields) would then be used in the SEO content code.

Perhaps you could find a program that would create a batch process to copy the content of the IPTC Keywords field into the Document Title and/or Description fields of all your images so that you could use this information within JuiceboxBuilder-Pro.

Otherwise, you could perhaps use a plugin (for example for Lightroom or WordPress) to create your gallery and then modify the plugin to generate SEO content code.
However, this would likely be a complex and time-consuming project.
You would need to:
(1) be familiar with the structure of the plugin you intend to modify.
(2) be familiar with the programming language used by the plugin (e.g. Lua for Lightroom or PHP for WordPress).
(3) create a method to iterate over the images in your gallery.
(4) extract the information you want to use for your SEO code from the images.
(5) output the SEO content (using the information extracted from the images) as HTML code to the web page.

How this would be achieved would differ greatly between plugins but the principle (the five steps above) would remain the same.

3,859

(5 replies, posted in Juicebox-Pro Support)

The multi-size image support is a feature of JuiceboxBuilder-Pro only and is not available in any of the plugins.
The Juicebox plugin for Lightroom cannot export multiple image resolutions at once.

I can't manage to get JBpro to use these. Is there a way?

No. It is not possible to tell JuiceboxBuilder-Pro what data to use to populate the tags and attributes in the SEO content code.
JuiceboxBuilder-Pro will always use the image title for the <img> tag's 'title' attribute and the image caption for the <img> tags's 'alt' attribute (and will also use both the title and caption as text within <p> tags).

I think this means that my conceptual understanding of things is solid

Yes. Juicebox's behavior regarding the linkURL should be logical and easy to understand (bugs notwithstanding). If a linkURL is set, then it should be used in preference to any image URL.

maybe a 1.4.1 release?

Very likely. As I mentioned earlier, we aim to fix this bug as soon as possible. If you (or any other users reading this) would like to be kept informed of new releases, then please join our mailing list at the foot of our homepage, follow us on Twitter @JuiceboxGallery or subscribe to our blog RSS feed.

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

3,863

(12 replies, posted in Juicebox-Lite Support)

Web pages using the border-box model no longer break Juicebox galleries.
This CSS issue has now been fixed in v1.4.0. Please see this blog entry for details.

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

3,865

(3 replies, posted in Juicebox-Lite Support)

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

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

3,867

(3 replies, posted in Juicebox-Lite Support)

These CSS issues have now been fixed in v1.4.0. Please see this blog entry for details.

Thank you for reporting this bug.
It looks like the problem is caused by the combination of setting both useFullscreenExpand="TRUE" and expandInNewPage="TRUE". I have logged a bug report with the developers.
Until the bug is fixed, a workaround would be to set one (or both) of these configuration options options to "FALSE".
As your gallery currently has a transparent background, you could perhaps set expandInNewPage="FALSE" and then set an opaque background color for your gallery in expanded mode, for example expandedBackgroundColor="rgba(0,0,0,1)".

Will all this be officially documented somewhere at some point?

I do not know if the complete logic which Juicebox uses to determine which image URL to use will be documented.
However, it takes into consideration factors such as:

  • Display mode (expanded vs normal)

  • Display screen (retina vs non-retina)

  • Screen mode (large vs small) which also takes into account the user's device (desktop vs mobile) and screen size

Also, the point that is still somewhat confusing to me is the handling of the linkURL attribute. Can you clarify how this will be used going forward?

Currently, the largeImageURL does take precedence over the linkURL. This is a bug which we intend to fix as soon as possible.
If a linkURL is defined, then it should always be used when clicking the 'Open Image' button (and for when imageClickMode="OPEN_URL"). If a linkURL is not defined, then Juicebox should use the largeImageURL and if a largeImageURL is not defined, then Juicebox should use the imageURL.

Also, it looks like 2 new attributes have been added to the <juicebox> tag in the XML, useLargeImages and useSmallImages.

These two new attributes are used only by JuiceboxBuilder-Pro when editing an existing gallery. They are not used by Juicebox itself (and therefore not required at all) when a gallery is being displayed.

I hope this makes sense and helps to clarify things.

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,872

(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,873

(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,874

(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,875

(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.