901

(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>

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.

903

(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.

904

(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?

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).

906

(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.

907

(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.

908

(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.

909

(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.

910

(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.

911

(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.

912

(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).

913

(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.

914

(1 replies, posted in Juicebox-Pro Support)

I realise that you do not want to use Flickr but, as Juicebox has built-in support for Flickr, using a Flickr account (or a Flickr set) as a source of images for a Juicebox gallery is a very simple process of just setting one or two configuration options.
Unfortunately, Juicebox does not have built-in support for Google Photos and there is no quick and easy solution for displaying images from a Google Photos album in a Juicebox gallery.

It is certainly possible to use a custom data source (as noted in this FAQ: Can Juicebox handle a custom data source, for example RSS or Instagram?) but Google Photos integration would likely turn into quite a substantial coding project.
You'd probably need to use the Google Photos Library API with the PHP client library (which looks to be quite a complex process in itself) to obtain a list of photos and then dynamically create the XML data for your Juicebox gallery in the correct format (using PHP).
I do not know of anyone who has done this before for Google Photos so I am unable to point you in the direction of any sample code.

Depending on the scale of your project, it might be quicker (and certainly easier) to just duplicate your Google Photos albums for your Juicebox galleries (using local images).

915

(3 replies, posted in Juicebox-Pro Support)

You're welcome!
I'm glad it solved your problem. Thank you for letting me know.

916

(3 replies, posted in Juicebox-Pro Support)

When I check your gallery's dynamically generated XML file, I expect to see XML data (the gallery's configuration options and image data) but, instead, the following messages are displayed:

Warning: require_once(GAWD_DIR/wd/start.php): failed to open stream: No such file or directory in /home/mhfm/public_html/wp-content/plugins/wd-google-analytics/google-analytics-wd.php on line 60

Fatal error: require_once(): Failed opening required 'GAWD_DIR/wd/start.php' (include_path='.:/usr/lib/php:/usr/local/lib/php') in /home/mhfm/public_html/wp-content/plugins/wd-google-analytics/google-analytics-wd.php on line 60

It looks like the problem is related to the WD Google Analytics plugin which is somehow interfering with the functionality of WP-Juicebox.
Try temporarily deactivating your WD Google Analytics plugin to see if this helps.

Edit:
I've investigated the problem further and it seems to have something to do with the fact that both plugins (WP-Juicebox and WD Google Analytics) have a file named 'config.php'.
I'm not sure of the exact cause of the problem (both files are in different folders and should not interfere with each other) but a workaround seems to be to rename the WP-Juicebox file 'config.php' to 'config2.php' and then also rename the reference to the file on line 275 of the 'wp-juicebox.php' file, changing:

$config_url = plugins_url('config.php?gallery_id=' . $clean_gallery_id, __FILE__);

... to:

$config_url = plugins_url('config2.php?gallery_id=' . $clean_gallery_id, __FILE__);

Please note that the line number above refers to the current version of WP-Juicebox (v1.5.1).

I hope this helps.

917

(1 replies, posted in Juicebox-Lite Support)

When I create a new gallery and add new images, it gets stuck with processing images after two or three images.

It sounds like JuiceboxBuilder-Lite is choking on a certain image (or images).
If you try to add a batch of images more than once, does JuiceboxBuilder-Lite stop processing then images on the same image number each time?

Here are a few things to check and try which should hopefully point you in the right direction.

(1) Try adding your images in small batches to try to find a specific image that JuiceboxBuilder-Lite fails to successfully process. You may have one or more images that are somehow corrupt (perhaps just even corrupt metadata could prevent JuiceboxBuilder-Lite from successfully processing images).

(2) If you find an image that causes the problem, then try resaving it in an imaging program (such as Adobe Photoshop) to see if this resolves the problem.

(3) Also, if you find a problematic image (or have a small batch of images that consistently fails), please zip the image(s), upload the file somewhere and provide a download link so that I can try to replicate the problem with the same images that you are using.

(4) Try creating a fresh gallery with a completely different image source (maybe a different camera or phone or perhaps just some sample images from the internet) to see if the problem still occurs.

These suggestions might not solve your problem but they should at least help to narrow down possible causes.

918

(3 replies, posted in Juicebox-Pro Support)

Can you tell me what is wrong?

You need to give your 'juicebox' object a variable name so that you can refer to it via the Juicebox-Pro API.
You can name your 'juicebox' object whatever you like but, in my sample, code, I used the variable name 'jb' so just change:

new juicebox({

... to:

var jb = new juicebox({

Also, is there a way to make the added showThumbPage textbox be inside the dark area, so it looks like a part of the web page?

It would not be easy to integrate a new HTML element inside the gallery. Juicebox has not been designed with this in mind and there's no obvious place for it to go.
However, you could perhaps use the Gallery Title to display your thumbnail page input box and button.
If you then position the Gallery Title in the TOP area (a reserved area at the top of the gallery where the Gallery Title, Button Bare and Back Button can be positioned, then it would not overlap any other gallery elements.
(You would lose the ability to display a Gallery Title in the gallery, though.)
Try the following:

<!--START JUICEBOX EMBED-->
<script src="jbcore/juicebox.js"></script>
<script>
    var jb = new juicebox({
        containerId: 'juicebox-container',
        galleryTitlePosition: 'TOP',
        galleryTitle: '<div id="input"><input id="index" type="text" /><span>&nbsp;</span><input id="show" type="button" value="Show" /></div>'
    });
    jb.onInitComplete=function() {
        $('#show').click(function() {
            var index = $('#index').val();
            jb.showThumbPage(index);
        });
    };
</script>
<div id="juicebox-container"></div>
<!--END JUICEBOX EMBED-->

Otherwise, you could include your thumbnail page input box and button in a header above the gallery on your web page.
You could give the header a fixed height and then have the gallery resize to fill the remaining space in the browser window (similar to the View Resizable Gallery with Top Menu Example in the Using a Resizable Gallery with a Header support section).
Here's a sample 'index.html' file that you can use (or copy/modify to suit your own needs).

<!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" />
        <style type="text/css">
            html, body {
                height: 100%;
                overflow: hidden;
            }
            body {
                background-color: #222222;
                margin: 0px;
            }
            #header {
                background-color: #222222;
                color: #666666;
                font-family: sans-serif;
                font-size: 20px;
                height: 50px;
                padding: 10px 0px;
                text-align: center;
                width: 100%;
            }
            #wrap {
                width: 100%;
            }
        </style>
        <script type="text/javascript" src="jbcore/juicebox.js"></script>
        <script type="text/javascript">
            var jb;
            function doLayout() {
                var windowHeight = parseInt(window.innerHeight ? window.innerHeight : $(window).height(), 10);
                var headerHeight = parseInt($('#header').outerHeight(true), 10);
                var galleryHeight = windowHeight - headerHeight;
                $('#wrap').height(galleryHeight);
            }
            $(document).ready(function() {
                $(window).resize(doLayout);
                jb = new juicebox({
                    containerId: "juicebox-container"
                });
                $('#show').click(function() {
                    var index = $('#index').val();
                    jb.showThumbPage(index);
                });
                doLayout();
            });
        </script>
        <title>Test</title>
    </head>
    <body>
        <div id="header">
            <input id="index" type="text" />
            <span>&nbsp;</span>
            <input id="show" type="button" value="Show" />
        </div>
        <div id="wrap">
            <div id="juicebox-container"></div>
        </div>
    </body>
</html>

Also, why on earth does the index.html generated by Juicebox have the <script>...</script> in the <body>...</body> instead of the <head>...</head> area?

It does not actually make any functional difference whether the embedding code is in the <head> or <body> section.
JuiceboxBuilder puts the <script> section in the <body> alongside the Juicebox container <div> (which must be in the <body>) to keep all the embedding code together so that it can be copied and pasted (if necessary) in a single chunk.

Please provide more specific guidance than "smaller batches."  Does that mean 60 or 100 or 200 or ...?

Unfortunately, there are no specifics that I can give you. The best that I can suggest is that you use some trial and error to figure out what is safe for your system. If you find that JuiceboxBuilder does not crash when adding 250 images at once (for example), then it would be safer to limit your batches to 200 images at a time (to factor in an element of safety). I realise that this is less than ideal but it should prevent the application from crashing when you near the end of adding your batches.

What is the relevant measure of "smaller"?  Number of images?  Total size of all images selected? Something else?

I expect the relevant factor is the total filesize of the images in the batch but this is just speculation on my part. I have no access to the JuiceboxBuilder source code and do not know the exact reason for the problem (so cannot easily figure out a 100% safe workaround).

Please enhance the sofware with a warning that too many files are being added and tell me to select fewer.  Don't just crash!  Check when the crash becomes likely and let me have another chance.

The developer are aware of this issue but I do not know when it might be addressed.
To collect more data on the issue, please let me know how many images you can add before the application crashes and what the total filesize of the batch is.
Also, please let me know what platform (Mac vs PC), operating system/version (e.g. macOS 10.13 or Windows 10 1809) and architecture (32-bit vs 64-bit) you are using and how much RAM your system has.
Thank you.

Does the Lightroom plugin have the same limitation?

No. As far as I am aware, the problem is a limitation specific to Adobe AIR (the platform on which JuiceboxBuilder runs).

If not, is there a way to collect all the settings and apply them in LR?

There is no way to migrate configuration option values from JuiceboxBuidler to Lightroom but, once you have a gallery set up in Lightroom, you can save the settings as a template and apply the template to future galleries (just like a 'Preset' in JuiceboxBuilder).

To set a template in Lightoom:
Once you've got a gallery configured that way you'd like it to be in Lightroom (using the individual controls in the Lightroom plugin's interface), you can save the combination of configuration options as a Lightroom template by clicking the + sign to the right of the text 'Template Browser' (in the left panel of the 'Web' section) and selecting a name for the template.
At any time in the future, if you want to apply this combination of configuration options to a gallery, expand the 'Template Browser' control panel, scroll down to the 'User Templates' section and select the template.

920

(3 replies, posted in Juicebox-Pro Support)

You could use the Juicebox-Pro API (specifically the showThumbPage() method) to jump straight to a certain thumbnail page.
Here's an example which allows the user to enter a thumbnail page number into an input box and when the 'Show' button is clicked, the chosen thumbnail page is displayed.
Just create a sample gallery in JuiceboxBuilder-Pro (with enough images that multiple thumbnail pages will need to be displayed) and use the following code as your gallery's 'index.html' file.

<!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" />
        <style type="text/css">
            body {
                margin: 0px;
            }
        </style>
        <script type="text/javascript" src="jbcore/juicebox.js"></script>
        <script type="text/javascript">
            var jb = new juicebox({
                containerId: "juicebox-container",
                galleryHeight: "400",
                galleryWidth: "600",
                showPagingText: "TRUE",
                showThumbsOnLoad: "TRUE"
            });
            $(document).ready(function() {
                $('#show').click(function() {
                    var index = $('#index').val();
                    jb.showThumbPage(index);
                });
            });
        </script>
        <title>Test</title>
    </head>
    <body>
        <div id="input">
            <input id="index" type="text" />
            <span>&nbsp;</span>
            <input id="show" type="button" value="Show" />
        </div>
        <div id="juicebox-container"></div>
    </body>
</html>

This example is purely to demonstrate functionality.
You can adapt and style the method of input to suit your own web page.

I hope this helps.

921

(1 replies, posted in Juicebox-Pro Support)

A frame-driven website is likely to be less than optimal on mobile devices (as you have discovered) and, additionally, there are drawbacks to loading a Juicebox gallery into an frame. These drawbacks are noted here (scroll down to "2) Using an iframe").

If possible, it would be much better to layout your page using CSS rather than frames and to embed the gallery directly into the web page following the embedding instructions here.

If you are looking to have a web page with a side menu, then I would recommend taking a look at the View Resizable Gallery with Side Menu Example in the Using a Resizable Gallery support section.
You can view the source of the sample web page in your browser and copy/modify it to suit your own needs.

If you are looking for an automated way to create your complete website, you might be interested in another one of our products, namely Showkase.

Showkase is a PHP web application (installed on your web server instead of your computer) which allows you to create a complete portfolio web site (integrating multiple galleries) online.
Showkase has full support for Juicebox-Pro 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.
You can check out the Showkase interface by logging into the Live Demo Admin.

Showkase comes with several different themes, (Boma, Kosel, Maribo) and Boma features a side menu (whereas Kosel and Maribo both feature a top menu). Here is a sample site created in Showkase with the Boma theme.

Showkase can be purchased as Showkase-Standard (which comes with Juicebox-Lite, the free version) or Showkase-Pro (which comes with Juicebox-Pro).
The only difference between Showkase-Standard and Showkase-Pro is the bundled viewer (Juicebox-Lite vs Juicebox-Pro).

I hope these notes help.

922

(5 replies, posted in Juicebox-Lite Support)

That's great! I'm sure you'll get on well with Juicebox-Pro.
If you get stuck with anything, just post a new topic in the Pro forum and I'll do my best to help you out.

923

(7 replies, posted in Juicebox-Pro Support)

You're welcome.
I hope the workaround isn't too inconvenient.

924

(5 replies, posted in Juicebox-Lite Support)

Can I add a page or screen number to it, like "Page 20 of 30"

Yes. Just set showPagingText="TRUE" (in JuiceboxBuilder-Pro's 'Customize -> Thumbnail' section).
Here's a sample gallery using this setting.

Yes, I'd rather not have multi-size, so would I have to do anything manually, or is assign a unique linkURL for each image something that an option tells Juicebox to do?

You would need to set the linkURL entries for your images (on JuiceboxBuilder's 'Images' tab) and provide (and upload to your web server) the images that your linkURL entries point towards.

A linkURL can be an absolute path (in the form http://www.example.com/images/image_0001.jpg) or a relative path (relative to the web page containing the gallery's embedding code).

Juicebox will automatically use the linkURL entries in the following scenarios:
(1) showOpenImageButton="TRUE" and the Open Image button is clicked (Lite and Pro).
(2) imageClickMode="TRUE" and the main image is clicked (Pro only).
(3) showDownloadButton="TRUE" and the Download Button is clicked (Pro Only).

Should we move this to Juicebox-Pro?

Don't worry about it. You are currently using Juicebox-Lite so your query is just fine here!

925

(5 replies, posted in Juicebox-Lite Support)

Is there a way to have 20 or maybe 50?

This is possible only with Juicebox-Pro (but not Juicebox-Lite, the free version).

With Juicebox-Pro you can set the thumbsPosition (the position of the thumbnails: TOP, BOTTOM, LEFT or RIGHT) and maxThumbRows and maxThumbColumns.

When thumbsPosition is set to either LEFT or RIGHT, the number of thumbnail columns is fixed at the maxThumbColumns value whereas the number of thumbnail rows is variable (up to the maxThumbRows value) depending on the dimensions of the thumbnails and the space available in the user's browser.
Take a look at this demo gallery with 3 columns of thumbnails: https://www.juicebox.net/demos/pro/simp … umbRows=10

When thumbsPosition is set to either TOP or BOTTOM, the number of thumbnail rows is fixed at the maxThumbRows value whereas the number of thumbnail columns is variable (up to the maxThumbColumns value) depending on the dimensions of the thumbnails and the space available in the user's browser.
Take a look at this demo gallery with 3 rows of thumbnails: https://www.juicebox.net/demos/pro/simp … ion=CENTER

I also want clicking on the larger image (or somewhere) to open the full sized full resolution image in a separate browser tab.

With Juicebox-Pro, you can create a Multi-Size Image gallery.
The Medium images will be displayed in the gallery and the Large images will be displayed when the images are opened on pages of their own.
If you do not want a Multi-Size Image gallery, then you can assign a unique linkURL for each image (which you could point towards a large image).

Set imageClickMode="OPEN_URL" (in JuiceboxBuilder-Pro's 'Customize -> Main Image' section).
If the image has a linkURL associated with it, then, when the main image is clicked, the linkURL will be opened in the linkTarget window (_blank, _self, _parent or _top). Otherwise, the largeImageURL will be opened and, failing that, the imageURL (the actual image used in the gallery) will be opened.

In Juicebox-Lite, you can use the Open Image button. (In Juicebox-Lite, it is not possible to change the image click functionality.)
Set showOpenButton="TRUE" (on JuiceboxBuilder-Lite's 'Customize' tab) to display the Open Image button on the gallery's Button Bar.
You can set a linkURL and linkTarget (click an image's thumbnail on the 'Images' tab to reveal the input fields at the bottom of the window) for each image.
You'll need to provide the large images yourself and ensure that your linkURL entries point towards them (with either absolute or relative paths).

I hope this helps to clarify things.
Please let me know if you have any further queries.