Everything worked as it should, although they were switched for me. So what is listed as Main was Thumb and visa versa.
Thank you for pointing that out. I have now edited my post above.
You are not logged in. Please login or register.
Juicebox Support Forum → Posts by Steven @ Juicebox
Everything worked as it should, although they were switched for me. So what is listed as Main was Thumb and visa versa.
Thank you for pointing that out. I have now edited my post above.
I'm glad you've been able to solve your problem.
Thank you for posting back to let me know.
Should this be repeated for each of the embeds or is once in the header sufficient?
Loading one instance of the 'juicebox.js' file in the <head> section of your web page is sufficient. (There is no need to load the 'juicebox.js' file for each gallery.)
When looking at the index for gallery1 what is to be placed here? Is it the index.html file at the root of the gallery folder or the full.html file in the jbcore folder?
Under normal circumstances, there should be no need to go into the 'jbcore' folder and the 'full.html' file should be left unmodified in its original location (the root of the 'jbcore' folder). (It is used when going fullscreen in mobile devices.)
Also, the 'index.html' file from a gallery is required only if you want to display the gallery on a page of its own. If you plan to embed the gallery in an existing web page alongside other content, then this file can safely be ignored.
Am I correct that for each slideshow I would need a baseURL for each tab, in my case gingerbread.html and art.html?
If you plan to embed several galleries, then I would recommend the baseURL method of embedding as documented here. This would allow you to upload your complete gallery folders to your web server keeping each gallery separate in its own folder.
The baseURL embedding code should be inserted into your own web page and you should not modify the 'jbcore/full.html' file. (All galleries can safely share a single 'jbcore' folder with the same 'full.html' file.)
If the above is true why would my page with one slideshow work at: http://uas.alaska.edu/sandbox/alumni/events-test.html that does not contain either the JBP created index file or full.html files?
As noted above, a gallery's 'index.html' file is required only if you want to display the gallery on a page of its own. It is not required (or used) if you embed the gallery in a web page of your own.
If your gallery does not have a 'full.html' page in the 'jbcore' folder, then your gallery will likely fail when going fullscreen on a mobile device.
Is there a list on your site that includes items that must be in the embed?
Yes. A list of Embed Options can be found here. These options (if used) must be in the embedding code rather than the XML file. All other options can be set either in the embedding code or the XML file. (The exception being debugMode which, if used, must be set in the XML file.)
I noticed that when I only had galleryHeight in the .xml file that it wasn't included in the published page.
The galleryHeight entry in the XML file is not actually used by Juicebox when the gallery is displayed. It is used only by JuiceboxBuilder-Pro to repopulate the fields in the interface when opening an existing gallery to edit it.
Try the following (with your own custom font and appropriate Unicode Ids):
/* Thumbnail nav buttons */
.jb-navigation .jbn-left-button:before, .jb-flag-large-screen-mode .jb-navigation .jbn-left-button:before
{
content: "\e000";
}
.jb-navigation .jbn-right-button:before, .jb-flag-large-screen-mode .jb-navigation .jbn-right-button:before
{
content: "\e001";
}
/* Main image nav buttons */
.jb-navigation .jbn-nav-button .jbn-left-button:before, .jb-flag-large-screen-mode .jb-navigation .jbn-nav-button .jbn-left-button:before
{
content: "\e016";
}
.jb-navigation .jbn-nav-button .jbn-right-button:before, .jb-flag-large-screen-mode .jb-navigation .jbn-nav-button .jbn-right-button:before
{
content: "\e017";
}I realise that you say this happens in all galleries (including our own demo galleries) but perhaps the following suggestions will help to optimize your own gallery for a smoother experience on the iPad 2.
I notice that you have set imagePreloading="ALL" so when your gallery initially loads, all the images in the gallery will be preloaded. Try setting imagePreloading="NEXT" (to preload only the next image in the gallery) to see if this helps.
Also, you could try reducing the file size of your images (so that there is less data to preload) to see if this makes a difference.
Your images are currently approximately 1600x900 and 250KB each. Try using JuiceboxBuilder-Pro to build a gallery with the default settings and the resulting images should be approximately 1024x768 and 120KB each.
Your gallery has also increased the imageTransitionTime from its default value of 0.5s to 1s.
Try reverting to the default setting to see if this makes for smoother transitions.
At the moment, the only instance of the 'juicebox.js' file on your web page is coming from the following code:
<script src="http://www.uas.alaska.edu/alumni/juicebox/jbcore/juicebox.js" type="text/javascript"></script>... and the file is not currently at that location.
Once this is fixed, try it again to see if it works. It is hard to tell whether there are any other problems without the 'juicebox.js' file being loaded on your page.
Unfortunately, I do not personally have an iPad 2 and I have been unable to see the problem you are describing.
When I view your gallery in a desktop browser (with Juicebox in Large Screen Mode) and reduce the width of the window, the complete image frame is displayed OK.
Also, when I view your gallery on an iPod Touch (with Juicebox in Small Screen Mode), the complete image frame is still displayed OK.
Try clearing your browser's cache before reloading your gallery just to be sure that the new Juicebox v1.3.0 files are being used in your gallery.
Also, try increasing your gallery's frame width to see what happens.
You can have multiple galleries share a single 'jbcore' folder by following the instructions here.
The code you posted should work fine (overriding the XML settings) but you would have to add the following line:
useFlickr: 'true',... if useFlickr="TRUE" is not already listed as a configuration in the 'config.xml' file that the gallery uses.
Cannot find Flickr User: Akron Children\'s Hospital
The backslash before the apostrophe suggests that your web server's PHP installation may have magic quotes turned on. Please see the Disabling Magic Quotes page and try turning off magic quotes to see if this solves the problem.
Also, when using flickrSetId, there is no need to specify a flickrUserName or FlickrUserId so perhaps just specifying the flickrSetId will avoid the problem.
Please try upgrading your gallery to Juicebox-Pro v1.3.0 which has recently been released.
There have been many changes in this version and upgrading might just solve your problem without any further action.
Please see the Upgrading Juicebox page for details on how to get the latest version.
If this does not help, please post the URL to your gallery so that I can take a look.
(I have been unable to replicate the problem that you have reported.)
We have just introduced a new image transition type (CROSS_FADE) in JuiceboxPro v1.3.0 which was released a few days ago.
The possible values for the imageTransitionType configuration option are now SLIDE, FADE, CROSS_FADE and NONE.
Please see the Version History for a full list of changes and the Upgrading Juicebox page for details on how to get the latest version.
We have no immediate plans to introduce any other image transition types but if you have any suggestions, please post them in the Feature Requests thread.
using JuiceBox Pro can I pull in the photos from two Flickr Sets
No. Juicebox-Pro accepts only one instance of each configuration option (including flickrSetId).
If I had photos being pulled from the complete stream and set it to pull a certain keyword, how long does it take for photos to show up when new photos are added using that keyword?
If you tag images in Flickr, it can take a while for the tags to propagate fully through Flickr's system in order for the images to show up in API searches (such as that performed by Juicebox to fetch the images from Flickr's servers).
According to the Flickr FAQ on this web page:
it shouldn't take more than a few days until your photos appear in searches, groups, etc.
It may take 'a few days' as a worst case scenario but at the other extreme, I have tagged images and had them show up in galleries within minutes.
Yes. That will work fine.
Captions should be visible (and link in captions should be functional) in Small Screen Mode.
You may have to tap the screen for the overlay (including the caption area) to become visible.
I notice that the underline appears in your link only when hovering over it (in a desktop browser) so it looks like there is some CSS on your web page which is interacting with the gallery.
Try viewing the gallery on a page of its own in your mobile device to see what happens.
(I would take a look but there is no 'index.html' file in your 'juicebox' gallery folder.)
Looking at these Flickr forum posts, it looks like it is not possible to create Sets within Groups:
http://www.flickr.com/help/forum/en-us/27432/
http://www.flickr.com/help/forum/en-us/ … 081504521/
http://www.flickr.com/help/forum/en-us/74316/
For reference, instructions for 'Embedding with Adobe Muse' can be found here.
The URLs in your embedding code refer to the 'www.sugarnightclub.ca' subdomain which, when entered into a browser's address bar redirects the user to the main 'sugarnightclub.ca' domain.
Try using the 'sugarnightclub.ca' domain in your URLs (without the 'www') or use relative paths instead.
'Next' transitions always slide in from the right and 'previous' transitions always slide in from the left.
It is not possible to reverse this using the available configuration options although you could create your own navigation buttons using the Juicebox-Pro API and use the buttons to change the images as required using the showNextImage() and showPreviousImage() methods.
However, this will not affect the AutoPlay functionality and in an automated slide show, the 'next' images will always slide in from the right.
You can upload everything in the 'wp-juicebox' folder except the 'default.xml' file (so that your existing 'default.xml' file on your web server will not be overwritten). Just unzip the 'wp-juicebox.zip' file and delete the 'default.xml' file before uploading to your web server.
Once the next version of WP-Juicebox is released, the default settings will no longer be stored in the 'plugins' folder and will, therefore, not be overwritten when updating the plugin in future.
Make sure that your own gallery's XML file is named 'config.xml' and is located in the same directory as the web page containing your gallery's embedding code.
If you rename or relocate your gallery's XML file, then you can point towards it using the configUrl configuration option.
If you continue to experience difficulties, please post the URL to your gallery so that I can take a look.
The bugs noted above have now been fixed in v1.3.0. Please see the Version History for a full list of changes and the Upgrading Juicebox page for details on how to get the latest version.
This bug (the flickering of images during transition in Firefox) has now been fixed in v1.3.0. Please see the Version History for a full list of changes and the Upgrading Juicebox page for details on how to get the latest version.
The backButtonHAlign configuration option has been designated as a Large Screen Mode option only in v1.3.0. Please see the Version History for a full list of changes and the Upgrading Juicebox page for details on how to get the latest version.
This bug has now been fixed in v1.3.0. Please see the Version History for a full list of changes and the Upgrading Juicebox page for details on how to get the latest version.
This bug has now been fixed in v1.3.0. Please see the Version History for a full list of changes and the Upgrading Juicebox page for details on how to get the latest version.
This bug has now been fixed in v1.3.0. Please see the Version History for a full list of changes and the Upgrading Juicebox page for details on how to get the latest version.
Juicebox Support Forum → Posts by Steven @ Juicebox
Powered by PunBB, supported by Informer Technologies, Inc.