901 Reply by Steven @ Juicebox

(3 replies, posted in Juicebox-Pro Support)

If you encounter the "Config file not found." message whilst trying to view a gallery locally (from your computer rather than from your web server) in Safari 11, then please see this forum post for a full explanation and a workaround.

Unfortunately, Safari 11 (released 19 September 2017) introduced a security restriction which prevents local viewing of Juicebox galleries by default. This issue is specific to viewing galleries locally (from your computer's hard drive) and there is no such issue once the galleries have been uploaded to a web server (where they can be viewed in any modern browser).
Selecting 'Disable Local File Restrictions' from Safari 11's 'Develop' menu (full instructions in the link above) should, once again, allow you to view your galleries locally in Safari 11.

If this does not describe your problem, then more general information on the "Config file not found." message can be found in this FAQ:
When I view my gallery I see the message 'Config file not found'. How do I fix this?

I hope my notes above help.
Please let me know how you get on and if I can be of any further assistance.
If you encounter the "Config file not found." message in an online gallery, then please post the URL to your gallery's web page so that I can see the problem for myself and hopefully help further.
Thank you.

Go to forum: Juicebox-Pro Support

902 Reply by Steven @ Juicebox

(1 replies, posted in Juicebox-Lite Support)

When using the Media Library as a source of images, a Juicebox gallery created with WP-Juicebox will display all images attached to the page or post containing the gallery shortcode.

Once the shortcode (e.g. [juicebox gallery_id="5"]) has been added to the page or post, click the 'Add Media' button (to the left of the 'Add Juicebox Gallery' button above the editor toolbar as seen in Screenshot #1 attached).
Now, just drag and drop your images into the media window which pops up.
Wait for the images to finish uploading and then close the media window via the cross at the top right (do not click the 'Insert into post' button at the bottom right).
That's all you need to do. The gallery is built dynamically at the time it is displayed so there is no need to do anything after uploading the images (other than publish your page or post).

If you want to see the images that are attached to the page or post, then in the media window, select 'Add Media (side menu) -> Media Library (tab) -> Uploaded to this post (drop-down menu)' (as seen in Screenshot #2 attached) and you'll see thumbnails of each image (which you can drag and drop into a custom order if you like). (After re-ordering images, again, just close the media window via the cross at the top right.

I hope this helps.
However, if you continue to experience difficulties, please post the URL to you gallery's web page so that I can see the gallery for myself and hopefully help further.
Thank you.

Go to forum: Juicebox-Lite Support

903 Reply by Steven @ Juicebox

(3 replies, posted in Juicebox-Pro Support)

I'm glad that you've been able to resolve your problem.
Thank you for letting me know.

Go to forum: Juicebox-Pro Support

904 Reply by Steven @ Juicebox

(3 replies, posted in Juicebox-Pro Support)

I've just checked the watermarking functionality in JuiceboxBuilder-Pro v1.5.1 using a sample PNG image with a transparent background and it seems to work OK for me (the transparency is carried through to the gallery images).
Please double-check that your own PNG image's background is actually transparent (just in case there's a problem there).
If you continue to experience difficulties, please attach the image to a post here in the forum or upload it somewhere and provide a download link so that I can investigate further and try to replicate your problem with your own image.
Thank you.

Go to forum: Juicebox-Pro Support

905 Reply by Steven @ Juicebox

(1 replies, posted in Juicebox-Pro Support)

When a Juicebox gallery is displayed on a touch-enabled mobile device, Juicebox uses Touch Input Mode (rather than Mouse Input Mode). Please see the Input Mode support section for more information.

In Touch Input Mode, the imageTransitionType is always set to SLIDE (which is the transition which best fits with the swipe gesture for navigating between images).
The imageTransitionType can be set only for Large Screen Mode and Mouse Input Mode. This is noted in the short description for imageTransitionType in the Main Image section of the Config Options Page:

imageTransitionType: How to transition between images. Only applies for Large Screen Mode and Mouse Input Mode.

Unfortunately, there is no way to change the imageTransitionType on a touch-enabled mobile device. It will always be set to SLIDE.

However, if you like, you can 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.
I do not know the likelihood of any suggestions being implemented but this is certainly the best place for all ideas.
Thank you.

Go to forum: Juicebox-Pro Support

906 Reply by Steven @ Juicebox

(1 replies, posted in Juicebox-Pro Support)

There are essentially two ways to make a Juicebox gallery responsive (with its dimensions dynamically changing with the size of the user's browser window).

Scenario #1:
A Juicebox gallery will be responsive (and will dynamically scale with the size of the user's browser window) if the gallery's own dimensions and the dimensions of all parent containers are expressed as percentages. If there is a fixed value anywhere up the chain, then the gallery's size will become fixed (e.g. 100% x 100% x 800px = 800px).
Please note that when using percentage heights, you may need to implement the suggestion noted here.

Scenario #2:
You could use JavaScript to listen for a change in the size of the user's browser window and assign new dimensions to the Juicebox gallery if and when this happens.
An example of this can be found in the resizable galleries support section here.
Take a look at the source of this sample gallery in your browser to see how this might be achieved.

Both scenarios above apply equally to Juicebox-Lite and Juicebox-Pro.

With this in mind, it can be difficult to ensure that a Drupal web page conforms to Scenario #1 and also difficult to implement Scenario #2 within a Drupal environment.

The code you provided includes the following line:

<div class="juicebox-parent " style="width: 540px; height: 450px;">

It looks like your gallery's parent container has fixed pixel dimensions and, therefore, your gallery will ultimately have a fixed size, too (even if it has dimensions expressed as percentages).

I'm not sure where the dimensions for your 'juicebox-parent' container are coming from (the module or your Drupal theme).
(Please note that the module is an unofficial plugin which we did not write ourselves.)
If these values are coming from you current gallery dimensions, then try setting your galleryWidth to be 100% (and set your galleryHeight to be a fixed pixel value (such as '600px') as your Drupal page will likely support vertical scrolling in which case the gallery would not benefit from being responsive in the vertical dimension).
Otherwise, you might like to try a different Drupal theme which does not use containers of fixed dimensions (which will constrain your gallery).

Go to forum: Juicebox-Pro Support

907 Reply by Steven @ Juicebox

(3 replies, posted in Juicebox-Pro Support)

I'm glad you've got it working!
Thank you for letting me know.

Go to forum: Juicebox-Pro Support

908 Reply by Steven @ Juicebox

(3 replies, posted in Juicebox-Pro Support)

No problem at all.
I'm glad it was an easy one to fix!

Go to forum: Juicebox-Pro Support

909 Reply by Steven @ Juicebox

(3 replies, posted in Juicebox-Pro Support)

The problem is caused by having set a fixed width for your gallery:

galleryWidth:'708'

Your gallery will always have a fixed width of 708px regardless of any parent containers or the size and shape of the browser viewport.

Set a gallery width of 100% instead and your gallery will fill the width of its parent container (and it should adapt to different browser viewport widths).

I hope this helps you to resolve your problem.

Go to forum: Juicebox-Pro Support

910 Reply by Steven @ Juicebox

(1 replies, posted in Juicebox-Lite Support)

The problem is caused by some custom CSS from your 'styles.css' file. On line 78, you have the following code:

img { 
    border: none;
    padding: 0;
    margin: 0;
    width: 100%;
}

These CSS rules are being applied to all images on your web page (including those inside your Juicebox gallery).

If you remove this code (specifically the width: 100%; line), then the thumbnails in your Juicebox gallery should look correct.

A better option would be to apply your custom CSS rules to only those elements on your page which require them through te use of CSS selectors (classes and ids).

I hope this helps you to resolve your problem.

Go to forum: Juicebox-Lite Support

911 Reply by Steven @ Juicebox

(5 replies, posted in Juicebox-Pro Support)

I'm glad you've been able to resolve your problem.
Thank you for letting me know.

Go to forum: Juicebox-Pro Support

912 Reply by Steven @ Juicebox

(5 replies, posted in Juicebox-Pro Support)

Please let me see the gallery where the Download Button does not appear.
It should not matter whether the configuration option is set in the embedding code or the XML data (whether from a static file or generated dynamically).
The problem may be something as simple as a typo in your configuration option name.
If I can see your gallery (and dynamically generated XML data), I'll be able to investigate further.
Thank you.

Go to forum: Juicebox-Pro Support

913 Reply by Steven @ Juicebox

(496 replies, posted in Juicebox-Pro Support)

@plato1123

Thank you for the link!

I do not know what suggestions the developers will implement in future versions (or how long it may take for suggestions to be implemented) so my notes below might help for anyone hoping to implement such functionality in the short-term.

The only user that I know of that has managed to overcome the restriction of one og:image per web page for Facebook sharing is sly in this forum thread. (He achieved this by overriding Juicebox's own Facebook sharing handler with what looks like quite a lot of complex custom JavaScript.)

Using the code from the link you quoted, the following might work, although please note that it is untested as I do not currently have a Facebook App ID. (Replace '123456789012345' in the following code with your own Facebook App ID.)

<!DOCTYPE html>
<html lang="en">
    <head>
        <meta charset="utf-8" />
        <meta name="viewport" id="jb-viewport" content="width=device-width, initial-scale=1.0, minimum-scale=1.0, maximum-scale=1.0, user-scalable=0" />
        <meta property="og:description" content="" />
        <meta property="og:image" content="" />
        <meta property="og:title" content="" />
        <meta property="og:type" content="website" />
        <meta property="og:url" content="" />
        <style type="text/css">
            body {
                margin: 0px;
            }
        </style>
        <script type="text/javascript" src="jbcore/juicebox.js"></script>
        <script>
          window.fbAsyncInit = function() {
            FB.init({
              appId            : '123456789012345',
              autoLogAppEvents : true,
              xfbml            : true,
              version          : 'v2.10'
            });
            FB.AppEvents.logPageView();
          };
         
          (function(d, s, id){
             var js, fjs = d.getElementsByTagName(s)[0];
             if (d.getElementById(id)) {return;}
             js = d.createElement(s); js.id = id;
             js.src = "//connect.facebook.net/en_US/sdk.js";
             fjs.parentNode.insertBefore(js, fjs);
           }(document, 'script', 'facebook-jssdk'));
        </script>        
        <script>
        function shareOverrideOGMeta(overrideLink, overrideTitle, overrideDescription, overrideImage)
        {
            FB.ui({
                method: 'share_open_graph',
                action_type: 'og.likes',
                action_properties: JSON.stringify({
                    object: {
                        'og:url': overrideLink,
                        'og:title': overrideTitle,
                        'og:description': overrideDescription,
                        'og:image': overrideImage
                    }
                })
            },
            function (response) {
            // Action after response
            });
        }
        </script>    
        <script type="text/javascript">
            var jb = new juicebox({
                containerId: "juicebox-container",
                shareFacebook: "TRUE"
            });
            jb.onImageChange = function(e) {
                var index = e.id;
                var info = jb.getImageInfo(index);
                var url = info.imageURL;
                var link = 'http://www.example.com/';
                var title = info.title;
                var description = info.caption;
                var image = link + url;
                shareOverrideOGMeta(link, title, description, image);
            };
        </script>
        <title>Test</title>
    </head>
    <body>
        <div id="juicebox-container"></div>
    </body>

</html>

Go to forum: Juicebox-Pro Support

914 Reply by Steven @ Juicebox

(3 replies, posted in Juicebox-Pro Support)

If you see the Juicebox logo in the lower right corner of your gallery, then your gallery is indeed Juicebox-Lite instead of Juicebox-Pro. (This branding is not present in Juicebox-Pro galleries.)

All you need to do to upgrade the gallery from Lite to Pro is replace the gallery's Lite 'jbcore' folder with the Pro 'jbcore' folder from the Juicebox-Pro v1.5.1 download zip package ('juicebox_pro_1.5.1/web/jbcore/').
Alternatively you can open and re-save your gallery in JuiceboxBuilder-Pro (and then re-upload the gallery to your web server, ensuring that existing files are overwritten).
Instructions for upgrading a gallery from Lite to Pro can be found here.

If your gallery still seems to be Lite, then try clearing your browser's cache to make sure that your browser is using the latest files from your web server (instead of older cached versions).

I hope this helps.
However, 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 hopefully help further.
Thank you.

Go to forum: Juicebox-Pro Support

915 Reply by Steven @ Juicebox

(5 replies, posted in Juicebox-Pro Support)

However I recently created a gallery using JuiceboxBuilder-Pro (v 1.5.1) and uploaded the gallery as is (index.html etc) - and the download button shows and works!

Juicebox-Pro uses the 'download' attribute (please see here for details) and browsers which support the 'download' attribute (noted here) will use this to download the image.
The PHP functionality is used as a fallback mechanism for browsers which do not support the 'download' attribute (such as Internet Explorer 11, Safari 5.1.7 on Windows and older browsers).

Therefore, PHP is required to be installed on your server to ensure that the Download Button works across all browsers.

It doesn't seem to work in my embedded galleries where
showDownloadButton="true"
(in ASP ashx file pretending to be an xml file)

If you do not have PHP installed on your server, then please check that you are using a browser which supports the 'download' attribute and also check that you do not have hotlink protection activated on your hosting account (which will prevent direct access to your images).
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 hopefully help further.
Thank you.

Go to forum: Juicebox-Pro Support

916 Reply by Steven @ Juicebox

(1 replies, posted in Juicebox-Pro Support)

A Single-Site License for Juicebox-Pro covers one website domain and all associated subdomains (please see the FAQ below) so a Single-Site Licence would be fine for your scenario.
Does a single domain license cover multiple subdomains?

Go to forum: Juicebox-Pro Support

917 Reply by Steven @ Juicebox

(1 replies, posted in Juicebox-Lite Support)

Unfortunately, due to certain browser security restrictions, Juicebox galleries cannot be viewed locally in all browsers.
Please see this FAQ for details:
When I view my gallery locally, I see the message "Juicebox can not display locally in this browser". Why?

This issue is specific to viewing galleries locally (from your computer's hard drive) and there is no such issue once the galleries have been uploaded to a web server (where they can be viewed in any modern browser).

If you encounter the "Config file not found." message whilst trying to view a gallery locally in Safari 11, then please see this forum post for a full explanation and a workaround.

Safari 11 (released 19 September 2017) introduced a security restriction which prevents local viewing of Juicebox galleries by default. Selecting 'Disable Local File Restrictions' from Safari 11's 'Develop' menu (full instructions in the link above) should, once again, allow you to view your galleries locally in Safari 11.

Juicebox galleries can be viewed locally in Safari (when using the tip in the link above) and also in Edge and Firefox (without any modification).

Go to forum: Juicebox-Lite Support

918 Reply by Steven @ Juicebox

(1 replies, posted in Juicebox-Pro Support)

No, sorry. You can set configuration options in the gallery's embedding code (please see the Setting Config Options support section for details) but the image data needs to be in a separate configuration file.
Even if using a Flickr account as a source of images for a gallery, you can set the Flickr configuration options in the gallery's embedding code but you still need to have a separate configuration file (even if it contains just a <juiceboxgallery /> tag.

Go to forum: Juicebox-Pro Support

919 Reply by Steven @ Juicebox

(496 replies, posted in Juicebox-Pro Support)

@alain.guilleux

As far as I am aware, the only two options available for the 'Metadata' drop-down menu are 'Copyright Only' and 'All' (the same options that you'll see in the web engines which are bundled with Lightroom: Classic Gallery, Grid Gallery, Square Gallery and Track Gallery).
Here is a direct quote from the 'Data model entries' section of the latest Lightroom Classic CC programmers guide SDK documentation:

metadataExportMode—What metadata to include, either 'copyright' or 'all'.

The only options that the Juicebox web engine has any control over are:
(1) The choice of whether or not to display the 'Metadata' drop-down menu. (If the 'Metadata' drop-down menu is to be displayed, then the options are populated by Lightroom itself.)
(2) The choice of which value to display as the default option ('Copyright Only' or 'All' ).

If you find that metadata fields that you require are not being exported into your gallery images when setting 'Metadata' to 'Copyright Only', then set 'Metadata' to 'All' instead.

Go to forum: Juicebox-Pro Support

920 Reply by Steven @ Juicebox

(1 replies, posted in Juicebox-Pro Support)

Looking at the [SOLVED] tag in your topic subject, it appears that you might already have resolved your problem (which would be great).
However, if you continue to experience difficulties, please post back with the URL to your gallery's web page so that I can see the problem for myself and hopefully offer some help. Thank you.

Go to forum: Juicebox-Pro Support

921 Reply by Steven @ Juicebox

(1 replies, posted in Juicebox-Lite Support)

According to your gallery's embedding code, it looks like your gallery's configUrl file should be located here:
http://www.deutsches-fachwerkzentrum.de/scripts/juicebox_lite_1.5.1/oekologischesbauen_goldstrasse25.php
However, going directly to that location in a browser does not display the gallery's XML data.

Please check the location of your gallery's configUrl file ('oekologischesbauen_goldstrasse25.php') and make sure that it outputs the gallery's XML data in the correct format (and with valid XML syntax).

(The configUrl is relative to the baseUrl and the baseUrl is relative to the web page containing the embedding code.)

I hope this helps to resolve your problem.

Go to forum: Juicebox-Lite Support

922 Reply by Steven @ Juicebox

(496 replies, posted in Juicebox-Pro Support)

@alain.guilleux

Thank you for your suggestion (and the link to the Google blog entry)!

What happens when 'Copyright Only' is selected in the 'Metadata' drop-down menu is actually handled by core Lightroom functionality (rather than any code specific to the Juicebox plugin). The plugin simply passes the value of the 'Metadata' input to Lightroom which then does the rest so, unfortunately, it's really not something that the plugin has any control over.

Go to forum: Juicebox-Pro Support

923 Reply by Steven @ Juicebox

(1 replies, posted in Juicebox-Lite Support)

Hi.

This is a support forum for the Juicebox-Pro web gallery software from SimpleViewer Inc.

From your query, it sounds like you have purchased a 'JuiceBox' from eMotorWerks, a completely unrelated company to our own (although the product names are the same).

You should be able to contact eMotorWerks via their online form here: https://emotorwerks.com/contact

I hope this points you in the right direction.

Go to forum: Juicebox-Lite Support

924 Reply by Steven @ Juicebox

(3 replies, posted in Juicebox-Pro Support)

Could you take a look at the attached .7z archive containing config.xml, index.html and the jbcore subdirectory.

There's no file attached to your post.
I've just checked and, unfortunately, the forum software does not allow .zip or .7z files to be attached to posts. Sorry about that. (It accepts mostly image and text files.)
Perhaps you could upload your .7z file somewhere else (perhaps your own web server or a file sharing service such as Dropbox or Google Drive) and provide a download link. Thank you.

I find that the same kind of failure (all html files, no images) happens sometimes with the galleries that came with LR,as well.

This certainly suggests that the problem lies with core Lightroom functionality rather that something specific to the Juicebox web engine.

The number of images does seem to make a difference, in that if there are only a few images to test, the export works, but with a few thousand images, it fails.

If the problem happens consistently when you try to export a few thousand images, then it sounds like Lightroom might be reaching some kind of internal limit (or maybe even a system limit such as memory).
Unfortunately, it sounds like there is little that we can do with regard to the Juicebox plugin to solve your problem as it happens elsewhere, too.
Also, I notice that you are using the latest version of Lightroom CC 6 (6.14). If the problem is a bug in Lightroom CC 6.14, then there are no further upgrades for Lightroom CC 6 and the next step up would be Lightroom Classic CC 7 (but I do not know if this will help).

I've found a couple of forum thread online which might be somewhat relevant to your problem (or at least help to explain what might be going on).

The first thread is a report of Lightroom CC 6.14 maxing out system memory so I guess this might also be what is happening with your scenario.
https://feedback.photoshop.com/photosho … out-memory

The second thread is a report of Lightroom CC 6 not exporting all selected images. (There are suggestions to close Adobe Bridge and any other programs which might be monitoring the output directory.)
https://feedback.photoshop.com/photosho … ted-images

I do not know if the information contained in these threads will help but it is almost certainly a Lightroom issue (rather than an issue specific to the Juicebox plugin) and the only thing I can suggest is that you try upgrading Lightroom if you can (although I realise that there are no further upgrades for Lightroom CC 6 and the next step up would be Lightroom Classic CC 7).

Go to forum: Juicebox-Pro Support

925 Reply by Steven @ Juicebox

(3 replies, posted in Juicebox-Pro Support)

That's very strange.
I've never known this to happen and, as far as I can recall, no-one has reported such a problem before.
It is also strange that the plugin used to work fine for you but now does not.
Changing gallery configuration options should have no bearing on the image export process.

What happens if you try to export a gallery using a different web engine such as Classic Gallery or Grid Gallery (one of the default web engines)? Are the images exported successfully when using these web engines? Is the problem just with the Juicebox web engine?

If you find that the problem happens with all web engines, then I would suggest reinstalling Lightroom itself to see if this helps.

If the problem happens only with the Juicebox web engine, then perhaps you could zip your incomplete gallery folder's 'index.html' and 'config.xml' files and attach them to a post (or upload them somewhere and provide a download link) so that I can check them out. Maybe there are clues within the exported HTML and XML files as to why the export process has been incomplete. Also, with access to your gallery's 'config.xml' file, I should be able to see your gallery's configuration options and can then try to replicate the problem myself using the same options.

Thank you.

Go to forum: Juicebox-Pro Support