Thanks for letting me know. I hope you get on OK.
Please keep me posted.
You are not logged in. Please login or register.
Juicebox Support Forum → Posts by Steven @ Juicebox
Thanks for letting me know. I hope you get on OK.
Please keep me posted.
There's nothing wrong with using an iframe but there are some drawbacks to doing so (which are noted here... scroll down to "2) Using an iframe") so I'd always recommend embedding directly into a web page (following either the regular embedding instructions or the baseUrl embedding instructions) where possible.
If you run into any difficulties, then perhaps you could let me know a little more about how you are trying to embed your gallery (maybe an example would help me to understand your scenario better) and I'll try to help further.
I have been using 1.5.1. I just sent a link to a smaller site that didn't have photos that I didn't want going public.
OK, thank you for the information.
From what I've read, Safari should support HTML5 download.
I put up an HTML5 download test, and it works with Safari.
Safari does now support the HTML 5 'download' attribute but, at the time the Download Button functionality was written for Juicebox-Pro, it is very possible that it did not (which would explain why Juicebox-Pro uses the PHP implementation for Safari).
In any case, it should work (regardless of the implementation being used).
Check out the Download Button in our demo gallery here.
If this works in your Safari browser, then the problem likely lies somewhere within your web server's set up and the error message you see ("This error was generated by Mod_Security.") certainly suggests that Mod_Security is at the root of your problem. It sounds like a custom Mod_Security rule is interfering with (and blocking) the PHP download process.
Please check in with your web host to find out what custom Mod_Security rules are being applied to your hosting account (and where they are being set).
You may need to temporarily remove them one-by-one (checking the Download Button's functionality after removing each one) to find the Mod_Security rule causing your problem.
If you find that the Download Button does not work in our demo gallery in your Safari Browser, then please let me know and I will notify the developers.
Thank you.
@adec
ah thanks!
You're welcome! I'm glad this thread has helped you out.
now just need to embed it into a local website to make sure it works there.
I hope all goes well. Just let me know if you run into any difficulties and I'll do my best to help you out.
For reference, the Embedding Guide is here.
@jcisaacs3
I'm sorry to hear that you are having trouble with Juicebox-Pro.
Hopefully my noted below will help.
Thank you for providing the URL to your website
Just for the record, I have been able to successfully use the Download Button in your gallery in all major up-to-date browsers on my Windows 10 PC (Edge, Chrome, Firefox, Internet Explorer, Opera).
It looks like the only browser in which the Download Button fails is Safari.
I notice that your gallery uses Juicebox-Pro v1.5.0.
Please try upgrading your gallery to the latest version (v1.5.1) as many bugs have been fixed since v1.5.0 and upgrading may fix your problem without any further action.
Full instructions for upgrading JuiceboxBuilder-Pro and existing galleries can be found on the Upgrading Juicebox support page.
I realise that the only fix regarding the Download Button listed in the Version History does not seem relevant to your problem but the code for the Download Button has changed since v1.5.0 so upgrading may still be worth a try.
I hope that upgrading your gallery helps.
Otherwise, the error message you see relates to Mod_Security so please check your web server's .htaccess files to see what Mod_Security rules are in place and which might be interfering with Juicebox's download functionality.
Just for clarification, your gallery's 'config.xml' file looks fine (all linkURL entries are blank).
Also, when you say that the Download Button works in Chrome and Firefox, this could be because these browsers use the HTML 5 'download' attribute rather than the PHP implementation of the download functionality. (Juicebox includes both methods of download to support browsers which do not support the HTML 5 'download' attribute.)
In any case, I hope that my notes above help.
Please let me know how you get on and if I can be of any further assistance.
What you are seeing in Firefox is the gallery being displayed in Small Screen Mode (where thumbnails and main images are displayed on separate pages).
Small Screen Mode is usually used only on mobile devices (or when Small Screen Mode is forced by setting screenMode="SMALL").
(More information on Screen Modes can be found in the Gallery Tour here.)
If all three screenshots are from the same gallery, then screenMode must be set to AUTO, otherwise a certain Screen Mode (either Large or Small) would always be used on all devices and in all browsers, so something must be triggering Small Screen Mode to be used in your Firefox browser.
Here are a few things to check:
Check that your Firefox browser is not in 'Tools -> Web Developer -> Responsive Design Mode'.
Check that your 'View -> Zoom' is set to 100% and not zoomed in or out.
Check that you do not have any browser extension installed and active which is currently changing the User-Agent string (for example, to mimic a mobile device).
I hope that this helps or at least points you in the right direction.
Hi.
This is a support forum for the Juicebox-Pro web gallery software from SimpleViewer Inc.
From your query, it sounds like you are referring to a 'JuiceBox' from eMotorWerks, a completely unrelated company to our own (although the product names are the same).
I do not know if they have a forum but you should be able to contact eMotorWerks directly via their online form here: https://emotorwerks.com/contact
I hope this points you in the right direction.
@mrp
Yes. You can set most configuration options in either the 'config.xml' file or the embedding code.
( I usually recommend setting options in JuiceboxBuilder-Pro as it seems to be the most popular method of creating and editing galleries and it does not involve any manual code editing.)
Please see the Setting Config Options support section for further details.
The only configuration options that must be set in the embedding code rather than the 'config.xml' file are listed in the Embed Options.
All other options can be set in either the 'config.xml' file or the embedding code.
(If an option is set in both the 'config.xml' file and the embedding code, then the value in the embedding code takes precedence over the value in the 'config.xml' file.)
Are there any known problems getting the Pro version to work with the Juicebox module?
There are no problems using Juicebox-Pro with the Juicebox Module for Drupal. Just follow the 'Installation Instructions' here.
When you reach Step #3, be sure to use the files inside the 'jbcore' folder from the Juicebox-Pro v1.5.1 zip package ('juicebox_pro_1.5.1/web/jbcore/').
Please note that upgrading the module to Juicebox-Pro will not change the module's interface.
There will be no additional interface options for setting Pro configuration options (like JuiceboxBuilder-Pro or the Lightroom Plugin).
However, you can configure your gallery as you like by entering individual Pro Options in the 'Juicebox Library - Pro / Manual Config' section of your Drupal Dashboard ('Home -> Administration -> Structure -> Content types -> Article -> Manage Display -> Juicebox settings').
Can I create a gallery with the thumbnail tool on the right side with the Juicebox module?
I am not familiar with the thumbnail tool you refer to so I guess this query is one for Ryan to field over in the Drupal forum.
Can I remove the large whitespace above a gallery?
First of all, please check with your browser's developer tools to see whether the whitespace you refer to is inside or outside the gallery.
If it is inside the gallery, then the space could be due to setting your gallery's height to 100%. If the gallery's parent container has no height specified via CSS, then the gallery's actual height could be 100% of the browser window height. The main images could already be scaled as large as possible within the gallery's image area (if they were scaled any larger, then cropping might occur), leaving space above and below the main images.
Try reducing your gallery's height. Try a fixed pixel value such as 600px to see if this helps.
The gallery will still be responsive in the horizontal dimension (dependent on your web page layout and the dimensions of all parent containers) but will have a fixed height.
However, this is not usually a problem for a web page which scrolls vertically.
Elements in a vertically scrolling web page usually have a fixed height (the height of elements does not usually change when scrolling down a page).
Please also see this FAQ:
My Juicebox gallery shows too much space above or below the main image, how do I fix this?
Can I remove the juicebox logo on the mobile display?
Yes. Just use Juicebox-Pro. All Juicebox-Lite galleries feature the Juicebox logo in the lower right corner. This branding is not present in any Juicebox-Pro galleries.
I am working on an intranet site that may not allow the server to have Internet access. Does it call home (require internet connection etc) for any reason...
Juicebox-Lite contacts our web server only to fetch the logo (for the lower right corner of the galleries). Juicebox-Pro does not call home at all.
... and will it not work if it cannot call home etc?
Both Juicebox-Lite and Juicebox-Pro will both work without an internet connection. Please see the following FAQ regarding local viewing, though.
When I view my gallery locally, I see the message "Juicebox can not display locally in this browser". Why?
Also, please see this additional note for local viewing in Safari 11 and this additional note for local viewing in Firefox 68.
I am constantly creating and deleting test environments. Is my Pro version tied to a specific site?
No. You do not actually need to inform us of the websites that you use Juicebox-Pro on.
We ask only that you abide by the Terms of Use and upload Pro galleries to only as many website domains as your license allows.
For example, if you have a 5-Site License, then you are free to change the website domains that you upload Pro galleries to at any time you like without notifying us and, as long as you have Pro galleries uploaded to no more than 5 different website domains at any one time, that is fine.
I don't want to have to deal with relicensing it every time I build a new test site.
Please see this FAQ:
How many websites can I use Juicebox-Pro on?
Licenses are only required for publicly accessible domains, so staging and testing domains do not require an additional license.
I hope my notes above help to clarify things.
Please let me know if you have any further queries.
My apologies, the test site is on my PC and I put it into sleep when I go to bed. That URL should be working again for the next 15 hours or so.
Still no joy with the URL I'm afraid...
I hope that Ryan (or another Drupal Juicebox Module user) can help you out over in the Drupal forum but I suspect that trying to integrate my solution into the module will not be an easy task.
Maybe there's a different solution that a user of the bootstrap tab system that you use can recommend (perhaps they have experienced a similar issue with other HTML elements embedded into the tabs ).
Being that the problem resolves itself when the browser is resized, you could perhaps manually trigger a resize when your tab is clicked. (Such a solution would be independent of Juicebox and the module's code.)
Try adding the following code to your web page:
<script>
$(document).ready(function() {
$('#gallery_tab').click(function() {
$(window).trigger('resize');
});
});
</script>
Again, this assumes that your 'Gallery' tab has an id="gallery_tab". (If not, then just change #gallery_tab in the code above to the correct 'id' for your 'Gallery' tab.)
It also assumes that jQuery is loaded into your web page. (Juicebox comes bundled with its own version of jQuery so as long as the code is run after the 'juicebox.js' file is loaded into your web page, then all should be fine.)
Please note that this proposed solution has not been tested so I do not know whether it will work or not, but it should be a fairly quick and easy thing to try (as long as you can get the JavaScript code into your web page).
Thanks!
Edit:
For others reading this thread, although I have notified the developers, unless the 'juicebox.js' file is repacked using a different method, it will always trigger the Content Security Policy eval warning.
If you have a CSP in place and want to retain it whilst still allowing Juicebox to run, then you'll need to add 'unsafe-eval' to your CSP (and also 'unsafe-inline', too, if your gallery's embedding code is inline and not in an external JavaScript file.)
Relaxing the CSP to suppress warnings is not ideal by any means but I thought I should mention this in case it helps anyone.
I get a lot of errors on the javascript console such as
I realise that in an ideal world, it would be great to have no '[Violation]' entries in the console but it is worth remembering that these entries are only present in Chrome and only when the debugging level is set to 'Verbose'. (They are not classed as 'Errors', 'Warnings' or even 'Info'.)
Just out of curiosity, I loaded a few popular web pages into Chrome (adobe.com, amazon.com, apple.com, microsoft.com, mozilla.org) and they all display '[Violation]' entries (of one type or another, some more than others) in 'Verbose' mode.
Of course after completing it I find I can't get rid of the 'unsafe-eval' in the policy
That's down to the way that the 'juicebox.js' file is packed which is a choice that the developers have taken.
The 'juicebox.js' file uses eval() and CSP does not allow the use of eval() ("Eval and related functions are disabled") so, unfortunately, Juicebox will not be fully compatible with CSP guidelines.
There really is nothing that can be done about this (at user level) at the moment, although I have notified the developers of this so it is in their hands now.
I didn't realise that you had so many galleries! Hopefully you'll be finished by now.
I'm glad you've made the choice of having al your galleries share a single 'jbcore' folder (as documented here).
This will make updating all your galleries (when a new version of Juicebox is released) a simple matter of replacing just one 'jbcore' folder on your web server (instead of 233).
(I mention this just in case anyone else reading this thread also has a lot of galleries and is not aware that multiple galleries can share a single 'jbcore' folder.)
Unfortunately, the URL you provided does not work so I cannot see your gallery's web page.
I don't really know where to apply the code...
If, for example, you are following the regular embedding instructions here, then you would just use the embedding code I provided (changing the gallery dimensions and background color as necessary) instead of the embedding code provided on the 'Publish' tab of JuiceboxBuilder. (It would just be a simple swap of code.)
Without being able to see your gallery's web page, I do not know how you are currently embedding your gallery.
If you are using the baseUrl method (which you might be using if you are following the Embedding in a Drupal Site instructions), then just amend the path to your 'juicebox.js' file and add the baseUrl entry (pointing towards the gallery folder) to the modified embedding code, for example:
<!--START JUICEBOX EMBED-->
<script src="/galleries/gallery1/jbcore/juicebox.js"></script>
<script>
function loadGallery() {
new juicebox({
baseUrl: "/galleries/gallery1/",
containerId: "juicebox-container",
galleryWidth: "100%",
galleryHeight: "600px",
backgroundColor: "#222222"
});
}
$(document).ready(function() {
$('#gallery_tab').click(function() {
loadGallery();
});
});
</script>
<div id="juicebox-container"></div>
<!--END JUICEBOX EMBED-->
However, if you are using the Juicebox Module for Drupal, then putting the embedding code into a JavaScript function and adding custom code to call the function when an element on your web page is clicked is not going to be easy. The module automatically embeds the gallery into your web page and you'd need to modify the module's source code to achieve this.
There are a couple of reasons why this may not be feasible, though.
(1) The Juicebox Module for Drupal was not written by ourselves and, as such, I am not overly familiar with the module's source code (and do not know how easy or difficult such a modification would be). Support for the module would be better directed towards the Drupal forum where the author of the module (Ryan Jacobs) might be able to help further.
(2) The Juicebox Module for Drupal uses a non-standard embedding method (it does not just drop the regular embedding code into the web page) so swapping the module's embedding code for my modified embedding code above is not going to be possible.
If you really need to get this working with your tabs, then I'd recommend following the Embedding in a Drupal Site instructions and using the modified baseUrl code that I posted above. Just make sure that both paths in the code (the path to the 'juicebox.js' file and the baseUrl entry, pointing towards the gallery folder) are correct.
Using fixed size in pixels does indeed fix the loading problem at the cost of responsiveness, but that's too much of a price to pay unfortunately.
It sounds like we're on the right track.
Regarding this suggestion, can you provide any more guidance please?
Sure!
Usually, your embedding could would look something like this:
<!--START JUICEBOX EMBED-->
<script src="jbcore/juicebox.js"></script>
<script>
new juicebox({
containerId: "juicebox-container",
galleryWidth: "100%",
galleryHeight: "600px",
backgroundColor: "#222222"
});
</script>
<div id="juicebox-container"></div>
<!--END JUICEBOX EMBED-->
Put the JavaScript section into a function and add an event listener (a click handler) to call the function (to load the gallery) when your 'Gallery' tab is clicked.
If, for example, your 'Gallery' tab has an id="gallery_tab", then your embedding code would look something like this:
<!--START JUICEBOX EMBED-->
<script src="jbcore/juicebox.js"></script>
<script>
function loadGallery() {
new juicebox({
containerId: "juicebox-container",
galleryWidth: "100%",
galleryHeight: "600px",
backgroundColor: "#222222"
});
}
$(document).ready(function() {
$('#gallery_tab').click(function() {
loadGallery();
});
});
</script>
<div id="juicebox-container"></div>
<!--END JUICEBOX EMBED-->
I hope this helps.
However, if you continue to experience difficulties, then please post the URL to your gallery's web page so that I can take a look at your gallery's environment live on your web server and hopefully help further.
Thank you.
It sounds like, when the Juicebox gallery is loaded into the gallery container, the gallery container may exist on the web page but with no dimensions (being that it is not visible until the 'Gallery' tab is clicked). If the gallery has a galleryWidth of '100%' but the gallery container has no dimensions, then the gallery's actual width will be 100% of zero.
One possible solution would be to put the Juicebox embedding code into a JavaScript function and then call the function when the 'Gallery' tab is clicked (after the gallery container has been assigned dimensions).
Another possible solution might be to give your gallery a fixed pixel galleryWidth (for example '800px'), although this will prevent the gallery from being responsive in the horizontal dimension (which may or may not be a problem depending on the design and layout of your web page).
I hope this points you in the right direction.
Thanks for your help.
You're welcome!
I figured it was hidden deep within the juicebox.js script and while it can be pretty printed I wasn't eager to go look.
Whilst you could technically decompress and pretty-print the 'jucebox.js' file, it still probably wouldn't make a lot a sense (a lot of descriptive variable names are changed in the compression process) and modification of the source code is not supported (see this FAQ). We'll need to wait for the developers on this one.
Now to change all those references to the inline script :-)
I hope you've not got too many to do!
Thanks! That has fixed that problem.
That's great! Thank you for letting me know.
On Chrome I'm still seeing a problem listed (which Firefox doesn't mention)
I see the 'Violation' entries in Chrome when setting the debugging level to 'Verbose'.
Unfortunately, there is nothing that a user can do to address this as the code which the 'Violation' entries refer to is buried deep within the 'juicebox.js' JavaScript file which is obfuscated and cannot be modified.
However, I have notified the developers who will investigate the issue.
Also curiously the button bar is shorter on 1.5.1 and so wraps onto a second line, which is annoying.
The Button Bar should not wrap unless there is not enough space for all buttons to be displayed on a single line.
I have created a test gallery (using the same configuration options that your gallery uses) and the Button Bar does not wrap there.
I notice that your 'juicebox.js' file is now v1.5.1 but your 'theme.css' file ('/juicebox/jbcore/classic/theme.css') is still v1.4.4.
Please ensure that all files within your gallery's 'jbcore' folder are up-to-date (v1.5.1) by replacing the existing 'jbcore' folder on your web server with the 'jbcore' folder from the Juicebox-Pro v1.5.1 zip package ('juicebox_pro_1.5.1/web/jbcore').
This should hopefully solve your problem.
Thank you for providing the URL to your gallery's web page.
The <script> tag loading your 'juicebox-gallery.js' file is not closed and everything after it, up until the next closing </script> tag on your web page (including the 'juicebox-container' <div>), is being treated as JavaScript by the browser (so there is essentially no container on your web page for the gallery to be loaded into).
(Sorry I did not notice this in your post above. It was much easier to catch with syntax highlighting in my browser.)
Change:
<script src="/scripts/juicebox-gallery.js" id="juicebox" data-page="travel/manila">
... to:
<script src="/scripts/juicebox-gallery.js" id="juicebox" data-page="travel/manila"></script>
Hopefully this will resolve your problem.
It looks like what you are doing should work.
In fact, I have just recreated your setup and it works for me, without any console errors.
The console errors you are seeing may be unconnected to the passing of the data value.
"Cannot read property 'trySetContainerSize'" certainty sounds like a problem with Juicebox being unable to size the gallery correctly.
Please post the URL to your gallery's web page so that I can see the problem for myself.
Once I'm able to see the problem live on your web server, I might be able to determine the exact cause of the problem and propose a solution.
Thank you.
Also, if you are not already using the latest version of Juicebox-Pro (v1.5.1), then please try upgrading your gallery to see if this helps.
(I have been using Juicebox-Pro v1.5.1 in my own tests and have not seen the console errors you reported.)
If necessary, full instructions for downloading the latest version of Juicebox-Pro and upgrading existing galleries can be found in the Upgrading Juicebox support section.
Incidentally, shareURL is not a configuration option that needs to be set in the gallery's embedding code.
It is used only by JuiceboxBuilder-Pro to set valid Open Graph meta tags in the gallery's 'index.html' web page.
shareURL is included in a gallery's 'config.xml' file simply so that JuiceboxBuilder-Pro can read it when the gallery is opened for editing.
(shareURL is not used by Juicebox when a gallery is displayed.)
If you do not want to use a query string (or a #) to pass a parameter via a URL, then I'm not exactly sure how you want to pass a parameter to the script (intended to avoid using inline JavaScript) without actually using inline JavaScript to pass the parameter.
You could perhaps set a session cookie (and grab the cookie's contents from within the script) but then you'd probably need separate scripts (to avoid using inline JavaScript) to set the cookie's functions and to set the cookie's contents (and it all seems to be overcomplicating matters somewhat).
HTML:
<!DOCTYPE html>
<html lang="en">
<head>
<title>Juicebox-Pro Gallery</title>
<script src="jbcore/juicebox.js"></script>
<script src="cookie.js"></script>
<script src="create_cookie.js"></script>
<script src="script.js"></script>
</head>
<body>
<div id="juicebox-container"></div>
</body>
</html>
'cookie.js':
function createCookie(name, value) {
document.cookie = name + '=' + escape(value) + '; path=/';
}
function readCookie(name) {
var re = new RegExp('(?:^|;)\\s?' + name + '=(.*?)(?:;|$)', 'i'), result = document.cookie.match(re), output = null;
if (result != null) {
output = unescape(result[1]);
}
return output;
}
function eraseCookie(name) {
var d = new Date();
document.cookie = name + '=; path=/; expires=' + d.toUTCString();
}
'create_cookie.js':
createCookie('base', '/galleries/gallery_1/');
'script.js':
var base = readCookie('base');
eraseCookie('base');
new juicebox({
baseUrl: base,
containerId: 'juicebox-container'
});
I guess this might not help as it still leaves us with the problem of how to get the parameter into the 'create_cookie.js' script without using inline JavaScript. It just shifts the problem around a bit (and avoids using a query string).
I do not know how (or where) your baseUrl and shareUrl parameters are being generated but if they are already being generated in another external script, then maybe you could just set the cookie directly from within this script (and it could still be read from the 'script.js' file above).
If you just want to set a global JavaScript variable for your parameter, then the problem still exists (at least in my own understanding) of how to set it without using inline JavaScript. I guess I really need to know how and where your baseUrl and shareUrl parameters are being generated so if you could please elaborate on that, then it might help me to try to formulate a solution.
Thank you.
I hope this helps (or at least gives you a little more food for thought).
You should be able to move the entire JavaScript embedding code into a separate script and then just load this script after loading the 'juicebox.js' script.
I think this should work OK.
At its most basic:
HTML:
<!DOCTYPE html>
<html lang="en">
<head>
<title>Juicebox-Pro Gallery</title>
<script src="jbcore/juicebox.js"></script>
<script src="script.js"></script>
</head>
<body>
<div id="juicebox-container"></div>
</body>
</html>
'script.js':
new juicebox({
containerId: 'juicebox-container'
});
I'm not sure what parameter you'd like to pass in the URL but you could do so with a query string, e.g.:
http://www.example.com/index.html?text=hello
You could then fetch the query string parameter from within the script using code such as:
if (window.location.search) {
var key = 'text';
var queryArray = {};
var queryComponent;
var queryString = unescape(window.location.search);
var re = new RegExp('([^?=&]+)(?:=([^&]*))?', 'g');
while (queryComponent = re.exec(queryString)) {
queryArray[queryComponent[1]] = queryComponent[2];
}
var value = queryArray[key];
// Do something with 'value' variable ("hello" in the example above)
}
(This may not be the most compact/optimized code for fetching a query string but it does handle multiple query string parameters.)
I'm not sure if this is exactly what you are looking for but it might point you in the right direction.
There is no way to auto-translate image titles and captions.
You'd really need to set up a separate XML file for each language that you want to support (same image data in each one, just with image titles and captions in different languages).
You could then load the gallery with the appropriate XML file using a configUrl (and a JavaScript variable) in the gallery's embedding code. (The configUrl option is noted in the Embed Options.)
For example, to support English, French and Spanish, you could have three XML files named 'config_english.xml', 'config_french.xml' and 'config_spanish.xml'.
You could then use something like the following:
<!--START JUICEBOX EMBED-->
<script src="jbcore/juicebox.js"></script>
<script>
var lang = navigator.language.substring(0, 2).toLowerCase();
var file;
switch(lang) {
case 'en':
file = 'config_english.xml';
break;
case 'fr':
file = 'config_french.xml';
break;
case 'es':
file = 'config_spanish.xml';
break;
default:
file = 'config_english.xml';
break;
}
new juicebox({
configUrl: file
containerId: "juicebox-container",
galleryWidth: "100%",
galleryHeight: "100%",
backgroundColor: "#222222"
});
</script>
<div id="juicebox-container"></div>
<!--END JUICEBOX EMBED-->
For reference, navigator.language is documented here.
I hoe this helps or at least points you in the right direction.
(The code above could certainly be optimized but I've tried to make it easy to read and understand.)
Many thanks for the suggestion (for a Juicbeox-Pro equivalent to SimpleViewer-Pro's thumbNavStyle="NUMERIC").
I've copied your post to the Feature Requests thread (here) where it will be seen by the developers.
I know that I've already mentioned this to yourself in an email but for anyone else reading this thread, it should be possible to achieve something like this manually using the Juicebox-Pro API (with help from the showThumbPage method) but knowledge of HTML and JavaScript would be required and you might need to get a little creative with the styling (SimpleViewer-Pro's thumbNavStyle="NUMERIC" used an ellipsis when too many thumbnail pages existed for there to be a link to every single one at once) and you might also need to overcome potential pitfalls along the way (such as the fact that the number of thumbnail pages may change in a responsive gallery if the browser window dimensions change).
An automated solution built-in to Juicebox-Pro would undoubtedly be easier to setup and use so thank you for the suggestion.
(Just a quick disclaimer, though, that I do not know what suggestions will be picked up by the developers and implemented in future versions.)
Feature request (for Juicebox-Pro equivalent to SimpleViewer-Pro's thumbNavStyle="NUMERIC") from Theorangepaper (original thread):
Navigation tool for thumb pages
Created with svBuilder-Pro I had a gallery of 2,626 historic Spanish orange crate labels diaplayed in my virtual Orange Wrapper Museum OPIUM www.opiummuseum.de. On the left hand side I definded a thumb area of 6 x 8 resulting in 55 thumb pages. Below the thumbs I placed a small navigation bar which gave the visitor direct access to any of the 55 thumb pages and thereby to any of the 2,626 main images. A visitor could easily arrive at any rear part of this large gallery or even hop to its very end.
It seems to me that there is no comparable navigation tool available in JuiceboxBuilder-Pro. To arrive at rear parts of a gallery or even hop to its end one has to sequentially run through the main images or at least through the thumb pages. In small galleries this might not be overly important. But the larger a gallery gets the more it becomes tedious and time demanding to run through it sequentially and the more important would it be to have random access to all images of the gallery. I therefore suggest to add a complete small navigation tool across the thumbs to JuiceboxBuilder-Pro.
To clarify what I mean I have prepared a comparison of a small gallery with 231 images only created with svBuilder-Pro with the same gallery created with JuiceboxBuilder-Pro. You can view it here, if you want: www.opiummuseum.de/spankist.vergleich.htm . But please imagine the gallery had not 231, but 2,626 entries.
Dirik von Oettingen
Germany
Juicebox Support Forum → Posts by Steven @ Juicebox
Powered by PunBB, supported by Informer Technologies, Inc.