You are not logged in. Please login or register.
Juicebox Support Forum → Posts by Steven @ Juicebox
Please post the URL to your gallery's web page so that I can try to see the problem for myself. Thank you.
If the gallery displays OK in Firefox, then it sounds like a problem specific to your Safari browser.
Try completely clearing your Safari browser's cache before reloading your gallery's web page. This might help.
Also, if you have any extensions installed in your Safari browser, try temporarily disabling them to see if this makes a difference.
Unfortunately, this is a known problem (please see this forum thread) which affects Edge and IE11 but not Chrome, Firefox, Opera or Safari. However, the developers are aware of the issue and hope to have it fixed for the next version.
In the meantime, I've posted a possible workaround in this forum post. It's not ideal but it might tide you over until the bug is fixed. Thank you for reporting it.
What you see when you disable JavaScript is likely to be the Search Engine Optimization (SEO) code which is included on the web page within <noscript> tags and is displayed if JavaScript is disabled in the browser (and the true Juicebox gallery cannot be run).
If you want to protect a gallery from the general public, then it is perhaps also likely that you will not want search engines indexing your gallery page's content so I would recommend that you remove the SEO code from your web page when using Juicebox's built-in Password Protection. (When creating a gallery with JuiceboxBuilder-Pro, deselect the 'Add SEO Content' checkbox from the 'Customize -> Sharing' section.)
As you point out, an alternative method of securing a gallery would be to password protect the gallery's directory on the web server using .htaccess and .htpasswd files. Instructions can be found here. You might also be able to password-protect a directory on your web server from within your web hosting account's online Control Panel (without having to manually set up .htaccess and .htpasswd files.
That would be nice to see it in the next version ;)
Please feel free to post ideas for future versions in the Feature Requests forum thread.
This keeps all the ideas together and ensures that they are not overlooked by the developers.
Thank you.
You're welcome!
I'm glad I could help.
Incidentally, if you were escaping your text with the PHP function htmlentities() before outputting it, you might like to try using htmlspecialchars() instead. htmlspecialchars() will convert only special characters (&, ", ', < and >) to HTML entities (just enough to prevent breaking the XML syntax) whereas htmlentities() will convert all applicable characters to HTML entities (which might be breaking your 'ß' character).
That's great!
Thank you for letting me know.
Juicebox can display characters other than regular alphanumeric characters (i.e. non Latin characters and non Arabic numerals) throughout a gallery.
Check out this demo Juicebox-Lite gallery which has Chinese characters in both the Gallery Title and the image titles and captions.
Take a look at your gallery's configuration file in a browser (open your gallery's 'loadRefGallery.php?refID=xyz' file directly in a browser) and view the source of the page to see exactly what your PHP script is generating and outputting to the dynamically generated content.
It's possible that the 'ß' character is being escaped (before being output) and that this may not be necessary.
As long as the 'ß' character actually appears (not in an escaped form) in the Gallery Title and/or image titles and captions in the configuration file, then it should also appear in the gallery itself.
Also, if you are trying to use ß, then as the '&' character is an XML entity that needs to be escaped in an XML file, you might need to escape the '&' character within ß to & and then use &szlig; instead (but using 'ß' directly should also work fine).
Please see the following FAQ. (There are a couple of links in the FAQ which might be useful.)
Can Juicebox handle a custom data source, for example RSS or Instagram?
Every Juicebox gallery must have a 'config.xml' file (where the gallery's configuration options and image data are stored).
However, the 'config.xml' does not need to be a static file created when the gallery is authored. It can be generated dynamically (by a server-side scripting language such as PHP) at the time the gallery is displayed.
You'd need to point Juicebox towards a PHP (or alternative language) script using a configURL entry in your gallery's embedding code, for example:
<!--START JUICEBOX EMBED-->
<script src="jbcore/juicebox.js"></script>
<script>
new juicebox({
containerId: "juicebox-container",
galleryWidth: "100%",
galleryHeight: "100%",
backgroundColor: "#222222",
configUrl: "config.php"
});
</script>
<div id="juicebox-container"></div>
<!--END JUICEBOX EMBED-->The output of the 'config.php' file would need to be in the format of a regular Juicebox 'config.xml' file but, within the script, you could pull in data from whatever source you like (such as a MySQL database).
It would certainly be possible to do but knowledge of PHP (or similar) and how to query your database would be required.
There is a simple example of a dynamically generated configuration file (to display images from a designated web server directory) in this forum post which might help.
I hope this points you in the right direction.
Juicebox-Pro does not use a key or serial number (although downloads are restricted to licensed users only).
If you still have a copy of the Juicebox-Pro zip file, you can just transfer it across to your new computer on a USB flash drive.
You can then unzip the file and install JuiceboxBuilder-Pro on your new computer following the installation instructions here.
If you need a new copy of the Juicebox-Pro zip file, you can download it again using the link from your purchase email. (The download link always points towards the latest version rather than the version you purchased.)
If you no longer have access to your purchase email, then please fill in this Download Link Request Form to the best of your ability and the admin team will send you a new download link.
Incidentally, you can install JuiceboxBuilder-Pro on up to 3 different computers, as noted in this FAQ:
Can I install on multiple computers?
I'm glad you've been able to figure it out. Thank you for letting me know.
Just for clarification (and for others who might be having rouble opening existing galleries with JuiceboxBuilder), when you click the 'Open Gallery...' button, you should navigate towards and select the gallery folder (rather than a specific file within the gallery folder).
However, the gallery folder must contain the gallery's XML file and the XML file must be named 'config.xml' (the default filename as used by JuiceboxBuilder). If you have moved or renamed the XML file, the gallery will not be able to be opened by JuiceboxBuilder.
I'm glad to hear that setting a flickrSetId has proved to be a suitable workaround for you.
Thank you for letting me know.
Now I've moved my photos to the Nextgen gallery, but showing them with Juicebox.
This is a work around that's working.
I'm glad that you've found a suitable workaround (although it is unfortunate that the Flickr sorting is not working for you as expected).
Here are a couple of alternative workarounds:
(1) Try creating a Flickr set from your images. Flickr sets are always returned in the order specified on the Flickr set page. (If you specify a flickrSetId, then the flickrSort option will not be used.) This should hopefully allow you to continue to use Flickr as the image source. Please see this FAQ for information on how to order images in a Flickr set: How do I change the order of images in a Flickr Photo Set?
(2) You could use the WordPress Media Library as the image source. WP-Juicebox displays all images uploaded to the post containing the gallery so you could upload the images (via the 'Add Media' button when editing the post). You can then go to 'Uploaded to this post' (within the media window) and drag and drop the thumbnails into the order you want them to be displayed in your gallery. (WP-Juicebox displays images in the order in which they appear in the 'Uploaded to this post' section.)
You're welcome.
Please feel free to post suggestions for future versions in the Feature Requests forum thread.
This keeps all the ideas together and ensures that they are not overlooked by the developers.
Thank you.
... this is the best way I have figured out to make it work for us.
If it works for you, that's absolutely fine: stick with it!
You show in your Demo only one gallery, is it possible to have more than one gallery ?
Yes. Please check out the Embedding Multiple Galleries support section.
There are online examples of embedding multiple galleries on a single web page and on separate web pages (and also an example of switching between galleries on a single web page).
Is-it possible to access to those gallery with navigation menu ?
With Juicebox-Pro, you can create as many individual galleries as you like. However, if you would like to link them all together (with a navigation menu), then you would need to do so manually following the examples in the Embedding Multiple Galleries support section (link above).
If you are looking for an automated solution to creating and listing multiple galleries, then we have another product that you might be interested in called Showkase.
Showkase is a PHP web application which allows you to create a complete portfolio web site (integrating multiple galleries) online.
Showkase has full support for Juicebox-Pro (and SimpleViewer-Pro) galleries and the galleries can be created within the application itself in a web browser interface (or created with JuiceboxBuilder and imported).
You can create Gallery Index pages and have as many galleries listed on each Gallery Index page as you wish.
Each gallery is represented by a thumbnail image with the gallery title displayed below and the gallery is opened when the user clicks on the image.
Demo sites created with Showkase can be found here and a sample Gallery Index page can be found here.
Showkase can also create non-gallery pages (About, Basic and Contact pages) where you can add information about yourself (or any other content you like).
All of this is done automatically within the Showkase interface without the need for any manual coding at all.
Showkase can be purchased as Showkase-Standard (which comes with Juicebox-Lite and SimpleViewer-Standard, the free versions) or Showkase-Pro (which comes with Juicebox-Pro and SimpleViewer-Pro).
The only difference between Showkase-Standard and Showkase-Pro is the bundled viewers.
More information on the differences between Juicebox and Showkase can be found in this forum post.
I hope this helps.
captionHAlign is a Large Screen Mode option only (this is noted in the short description of the option on the Config Options page) and your gallery is always displayed in Small Screen Mode (by setting screenMode="SMALL") so the option is not used in your gallery.
If you like, you could try adding the following CSS to the <head> section of your gallery's web page:
<style type="text/css">
/* IMAGE TITLE */
.jb-caption .jb-caption-title {
text-align: center !important;
}
/* IMAGE CAPTION */
.jb-caption .jb-caption-desc {
text-align: center !important;
}
</style>@wspollack
Yes, it would certainly be possible to create a template gallery and use this as a starting point for all subsequent galleries.
You could use the sample 'juicebox_pro_1.5.0/web/' gallery from the Juicebox-Pro v1.5.0 zip file, open its 'config.xml' file in a plain text editor, add the languageList you'd like to use (as an attribute to the opening <juiceboxgallery> tag) and save the file.
Now, when you want to create a new gallery, you can open this modified sample gallery in JuiceboxBuilder (instead of clicking the 'New Gallery...' button and starting completely from scratch), add whatever images you like, configure the gallery as required and when you save the gallery on the 'Publish' tab, the languageList will still be in place (alongside the gallery's other configuration options in its 'config.xml' file) even though it never appears in the JuiceboxBuilder interface.
When the user said "I have several galleries and i want all of them to use the same languageList definition.", my suggestion (to just add the languageList manually to all individual galleries) might still be the easiest solution for existing galleries.
However, your suggestion is an excellent idea for creating new galleries going forward.
Thank you for pointing it out.
I don't know why the problem happened in the first place (it sounds like updates to Chrome and Edge might have prevented redirects within iframes from working correctly) but I'm glad that my suggestion worked.
Thank you for letting me know.
Incidentally, just in case you are not aware, you can embed Juicebox galleries directly into WordPress pages and posts (without the need to use iframes) by using the baseUrl method of embedding documented here.
Essentially, once you have created a Juicebox gallery on your computer (perhaps with JuiceboxBuilder), you would upload the complete gallery folder 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.
Also, there is a dedicated Juicebox plugin for WordPress called WP-Juicebox which would allow you to create and manage galleries from within the WordPress dashboard. The plugin handles the embedding of the galleries automatically.
You can download WP-Juicebox from its support page here.
I have run some tests and have found the following.
(1) Juicebox-Pro sets flickrTagMode to ALL by default. The Flickr API Explorer sets 'tag_mode' to 'any' by default.
(2) Juicebox-Pro sends 'original_format' as a Flickr API 'extra' parameter.
(3) Juicebox-Pro sets flickrImageCount to 50 by default (the same as the image limit within Juicebox-Lite). The Flickr API Explorer sets 'per_page' to '100' by default.
(4) The Juicebox-Pro flickrImageCount / Flickr API 'per-page' setting seems to make a difference to the image order.
#1 and #2 will likely not make a difference to your gallery but I notice that changing the flickrImageCount can affect the order of images.
For example, with the Juicebox-Pro flickrImageCount / Flickr API 'per-page' setting set to 500 (to cover all images in your Flickr selection), note the 4th and 5th images in the gallery / API results.
Now, reduce the Juicebox-Pro flickrImageCount / Flickr API 'per-page' setting set to 100 (less than the total number of Flickr images in your selection). The 4th and 5th images are still both present in the gallery / API results but their positions are swapped around (even though the sort order has not changed). Even though fewer images (100) will be returned by Flickr, I would expect the order of images in the 100 test to be the same as the order of these images within the 500 test but this does not seem to be the case (and only Flickr will be able to explain why as I do not know the algorithms that Flickr's API uses).
It should be noted that this happens in both Juicebox-Pro and with the Flickr API Explorer (independent of Juicebox-Pro).
When the Flickr API Explorer settings are identical to those used by Juicebox-Pro, the results are also identical.
If the order of images returned by Flickr (when flickrImageCount / Flickr API 'per-page' is set to less than the number of images you want to display in your gallery) is the order you'd like to use, then I'm not sure what you can do (as you'll need to set flickrImageCount to the number of images you want to display (which might result in an order you do not want).
The only thing I can think of is that maybe the images have similar but not identical time data (same day, same hour, maybe even same minute) and that Flickr's API builds an initial array of images images in different ways (depending on search criteria) and then sorts them by time but perhaps not going down to second or millisecond accuracy so some images with similar but not identical time data might end up in different orders. I do not know if this is what is happening (it seems unlikely) but it's the only thing I can think of at the moment which might explain the results I am seeing.
Maybe refreshing (editing or changing) the metadata stored within your images within the Flickr interface will result in more consistent and predictable behavior but Juicebox can only send a request to Flickr (via the Flickr API) and display whatever Flickr returns. It might be a long process but it might ultimately be the solution to the problem. (There is no way to know without trying.)
If you want to try to understand exactly why Flickr returns images in different orders depending on their API's 'per-page' value (even though the sort order does not change), then you will probably need to ask Flickr themselves in their API support forum.
I don't know if this will help but it's as much as I've been able to determine thought my own testing.
I notice that your iframe loads the following web page:
https://wraa_1954@03f8c79.netsolhost.com/SVPro_Galleries/tt_exhibit_2017_svpro/index.html
However, when this web page is entered directly into a browser's address bar, I see that the browser is redirected to this web page:
https://03f8c79.netsolhost.com/SVPro_Galleries/tt_exhibit_2017_svpro/index.html
I would try using the redirected URL above as the 'src' attribute for your iframe (essentially the same as the one you currently use but without "wraa_1954@" at the beginning).
I hope this helps.
Unfortunately, there is no easy way to have multiple galleries share configuration options from a central location.
You'll just need to add the languageList option to each gallery's current list of options (see example above).
languageList is not featured in the JuiceboxBuilder-Pro interface. It is one of few options that needs to be set manually.
For reference, the languageList support section can be found here.
Instructions for setting configuration options (such as languageList) can be found here.
For example, you could set the languageList option in your gallery's embedding code as follows:
<!--START JUICEBOX EMBED-->
<script src="jbcore/juicebox.js"></script>
<script>
new juicebox({
containerId: "juicebox-container",
galleryWidth: "100%",
galleryHeight: "100%",
backgroundColor: "#222222",
languageList: "Show Thumbnails|Hide Thumbnails|Expand Gallery|Close Gallery|Open Image in New Window|Images|Next Image|Previous Image|Play Audio|Pause Audio|Show Information|Hide Information|Start AutoPlay|Stop AutoPlay|AutoPlay ON|AutoPlay OFF|Go Back|Buy this Image|Share on Facebook|Share on Twitter|Share on Google+|Share on Pinterest|Share on Tumblr|of|Send Email|Download"
});
</script>
<div id="juicebox-container"></div>
<!--END JUICEBOX EMBED-->... or you could edit your gallery's 'config.xml' file in a plain text editor and add the languageList option as an attribute to the opening <juiceboxgallery> tag (alongside the other options that your gallery uses):
<juiceboxgallery
galleryTitle="This is a Juicebox gallery."
useThumbDots="true"
textColor="rgba(255,0,0,1)"
languageList="Show Thumbnails|Hide Thumbnails|Expand Gallery|Close Gallery|Open Image in New Window|Images|Next Image|Previous Image|Play Audio|Pause Audio|Show Information|Hide Information|Start AutoPlay|Stop AutoPlay|AutoPlay ON|AutoPlay OFF|Go Back|Buy this Image|Share on Facebook|Share on Twitter|Share on Google+|Share on Pinterest|Share on Tumblr|of|Send Email|Download"
>Thank you for the additional information.
It looks like a lot of images in conjunction with a deep directory structure is not an ideal combination.
Unfortunately, being that they are both platform limitations (rather than bugs specific to the JuiceboxBuilder code), there is little that we can do to eradicate them.
At least knowing that both of these issues cause problems, we can work around them (with a less deep directory structure and by adding small batches of images instead of one large batch).
Juicebox (whether the gallery is created by the WordPress plugin or any other method) just makes a request to Flickr's API (using the Flickr configuration option values) and displays the images in the order in which they are returned by Flickr.
If you go to the Flickr API Explorer (bypassing Juicebox completely) and enter the same details you use for your gallery:
user_id: 142825215@N06
tags: Hillershausen
sort: date-taken-asc... you'll see the images returned in the same order as they are displayed in the gallery. All the sorting is done at Flickr's end.
If the images are not returned in the correct DATE-TAKEN-ASC order, then maybe you can log into your Flickr account and check (and change if necessary) the metadata associated with the images (to ensure that the order is correct).
Otherwise, you could perhaps change the 'date uploaded' for each image (so that they are in the order you want) and then display the images using DATE-POSTED-ASC, as noted in this FAQ:
How do I change the order of images from Flickr?
If you think there's genuinely a problem with the order in which Flickr is sorting your images, then you might also like to post in the Flickr API forum.
I hope this points you in the right direction.
Did you try adding all 100 images at once from the shallow directory structure (and, if so, did it work)?
There is a known issue which can occur when adding many images at once and if you are adding a large batch of images, the maximum path length might just be a red herring.
If you add many images at once, Adobe AIR may not be able to allocate enough memory for the task at hand. Even if your computer has plenty of free RAM, Adobe AIR applications are limited to around 1GB of memory allocation. The workaround is to add your images in smaller batches.
I don't know if this is relevant but it might be something to bear in mind when testing further.
You're welcome!
I'm glad I was able to help.
(Nice use of the Back Button's 'home' icon by the way!)
Juicebox Support Forum → Posts by Steven @ Juicebox
Powered by PunBB, supported by Informer Technologies, Inc.