526

(5 replies, posted in Juicebox-Lite Support)

Unfortunately, this bug was first reported after Juicebox v1.5.1 was released and there have been no versions released since then.
As such, this bug has not yet been fixed and is present in the current versions of both JuiceboxBuilder-Lite and JuiceboxBuilder-Pro.
However, it is a known bug that the developers are aware of and it should hopefully be fixed in a future version (although I do not know when this might be).
In the meantime, if your images need to be rotated twice, then I'd recommend doing so in an imaging program (such as Adobe Photoshop) before feeding them to JuiceboxBuilder.
I realise that this will create an extra step in your workflow but, unfortunately, it is unavoidable until the bug is fixed.

527

(6 replies, posted in Juicebox-Pro Support)

I've tried using Chrome's Javascript console to see what is going on, but nothing is shown - is there any way that I can see what the JB code is actually doing?

Try checking the 'Network' tab in your browser's developer tools to see the URLs that are actually being loaded (or attempting to be be loaded).

I was going to suggest that you try explicitly adding a themeURL entry to your gallery's embedding code but, as you already do this, maybe you could try removing it (and allow Juicebox to load the default theme from its default location) to see if this makes a difference. (You might need to reinstate a stock 'jbcore' folder within your gallery to try this.)
If a theme CSS file cannot be found, then the result is usually a blank gallery (like you describe) so it's worth a shot (at least for troubleshooting purposes). (The problem might be the URL to the theme CSS file rather than the URLs to the image files.)

At present, the SE friendly URL re-writing on this site is off - let me know if you want to take a look at the problem, and I'll turn it on, or I'm happy to give you administrator access to the backend of the site, if you wish, so that you can turn it on or off.

I'd really need to see the problem so if you can switch on the URL rewriting that would be great, although I may not be at my computer for a short while so if you'd rather send me (via email) access to your site's backend and instructions on how to switch the URL rewriting on and off, then I'll take a look as soon as I can.
Thank you.

528

(0 replies, posted in Tricks and Tips)

JuiceboxBuilder (both Lite and Pro versions) has the ability to extract IPTC data for use as image titles and captions via the 'Images -> Titles -> Use IPTC Title' and 'Images -> Captions -> Use IPTC Caption' options from the drop-down menu at the top.

If you are entering IPTC data in an Adobe program (such as Lightroom or Photoshop), then the label you'll need to use for the image title is IPTC Document Title and the label you'll need to use for the image caption is IPTC Description.

If you'd like to confirm that your downloaded zip files are not corrupt, then here are filesizes and hashes for the current (v1.5.1.2) Juicebox-Lite and Juicebox-Pro zip files.

Juicebox-Lite:

Name: juicebox_lite_1.5.1.2.zip
Filesize: 1,891,211 bytes
MD5: 7aea2fa3fe11019f0b0bd794c96ce85a
SHA1: 87b5da8cf23ef5b36a003468c8abc6037123166f
SHA256: 3a38333181f38806e18f45604e64fac067525f25c16fb836288160d145a5c7a9

Name: JuiceboxBuilder-Lite.air (v1.5.1.2)
Filesize: 1,386,533 bytes
MD5: c00e6323c08438f3fc069f10199e63f6
SHA1: 81f902352a1c077c653e61d9c46288723995c751
SHA256: 2ba340cbe7cc9824f5324bf6f238b194be17524e4a2cef71a9230d68578414ec

Juicebox-Pro:

Name: juicebox_pro_1.5.1.2.zip
Filesize: 1,907,008 bytes
MD5: 18dcb1666d93a4d24da1e7eff8138470
SHA1: 5b369b377a35293e9cd0055f622acb594eeddc2e
SHA256: 70cacb58d8d45fd347d599e4835d5dfec1c9ee9cf10786f5d7b2219e626acc4a

Name: JuiceboxBuilder-Pro.air (v1.5.1.2)
Filesize: 1,390,776 bytes
MD5: 6714ed9b9790beec4eb46dbe2000a656
SHA1: 0790b8df79efaf6f0b89624884252fd07001149e
SHA256: a26ff24c35c825e316ab7aa509d574dc6585d201da5260ab1df74a020315f591

[Edited 17 November 2023.]

530

(6 replies, posted in Juicebox-Pro Support)

I do not know how Joomla's URL rewriting works but if a URL is rewritten and changed, then it will no longer point towards the same location (and things will break).

Do you have an example of URL within your Juicebox embedding code before and after the rewriting so that I can see what's going on? Thanks!

Two things immediately spring to mind which might help...

(1) Manually change all the paths in your Juicebox embedding code (and the gallery's 'config.xml' file) from relative paths to absolute paths (i.e. paths starting with http:// or https://). A few copy and pastes (or some search and replace actions) in a plain text editor should take care of this.

(2) If the rewriting functionality allows for it  (I do not know if you are using a core Joomla feature or a plugin), make an exception for your Juicebox gallery page (within Joomla or the plugin's settings) so that rewriting is not performed on that page.

If you continue to experience difficulties, then please post back with a link to your gallery's web page so that I can see the problem for myself and hopefully help further. Thank you.

(If you do not want to post the link publicly here in the forum, just send em an email. My email address is in the column to the left of this post.)

531

(1 replies, posted in Juicebox-Pro Support)

As Shopify is not a regular web host, they do not provide FTP access to the web space that they provide (which would be required to upload the gallery files) unless you have a Shopify enterprise plan.
This is noted in this Shopify forum thread.

Due to Shopify not providing FTP access to the web space that they provide, you would need to find an alternative host for your Juicebox gallery and then load the gallery into an iframe in your Shopify page following the Embedding in a Web Template Site instructions here.

There are many web hosts that offer free web space which would be suitable for hosting Juicebox galleries. Juicebox galleries do not require any special web server requirements (with the exception of Password Protection and the Download Button which require PHP 5.2.0 or later). Please see the System Requirements for details.
Try a web search with terms such as 'free web hosting' but please bear in mind that with a free hosting account, you may get little or no support, less reliability (more server down-time) and fewer features than with a paid support account.
A couple of free web hosts that I have personally used in the past and that you might like to take a look at are AwardSpace and x10hosting.
Please note that we are not affiliated with these web hosts at all. They are merely suggestions (and not recommendations).

If you do have a Shopify enterprise plan with FTP access, then you should be able to log into your Shopify web space, upload the complete Juicebox gallery folder via FTP (using a dedicated FTP program such as Filezilla) and then embed the gallery into your Shopify page using the baseUrl method of embedding documented here.
The baseUrl method of embedding is essentially the same the regular method of embedding but with a baseUrl entry in the embedding code pointing towards the gallery folder.

I hope my notes above help to clarify things and point you in the right direction.

532

(5 replies, posted in Juicebox-Pro Support)

No problem! I'm glad that everything seems to be working as expected.
Just give me a shout if you see anything odd happening and I'll look into it further.
Thanks!

533

(5 replies, posted in Juicebox-Pro Support)

You're welcome! Your gallery certainly looks fine.

Incidentally, everything seems to be working as expected when I view your gallery in Firefox (on my laptop) and use Responsive Design Mode ('Tools -> Web Developer -> Responsive Design Mode').
At default settings (Screen Dimensions 360px by 740px, Device Pixel Ratio 1), small images are used (checked on the developer tools 'Network' tab).
If I then change the Device Pixel Ratio to 2 (to simulate a retina screen), medium images are used.
Everything seems to be working as expected.
(It's possible that your Chrome browser was simulating a device with a retina screen.)

534

(5 replies, posted in Juicebox-Pro Support)

Just in case you've not yet seen it, the Multi-Size Image Support page can be found here.

Unfortunately, using a browser's developer tools is not always the most accurate way of replicating a particular browsing experience.
Changing the effective screen size might not be enough to emulate a mobile device and trigger a certain image size to be used.
When deciding which image size to use (or more specifically which screen mode to use, which has a bearing on the choice of image size), Juicebox also takes into account the user agent string (used to identify the browser) and the pixel density of the screen (i.e. retina or not).

As noted on the Multi-Size Image Support page, Small images are used when the gallery is displayed in Small Screen Mode on a non-retina screen but Medium images are used when the gallery is displayed in Small Screen Mode on a retina screen.

I have a set of images with 'SMALL', 'MEDIUM' and 'LARGE' text emblazoned across them which I use for testing (so that I can visually determine which image size is being used at a glance without needing to delve into the network report).

I have just checked a Small Screen Mode gallery on my non-retina laptop and small images are being used.
I have also checked an Auto Screen Mode gallery on my retina iPhone and medium images are being used.
Both these results are expected and things seem to be working OK (at least in my own tests).

I hope this helps (at least a little).

535

(1 replies, posted in Juicebox-Pro Support)

Ideally, Juicebox would allow me to create fields for the table which I would populate and these would appear below the image or overlay it.

Unfortunately, creating some kind of input method for custom fields for image captions (or anything else for that matter) would be a hugely complex task (and not possible within JuiceboxBuilder-Pro whose source is not available to be modified by users).
You can, however, add as much text to an image caption as you like and you can split text into separate lines using HTML line breaks (<br>).
For example, a simple two-line caption would look something line this

Line #1<br>Line #2

The use of HTML formatting within image titles/captions is noted in this FAQ:
How do I add HTML formatting to image captions and titles?

You could use an HTML <table> within an image caption but the caption area is already a <table> (with its own styling) so you might run into problems (although you could certainly try it if you like).
I am not aware of anyone having used a table in an image caption before so, unfortunately, I cannot point you towards any references for this.

If you do add a lot of text to your image captions, then you might need to increase maxCaptionHeight (in JuiceboxBuilder-Pro's 'Customize -> Caption' section) to accommodate all the text.

I hope this helps (at least a little).

If you use Juicebox-Pro's own Background Image Options (and your background image fills the gallery area without any transparency), then you may see a brief flash of color (grey by default) before the background image is displayed.
This is because the backgroundColor (set in the gallery's embedding code) is read and processed before any configuration options in the gallery's 'config.xml' file (such as backgroundUrl).
Set the gallery's backgroundColor to be completely transparent (any color with an opacity of 0) and this should resolve this issue.

backgroundColor: "rgba(0,0,0,0)"

(You can change the backgroundColor in JuiceboxBuilder-Pro's 'Customize -> Lite' section or by manually editing the gallery's embedding code.)

Incidentally, if the background image does not fill the gallery area (if backgroundScale="NONE") or if the background image is a PNG file with transparency, then the backgroundColor still needs to be active.

Unfortunately, there are no configuration options available within JuiceboxBuilder-Pro to change the font size of image titles and captions.

However, you can style individual image titles and captions (for example, to change the font size) using HTML formatting as noted in this FAQ:
How do I add HTML formatting to image captions and titles?

A sample caption with a font size of 12px (for example) would look like this:

<span style="font-size: 12px;">Image caption text goes here.</span>

In the gallery's XML configuration file, the caption would look like this:

<caption><![CDATA[<span style="font-size: 12px;">Image caption text goes here.</span>]]></caption>

... but JuiceboxBuilder-Pro will automatically add the <caption> and CDATA tags so you only need to enter the <span> tag (as above) into JuiceboxBuilder-Pro.
(You can do likewise for image titles.)

Otherwise, you can set the size of all image titles and/or captions at once using CSS such as the following (changing the numeric values as appropriate):

/* IMAGE TITLE */
.jb-caption .jb-caption-title {
    font-size: 20px !important;
}

/* IMAGE CAPTION */
.jb-caption .jb-caption-desc {
    font-size: 18px !important;
}

/* IMAGE NUMBER */
.jb-cap-frame .jbac-number {
    font-size: 12px !important;
}

You could add this CSS to the end of your gallery's 'jbcore/classic/theme.css' file or wrap it in <style type="text/css"> ... </style> tags and add it to the end of your gallery web page's <head> section.

If you want to change the font size for the Gallery Title, then you can do so using HTML formatting (just like the image titles and captions above).
Please see this FAQ for details:
How do I add HTML formatting to the Gallery Title or Back Button?

For example, you could enter a Gallery Title such as the following into JuiceboxBuilder-Pro's 'Customize -> Lite -> Gallery Title' field (changing the values as appropriate):

<span style="font-size: 48px;">Gallery Title text goes here.</span>

Alternatively, if you want to change the font size for the Gallery Title via CSS, then use the following (changing the numeric values as appropriate):

/* GALLERY TITLE - LARGE SCREEN MODE */
.jb-area-large-mode-title {
    font-size: 48px !important;
}

/* GALLERY TITLE - SMALL SCREEN MODE */
.jb-idx-ssm-title-wrapper {
    font-size: 48px !important;
}

Here is a comprehensive list of things to check and try for anyone experiencing difficulties installing JuiceboxBuilder-Pro (or JuiceboxBuilder-Lite).
I will update this list if/when any new tips are found.

#1 Check out the Install Issues in the JuiceboxBuilder User Guide in case any of the notes describe the problem you are facing and help.

#2 If using MacOS Catalina (10.15), then please see the additional steps required to install JuiceboxBuilder-Pro here.

#3 Make sure that you are using the latest version of JuiceboxBuilder-Pro.
You can check the latest version on the Version History page and you can check the version that you are using by going to 'Help -> About JuiceboxBuidler-Pro...' from teh drop-down menu at the top of the program.
If necessary, full instructions for downloading the latest version can be found on the Upgrading Juicbebox support page.

#4 Make sure that you have extracted the Juicebox-Pro zip file to your hard drive (rather than just looking inside the file with a zip program) and that you are not running the 'JuiceboxBuilder-Pro.air' file from a restricted file system or network drive.

#5 Make sure that the Juicebox-Pro and 'JuiceboxBuilder-Pro.air' files are not corrupt.
If you have been able to extract the Juicebox-Pro zip file without any errors, then the chances are that your files are OK.
However, you can check the MD5, SHA1 and SHA256 hashes of the current Juicebox files here.

#6 Make sure that you are using the latest version of Adobe AIR with WebKit support. This is currently AIR v33.1.1.744.
This version of Adobe AIR can be downloaded from the foot of Harman's AIR download page here.

#7 Check out the "Troubleshoot Adobe AIR installation" help pages below in case the problem is with Adobe AIR (rather than with JuiceboxBuilder-Pro).
Mac: https://helpx.adobe.com/air/kb/troubles … ac-os.html
Windows: https://helpx.adobe.com/air/kb/troubles … ndows.html

#8 Try using an older version of Adobe AIR.
JuiceboxBuilder-Pro requires Adobe AIR v2.0 or later so you could try a version such as v20.0.
Unfortunately, it is no longer possible to download older versions of AIR from the Adobe archive download page so finding older versions might be difficult. If you find a link to an older version of AIR from a source other than Adobe, then please download and install at your own risk. (Some users have reported success in using older versions of Adobe AIR which is why I list this as a suggestion.)

#9 Try completely disabling any third-party security software that you might have installed (e.g. Avast or AVG), including real-time protection and ransomware detection, before attempting to install JuiceboxBuilder-Pro in case this may somehow be interfering with the JuiceboxBuilder-Pro installation. (Please do so at your own risk and be sure to disconnect from the internet first.)

#10 Check that your system clock is accurate (and resync with a known time server if necessary) before attempting to install JuiceboxBuilder-Pro. (One user actually claims to have had to wind back his system clock 2 years in order to install JuiceboxBuilder-Pro. This seems to have been an isolated incident and no-one is quite sure why this was necessary but it might be something worth trying if nothing else works.)

#11 Try the complete uninstall/reinstall procedure below.

(1) Uninstall your current version of JuiceboxBuilder-Pro (if you have a version installed).
Mac: Delete the 'JuiceboxBuilder-Pro' file from the Applications folder and empty your Trash.
Windows: Use the uninstaller in the 'Control Panel -> Programs -> Uninstall a program...' list.

(2) After uninstalling JuiceboxBuilder-Pro, please check that there are no files are left behind (even from a failed installation) by manually deleting the following folders (if they exist) from your hard drive:
Mac:
/Applications/JuiceboxBuilder-Pro.app/
/Users/Username/Library/Application Support/Adobe/AIR/ELS/JuiceboxBuilder-Pro
/Users/Username/Library/Preferences/JuiceboxBuilder-Pro
Windows:
C:\Program Files (x86)\JuiceboxBuilder-Pro
C:\Users\Username\AppData\Roaming\Adobe\AIR\ELS\JuiceboxBuilder-Pro
C:\Users\Username\AppData\Roaming\JuiceboxBuilder-Pro
C:\Users\Username\Documents\JuiceboxBuilder-Pro

You may need to show hidden files to find some of the above locations in Windows File Explorer. Open File Explorer from the taskbar. Select 'View > Show', then select 'Hidden items' to view hidden files and folders.

(3) Also, please follow the procedure above (Steps #1 - #2) for JuiceboxBuilder-Lite, too (if you have it installed).
JuiceboxBuilder-Lite and JuiceboxBuilder-Pro can both be installed and run side by side on the same computer but, being that you are experiencing problems, it might be wise to completely clear your system of all JuiceboxBuilder files before trying to reinstall JuiceboxBuilder-Pro.

(4) Uninstall Adobe AIR.

(5) Reinstall Adobe AIR.
You can download the latest version of Adobe AIR from here.
Windows: To install Adobe AIR, instead of just double-clicking the 'AdobeAIRInstaller.exe' installation file, right-click it and select 'Run as administrator'.

(6) Reinstall JuiceboxBuilder-Pro (making sure that it is the latest version) following the instructions here.

#12 When using JuiceboxBuilder-Pro, do not load a gallery from (or save a gallery to) an online synced file-sharing folder (such as Google Drive or Dropbox).
JuiceboxBuilder-Pro creates a temporary folder (named '.tempGallery') whilst a gallery is being created or edited. This folder is automatically deleted on closing JuiceboxBuilder-Pro.
However, the use of an online synced file-sharing folder can prevent JuiceboxBuilder-Pro from deleting this temporary folder.
If you run into this problem and find that the 'New Gallery...' and 'Open Gallery...' buttons on the 'Start' tab become unresponsive, then just close JuiceboxBuilder-Pro and delete the '.tempGallery' folder manually.
On a Windows system, the '.tempGallery' folder is located here:

C:\Users\Username\Documents\JuiceboxBuilder-Pro\.tempGallery

Note for Juicebox-Lite users:

The notes above refer to Juicebox-Pro/JuiceboxBuilder-Pro but apply equally to Juicebox-Lite/JuiceboxBuilder-Lite.
If you are having problems with JuiceboxBuilder-Lite, then just follow the suggestions above but replace any instances of 'Juicebox-Pro' and 'JuiceboxBuilder-Pro' in any paths with 'Juicebox-Lite' and 'JuiceboxBuilder-Lite' respectively.

[Edit: Link updated 7 February 2025.]

Thank you for posting your suggestion in the Feature Requests forum thread!

Sorry, I missed your question about webp.

JuiceboxBuilder-Pro does not currently support webp as an image format.
Please see this FAQ:
Will Juicebox load things other than images?

However, you could use webp images in a Juicebox gallery but you'd need to build the gallery manually (adding an <image> entry to the gallery's 'config.xml' file for each webp image and then copying your image and thumbnail webp files to the gallery's 'images' and 'thumbs' folders respectively). As long as the browser being used to view the gallery supports webp images (please see here for details), the images will be displayed in the gallery.

If you like, you could post this idea (support for webp images) as a suggestion in the Feature Requests forum thread.
This keeps all the requests together and ensures that they will not be overlooked by the developers.
I do not know the likelihood of any ideas being implemented in future versions but this is certainly the best place for all ideas.
Thank you!

Probably the factor 1 ("The speed of the web server hosting the site") you mentioned and cannot be influenced is decisive, since the results of the measurements in the Google Search Console vary widely.

I agree.
There's really not much we can do as gallery authors (other than change the image filesize and the value of the imagePreloading configuration option) and if Google search results vary for any given gallery, then it's down to the web server hosting the gallery and Google's algorithms, neither of which we have any control over.

If it's any consolation, both your galleries (your 80% and 90%) galleries load quickly for me (real life scenario).

Thanks and best regards

You're welcome!

With regard to the speed at which your gallery images load, there are several contributing factors.
(1) The speed of the web server hosting the site.
(2) The speed of your own internet connection.
(3) The file size of the gallery images.
(4) The value of the imagePreloading configuration option.

You have little or no control over #1 and #2 is not relevant to Google search results (but can certainly play a part when viewing a gallery yourself).

With regard to #3, make sure that your image file sizes are not too large.
If using JuiceboxBuilder-Pro to create your gallery with default image dimensions (1024px x 768px at 80% quality), then resulting gallery images should be somewhere within the range of between 100KB and 200KB each.
If your image file sizes are much larger than this, then try tweaking the image dimensions and/or quality to bring the file sizes down to a reasonable level for web gallery use.

With regard to #4, the imagePreloading configuration option "Determines how images are preloaded. Also controls if images are kept in memory after being viewed." (Please see the Main Image Options in the Config Options page for details.)

The default value for imagePreloading is PAGE (whereby all images on the current thumbnail page are preloaded) but you could change this to NEXT (so that, when the gallery is initially loaded, only the next image in the gallery is downloaded and cached by the browser) or ALL (so that all gallery images are initially downloaded) to see if this makes a difference.

imagePreloading is supported by Large Screen Mode only so I don't think it'll have any effect on Google's mobile search results (Juicebox uses Small Screen Mode on mobile devices unless screenMode is explicitly set to LARGE in JuiceboxBuilder-Pro's 'Customize -> General section) but you might like to try changing its value as this is the only configuration option which has anything to do with the loading of the images.

Unfortunately, I know of no other ways to influence Google search results as far as image loading is concerned.

543

(1 replies, posted in Juicebox-Pro Support)

The captionPosition configuration option is active in Large Screen Mode only (noted in the Caption Options section of the Config Options page).
However, by default, when a gallery is viewed on a mobile device, Juicebox will display the gallery in Small Screen Mode where the value for captionPosition of OVERLAY is used (as screen real estate is generally limited on mobile devices and this value gives captions as much space as possible).

It is not possible to change the value of captionPosition for Small Screen Mode but you can force your gallery to be displayed in Large Screen Mode in all browsers and on all devices if you like by setting screenMode="LARGE" (in JuiceboxBuilder-Pro's 'Customize -> General' section).

For reference, more information about Screen Modes can be found in the Gallery Tour.

I hope this helps to clarify things a little.

I have tried to replicate the problem you describe (using a small image, setting imageScaleMode to SCALE_DOWN and comparing the size of the displayed image in Irfanview and JuiceboxBuilder-Pro's live preview window) but I do not see the problem shown in your screenshots. Both images are displayed at the same size for me.

There are, however, some known issues with JuiceboxBuilder-Pro's live preview window being unable to display the gallery with 100% accuracy (due to the internal browser not fully supporting CSS 3).
Please see the Known Issues section of the JuiceboxBuilder-Pro User Guide.

I don't know if it will help but try viewing the gallery in a modern and up-to-date browser (Chrome, Edge, Firefox, Opera, Safari) rather than JuiceboxBuilder-Pro's live preview window to see if this makes a difference (and make sure that your browser's zoom functionality is set to 100%).

Incidentally, I've also just created a test gallery using your own gallery's 'config.xml' settings from your post above (in case there's some odd combination of settings which is causing the problem) but I still cannot replicate the problem myself so the issue could potentially lie somewhere within your own system.

Check that your Windows 'Settings -> Display -> Scale and layout' value is 100% (in case this is currently set to a higher values such as 125%).

What I'm seeing when I view your gallery is expected behavior but maybe an explanation of what I'm seeing will help to clarify some things.

The first image in your gallery has dimensions of 665 x 999 and your gallery currently sets imageScaleMode="NONE".

When I view your gallery in small browser window (shorter than the image's actual height), the image is displayed at its actual size (without any dynamic scaling), but because the browser window (and, therefore, the gallery's image area) is not large enough to accommodate the image in its entirety, it is cropped (equally at the top and bottom), as noted on the Config Options page ("NONE: No scaling. Large images are cropped to fit Image Area.").

When using imageScaleMode="NONE", the image will be seen in its entirety (without cropping) only when the users browser window (or, more specifically, the gallery's image area) is large enough to accommodate the entire image.

With a responsive gallery whose dimensions change depending on the shape and size of the user's browser viewport (such as your full page gallery), you really have no way of knowing the shape and size of your gallery (it is dependent on the user's device and browser window) so the only way to be sure that your gallery images will be seen in their entirety is to set imageScaleMode to either SCALE_DOWN (the default value) or SCALE.

SCALE_DOWN is the default value as this scales down large images to fit within the gallery's image area (if necessary) but does not scale up small images (as this will likely decrease their visual quality.

I hope this helps to explain what you are seeing.

Images in a Juicebox gallery are dynamically scaled according to the imageScaleMode configuration option (in the 'Main Image' section).
The default value for imageScaleMode (which is used when imageScaleMode is not explicitly defined in the gallery's 'config.xml' file) is SCALE_DOWN, whereby large images are scaled down (if necessary) to fit within the gallery's image area (whilst repsecting their aspect ratios and without cropping) but small images are not scaled up.
You can check out the list of all possible values for imageScaleMode (including short descriptions for each) in the Main Images section of the Config Options page.
Your gallery's 'config.xml' file does not seem to include a value for imageScaleMode (at least not in the portion you included in your post above) so the default value of SCALE_DOWN will be used.

Is it possible to show them at the original size ?

If you do not want Juicebox to scale your gallery images at all, then set imageScaleMode to NONE. (This will work best with a gallery of fixed size where the gallery's dimensions are known and large enough to accommodate your images without them needing to be scaled up or down to fit within the gallery's image area.)

547

(7 replies, posted in Juicebox-Pro Support)

Now all i need to do is ask if we can have the first image in the slideshow set as the icon!

Unfortunately, as I'm sure you're already aware, there is no easy way to do this.
What you are doing is probably as automated as possible (using JuiceboxBuilder-Pro).
(With the Juicebox plugin for Lightroom, you could quite easily point towards the first image in the gallery but there would be no way to process the image to create multiple different sizes so you'd need to rely on the browser's algorithms to dynamically resize the image as and when required.)

Thanks for the help - it worked really well.

You're welcome!

I'm sorry that you've not been able to resolve your problem.
It does seem to be some kind of server setup issue.
If I view the source of the gallery's web page in a browser and click on the 'src' attribute's value for any <script> tag, I should be able to see the contents of the file but, for every JavaScript file I've checked, the server just displays the site's error 404 (file not found) page.
Likewise, I cannot view the gallery's dynamically-generated XML data in isolation either. The same error 404 is returned. (This is in a desktop browser.)
It looks like the server might have some kind of hotlink protection for JavaScript and XML files (and possibly other file types) which could certainly be preventing the gallery from being displayed. If a browser cannot access a gallery-specific file directly, then Juicebox will not be able to see it either.
A change of web host might be the best course of action if the current host is unwilling or unable to help.

549

(7 replies, posted in Juicebox-Pro Support)

You could place your icon into the 'template/jbcore' folder, (JuiceboxBuilder-Pro copies the entire 'template/jbcore' folder across to the gallery folder), e.g.:
Mac: /Applications/JuiceboxBuilder-Pro.app/Contents/Resources/template/jbcore/icon.png
Windows: C:\Program Files (x86)\JuiceboxBuilder-Pro\template\jbcore\icon.png

Your <link> tag would then look something like this (with a relative path to the icon file within the gallery's 'jbcore' folder):

<link rel="apple-touch-icon" href="jbcore/icon.png"/>

Use a similar path for any other <link> tags you use.

550

(2 replies, posted in Tricks and Tips)

Just a couple of quick clarifications and expanded explanations:

None of which are in the Config Guide.

All the configuration options which are used by Juicebox when the gallery is displayed in a browser (i.e. those options which make a difference to the layout and functionality of a gallery) are included in the Config Options page.
JuiceboxBuilder-Pro does write some extra settings to the gallery's 'config.xml' file which are not included in the Config Options page.
These settings mostly refer to image generation and are included so that if the gallery is opened and edited by JuiceboxBuilder-Pro in the future, the same image settings (e.g. dimensions and quality) will be used.

Side Note: config.xml and index.html are really a pair of files to be considered together. JbB changes both files depending on settings selected.

All configuration options (required by both Juicebox and JuiceboxBuilder-Pro) and image data are stored in the gallery's 'config.xml' file.
The 'index.html' file contains just the gallery's embedding code and the SEO Content (if the 'Add SEO Content' checkbox is selected in JuiceboxBuilder-Pro's 'Customize -> Sharing' section).
The SEO Content contains the image paths, titles and captions.
The only configuration options that are stored in the embedding code are the Embed Options, backgroundColor, galleryWidth and galleryHeight.
JuiceboxBuilder-Pro writes values for these options to the 'config.xml' file (again options which are not used by Juicebox when the gallery is displayed) so that the application's interface can be populated with the correct values when the gallery is opened for editing.
(JuiceboxBuilder-Pro reads only the gallery's 'config.xml' file (and not the 'index.html' file) on opening a gallery so all data required to recreate a gallery is stored in the 'config.xml' file.)

Now, there will always be a setting for 'show open button' in your config.xml.

As you correctly mention, default values do not need to be written to the 'config.xml' file.
If a particular configuration option is not present in the 'config.xml' file, then Juicebox will use the option's default value.
If you reset an option to its default value using its own input field (e.g. checkbox or combobox), then the option will remain in the 'config.xml' file (with the correct default value).
However, if you reset an option's value using the 'cross-in-a-circle' icon to the right of the option (in JuiceboxBuilder-Pro's interface), then the option will be removed from the 'config.xml' file.
Essentially, if a value is set by the user (even to a default value), then the option will be present in the 'config.xml' file.

I don't know what performance that might make on slower, low powered devices.

Having all configuration options listed in a 'config.xml' file really won't make any noticeable difference in a real-world scenario and is nothing to worry about.