2,926

(5 replies, posted in Juicebox-Lite Support)

I am sorry to hear that you are having difficulties installing JuiceboxBuilder-Lite.
Under normal circumstances, all that should be necessary to install JuiceboxBuilder-Lite is to ensure that you have Adobe AIR installed and then double-click the 'JuiceboxBuilder-Lite.air' file.

If you were able to extract the Juicebox-Lite zip package successfully without any error messages, then it is unlikely that the 'JuiceboxBuilder-Lite.air' installation file is actually damaged or corrupt.
However, if you would like to check the integrity of your 'JuiceboxBuilder-Lite.air' (v1.4.3.2) file, then it should have the following properties:
Filesize: 1,376,245 bytes
MD5 hash: 1015798482f200693a23edb0d3c80bbd
SHA1 hash: b980edd071f086071dc860fdbce4ac687d8660b0
You can check the MD5 and SHA1 hashes of files with a free program such as HashCalc.

Please try the following. Make sure that you using an Administrator User Account and then:

  • Uninstall Adobe AIR.

  • Make sure that no remnants of any failed JuiceboxBuilder-Lite install are still present on your system by searching your hard drive for the term 'JuiceboxBuilder' and manually deleting everything found.

  • Download the latest version of Adobe AIR from here: http://get.adobe.com/air/

  • Install Adobe AIR by right-clicking the 'AdobeAIRInstaller.exe' file and selecting 'Run as administrator'.

  • Now try reinstalling only JuiceboxBuilder-Lite, allowing the application to install to the default location.

If you continue to experience problems, then there is a fairly comprehensive list of things to check/try (such as temporarily deactivating your anti-virus program in case this is somehow interfering with the JuiceboxBuilder-Lite installation process) in this forum thread.

Hopefully one of the suggestions above (or in the forum thread) will help.

2,927

(29 replies, posted in Juicebox-Pro Support)

OK. Thank you for letting me know.
I have notified the developers who will investigate further.
I will post back in this thread when I have any further news.

2,928

(1 replies, posted in Juicebox-Pro Support)

All galleries must have an XML file but you could certainly use a server-side scripting language (such as PHP) to dynamically generate the required XML file (rather than just create a static XML file in whilst authoring the gallery).

Please see this FAQ which should hopefully point you in the right direction:
Can Juicebox handle a custom data source, for example RSS or Instagram?

Also, there is an example of using PHP to dynamically generate an XML file which displays all images in a designated folder in this forum post.

2,929

(1 replies, posted in Juicebox-Pro Support)

Please see this FAQ which deals with a similar scenario (too much space above or below the main image).

The space to the left and right of your main images is due to the different aspect ratios of the images (portrait style) and the image area within the gallery (landscape style).
The images are actually displayed as large as possible within the image area without cropping.
If the images were displayed any larger within the image area (without the gallery's dimensions changing), then the images would be cropped at the top and bottom.
You could set imageScaleMode="FILL" but this would result in your images being cropped at the top and bottom.
Perhaps the best solution would be to change your gallery's dimensions so that the image area's aspect ratio better matches that of your images. You could do this by increasing the height of your gallery or by reducing its width.

Please make sure that you are using the latest version of Juicebox (v1.4.3.2).
Flickr made a change to their API to be more secure and we updated Juicebox to handle this change in v1.4.2.
Please see this Juicebox blog entry for further information.

If you are already using the latest version of Juicebox, then the issue might be caused by a temporary glitch with Flickr's web servers or a problem with your internet connection. Either might be preventing your browser from being able to download the images in a timely manner resulting in blank spaces where images should be.

Please post the URL to your gallery's web page so that I can take a look at the problem and investigate further.
I will report back with my findings.

2,931

(5 replies, posted in Juicebox-Pro Support)

Thank you for the link.
I'll let the developers know (but I would still recommend that you post any suggestions in the Feature Requests thread so they do not get lost).

2,932

(2 replies, posted in Juicebox-Pro Support)

As far as I am aware, there are currently no plans to add support for sharing on Instagram.

If you wanted to add support for a social media platform which is not currently supported by Juicebox, then you might be able to implement it using the Juicebox-Pro API.
As long as the social media platform has its own sharing functionality (where you can send information to their web site via a share URL), then you could manually add an HTML button to your web page (alongside your gallery) which, when clicked, would fetch the required information about the image currently being displayed in the gallery (using the available Juicebox-Pro API methods such as getImageInfo()) and use this information to populate the parameters in the share URL.
Knowledge of HTML and JavaScript would be required and while this may be possible, it might not be easy to achieve (although I hope it points you in the right direction if you plan to try it).

2,933

(5 replies, posted in Juicebox-Pro Support)

It's not technically a bug (although I understand what you are saying).
The dynamically generated code is valid HTML 5 and is unconnected to JuiceboxBuilder-Pro's 'Add SEO Content' functionality which works as documented here.

Also, as noted in this Google Developers Webmasters support page: https://developers.google.com/webmaster … learn-more

... crawlers are not able to see any content that is created dynamically.

... so the code you are referring to will not be seen by web crawlers and will have no effect on SEO. Web crawlers will see only what you see when you view the source of the web page unless you explicitly provide HTML snapshots of dynamically generated content on your web server. (An HTML snapshot is all the content that appears on the page after the JavaScript has been executed.)

Thanks for creating a version 1.4.4 where no path is used in alt of <img>.

I would encourage you to post feedback and 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.

2,934

(5 replies, posted in Juicebox-Pro Support)

JuiceboxBuilder-Pro's 'Add SEO Content' functionality adds SEO code to the gallery's 'index.html' file (and to the embedding code presented on the 'Publish' tab which you can copy and paste if you want to embed your gallery into an existing web page alongside other content).

The SEO code is not included in the HTML code which is generated dynamically by the 'juicebox.js' file when the gallery is displayed.

The SEO code is included in the embedding code (inside the 'juicebox-container' <div>) so that it can be seen by web bots crawling the internet and also by viewing the source of the web page in a browser (but not by inspecting the dynamically generated code via a browser's developer tools).

'Add SEO Content' is a feature of JuiceboxBuilder-Pro only. The SEO code must be generated whist creating the gallery and before the gallery can be displayed. As such, 'Add SEO Content' is not a configuration option that can be added to a gallery's XML file. (It is used only by JuiceboxBuilder-Pro when creating a gallery and is not recognised by the 'juicebox.js' file when a gallery is displayed.)

I hope this helps to clarify things.

[Post moved to keep cases separate.]

2,935

(3 replies, posted in Juicebox-Pro Support)

Thanks Steven, it works.

That's great! Thank you for emailing me back to let me know.
I'll ensure that the fix is included in the next version of the plugin.

2,936

(4 replies, posted in Juicebox-Pro Support)

I can't explain how your web address was used as the linkURL in several (but not all) of the images in your gallery but I'm glad that you have been able to resolve your problem. Thank you for posting back to let me know.

Just for the record, linkURLs can be entered (and deleted) on the 'Images' tab of JuiceboxBuilder-Pro.
Click a thumbnail and the Title, Caption and Link URL input fields for that particular image will be displayed.

If you wanted to remove all linkURLs from a gallery's XML file, you could open the file in a text editor which supports regular expressions, (such as Notepad++), do a global regular expression search for the following:

linkURL=".*?"

... and replace all instances found with:

linkURL=""

This will replace all linkURLs with linkURL="" in a single action and imageURLs will be used for all images.

2,937

(3 replies, posted in Juicebox-Pro Support)

This is, indeed, a bug. Thank you for reporting it.
It will be fixed in the next version of the Lightroom plugin.
In the meantime, I have emailed you a version of the plugin which should hopefully fix the problem.

2,938

(2 replies, posted in Juicebox-Lite Support)

Please note that we did not write the Juicebox module for Drupal and, as such, support for the module would be better directed towards the Drupal forum where the author of the module (who is more familiar with both Drupal and the module itself) should be able to answer your query: https://www.drupal.org/forum
The author of the module is active in the Drupal forum (and very helpful) and should be able to help you out.
The Drupal forum would definitely be the best place for you to post your query.
I realise that this does not directly answer your query but it should at least point you in the right direction.

I'm glad you've been able to get to the bottom of your problem.
Thank you for posting back to let me know.

2,940

(4 replies, posted in Juicebox-Pro Support)

The problem is due to linkURL entries in your gallery's XML file such as the following:

linkURL="www.paulraphaelson.com"

If a linkURL is present, then Juicebox will use this instead of the imageURL when the Open Image Button is clicked.
Because your linkURL does not start with http://, Juicebox sees the path as being relative (to the HTML page containing the gallery's embedding code).

Try one of the following:
(1) Change your linkURLs to be the same as your imageURLs (and the images will be opened when the Open Image button is clicked).
(2) Leave your linkUR s empty (and Juicebox will use the imageURLs). (Same result as #1 above.)
(3) Change your linkURLs from www.paulraphaelson.com to http://www.paulraphaelson.com and when the Open Image Button is clicked, the user's browser will open the address http://www.paulraphaelson.com.

2,941

(15 replies, posted in Juicebox-Pro Support)

I'm on bluehost, and checked the the php version they run. It is 5.2 and is set to "Single php.ini". Could that be something?

A Juicebox gallery does not use or require PHP so this is not the cause of the problem.

Without being able to examine your .htaccess file, I do not know if there is any code in there which might be contributing to your problem. Take a look for any references to XML files. (Search the file for the term 'xml' and temporarily remove any entries found to see if this helps.)

Perhaps the best thing to do would be to contact your web host and ask them why your http://morethansnapshots.com/LRGallerie … config.xml file is not publicly accessible and why trying to access it in a browser results in an error 403 (forbidden) message.

Also, having seen that my galleries are embeds, do I need so put additional code into files?

No. For what you are trying to do (link directly to full-browser gallery pages), all you should need to do is:
(1) Create a gallery with JuiceboxBuilder-Pro (or whatever other method you like).
(2) Upload the complete gallery folder (not just the contents) to your web server (without making any modifications to the contents of the gallery folder at all).
(3) Link to the gallery's 'index.html' file (inside the gallery folder) from your main web page.

If your web server was allowing access to your gallery's XML file, then you would not be experiencing any problems.
Your web host should hopefully be able to quickly and easily determine the exact cause of your problem and fix it for you.

2,942

(1 replies, posted in Juicebox-Lite Support)

Use relative paths in your embedding code and the gallery should display both locally (in supported browsers - please see this FAQ for details) and online.

For example:

<!--START JUICEBOX EMBED-->
<script src="../../Benutzer/ThomasKlinger/Bilder/galerie/jbcore/juicebox.js"></script>
<script>
    new juicebox({
        baseUrl : '../../Benutzer/ThomasKlinger/Bilder/galerie/',
        containerId : 'juicebox-container',
        galleryWidth : '800',
        galleryHeight : '600',
        backgroundColor: '#222222'
    });
</script>
<div id="juicebox-container"></div>
<!--END JUICEBOX EMBED-->

The above is just an example. I do not know the file structure of your site so you will need to make sure that the relative paths are correct.

Just for the record, if you added 'file:///' to the beginning of your paths, your gallery might work locally but it would not work online as visitors to your web site would not have access to files on your C:/ drive.
For example:

<script src="file:///C:/Benutzer/ThomasKlinger/Bilder/galerie/jbcore/juicebox.js"></script>

Thank you for the feedback and suggestion.
I would encourage you to post your ideas in the Feature Requests forum thread. This keeps all the ideas together and ensures that they are not overlooked by the developers. Thank you.

2,944

(15 replies, posted in Juicebox-Pro Support)

No problem.
Hopefully you'll be able to sort things out. It certainly looks like the problem is related to file or folder permissions on your web server.
If you continue to experience difficulties, I'm still happy to take a look for you so just let me know.

2,945

(15 replies, posted in Juicebox-Pro Support)

Whether you intend to display a Juicebox gallery in a web page alongside other content or just on a page of its own, it still needs to be embedded. When you create a gallery with JuiceboxBuilder-Pro or the Lightroom plugin, the gallery is automatically embedded into a page of its own (the 'index.html' page).

You should be able to create a gallery (with the method of your choice), upload the complete gallery folder to your web server and link to the 'index.html' page within the gallery folder.

Your problem is currently with the 'config.xml' file inside the gallery folder (your '/LRGalleries/TxCapSculptureJBX/' folder).
Try opening the 'config.xml' file directly in a browser: http://morethansnapshots.com/LRGallerie … config.xml
This bypasses Juicebox. You should be able to see the contents of the XML file in your browser. Instead, the following message is displayed.

403 Permission Denied
You do not have permission for this request /LRGalleries/TxCapSculptureJBX/config.xml

This suggests that the permissions on the file (or on one of its parent folders) are still too restrictive and your web server is preventing the browser from being able to read the file.
Compare this to the 'config.xml' file in a working gallery: http://www.juicebox.net/demos/lite/full/config.xml

It is not a problem with Juicebox functionality but rather a problem with the XML file on your web server.
Please double-check the permissions on your gallery's 'config.xml' file and on all the directories that the file is nested within ('LRGalleries' and 'TxCapSculptureJBX').

If you continue to experience difficulties, then it would help if I had access to your web server so that I could investigate further.
If you are agreeable to this, please let me know and I will send you a message with an email address where you can send me your FTP login details.
Thank you.

2,946

(6 replies, posted in Juicebox-Pro Support)

Thank you for sharing your findings.
Unfortunately, I cannot explain why JuiceboxBuilder-Pro cannot write back to the original gallery folder on your network drive (are any files from within the folder open in any other programs which may have put a temporary lock on them?) but as long as saving the new gallery to a new folder works consistently, then this seems to be the way to go.

Thank you for providing the URL to your gallery.
I have viewed your gallery and all 47 thumbnails displayed first time without issue and without the need to refresh the page (although they seemed a little slow to load).

If you view your gallery in different browsers (or in the same browser after clearing the cache each time), is it always the same thumbnails that do not appear or does it change from time to time?

If you find that you are getting inconsistent results then the problem may be due to either your web server or internet connection.
The code on your web page remains constant and browsers will always process this code in the same way each time the page is displayed.
The only other factors in the equation are the web server and internet connection (the means by which the code is passed to the browser). If the browser does not receive the complete code, then your web page may not be complete.
For example, if your web server is experiencing problems in serving the files in a timely manner, the browser may time-out whilst trying to load an image. Also, if you have an internet connection that drops-out occasionally, a similar thing can happen.
Please check with your web host to see if they have been experiencing any issues lately which might be contributing to your problem. Also, check that your internet connection is stable.

Maybe the problem is just a browser caching issue. Try completely clearing your browser's cache before reloading your web page to see if this helps.

2,948

(6 replies, posted in Juicebox-Pro Support)

Juicebox saves the data from the 'Set Image Sizes' pop-up window in preset files and if small or large images are deselected when a preset is saved, then they will also be deselected when the preset is loaded.
I realise that you would rather have Juicebox not save the image size data but this is how Juicebox works and knowing this should at least help you workaround it.

I loaded the preset without the sizes. I went back to the size panel and changed the sizes. I saved the preset:

    thumbWidth="64"
    thumbHeight="64"
    thumbQuality="80"
    useLargeImages="true"
    useSmallImages="true"
    smallImageWidth="640"
    smallImageHeight="480"/>

And I asked to publish the gallery to a new folder. Unfortunately, the images were copied unchanged from the old to the new gallery and no larger/smaller folders even appeared.

I tried what you described above but was unable to replicate the problem. My test gallery included both small and large images as expected.

I went back to the size panel and changed the sizes. I saved the preset:

Make sure that you click the 'OK' button in the 'Set Image Sizes' pop-up window between changing the sizes and saving the preset.

Also, please make sure that you are using the most recent version of JuiceboxBuilder-Pro (v1.4.3) to ensure that any bugs present in previous versions which have since been fixed are not contributing to your problem. You can check which version you are using by going to 'Help -> About JuiceboxBuilder-Pro' from the drop-down menu at the top.
If necessary, instructions for downloading the current version and upgrading JuiceboxBuilder-Pro can be found on the Upgrading Juicebox support page.

I see the problem you are describing.

Default values are not written to gallery XML files as they should not be not necessary. If a configuration option is not explicitly listed in a gallery XML file, then its default value should be used.

However, the exception to this rule is that if you do not explicitly set an expandedBackgroundColor, Juicebox uses the backgroundColor (for consistency between the normal and fullscreen displays).

The workaround to this would be to ensure that you explicitly set an expandedBackgroundColor.

The only problem with this is that when you use an expandedBackgroundColor with transparency and set useFullscreenExpand="TRUE", the actual background color is dependent on the browser as different browsers use different background colors (black vs white) for the default fullscreen visual environment.

The best course of action to workaround both issues above would be to explicitly set an opaque expandedBackgroundColor.

Please check that the images have been uploaded to the correct location on your web server and check that the thumbURL paths in the gallery's XML file point towards the thumbnail images correctly.

You might like to try re-uploading the thumbnail images to your web server in case something happened during the initial upload resulting in missing or corrupt files.

Please also see this FAQ:
My images show locally, but not when I upload them to my website. Why?

Also, check the permissions of the thumbnail files (with a dedicated FTP program such as Filezilla or within your web hosting account's online CPanel) and their parent folders to make sure that they are not too restrictive. Default permissions of 644 for files and 755 for folders should be fine.

If you continue to experience difficulties, then please post back with the URL to your gallery so that I can take a look at the problem for myself and help further.