Using the standard Piwik analytics code will log hits to just the gallery's web page.

Setting enableDirectLinks="TRUE" in your gallery will give each image in the gallery a unique URL (using a # identifier at the end of the URL) but the web page is not refreshed/reloaded each time a new image is selected so the analytics code will not be rerun (it will be run only once when the web page is initially loaded).

You'll likely need to manually register a hit each time a new image is selected using the Juicebox-Pro API's onImageChange(e) event.

Keep the standard Piwik code in your gallery's web page and then use something like the code below:

<script type="text/javascript" src="jbcore/juicebox.js"></script>
<script type="text/javascript">
    var jb = new juicebox({
        containerId: "juicebox-container",
        enableDirectLinks: "TRUE"
    });
    jb.onImageChange = function(e) {
        var imageNumber = e.id;
        _paq.push(['trackEvent', 'Juicebox', 'Gallery', imageNumber]);
    };
</script>
<div id="juicebox-container"></div>

You might need to check with Piwik's Event Tracking support page for the correct JavaScript code to use (and you can change the terms 'Juicebox' and 'Gallery' to suit your own needs).

I hope this points you in the right direction.

If you drag and drop a selection of images into JuiceboxBuilder-Pro, then the initial order will start with the image that you actually click to initiate the drag and drop action (and then wrap around to the start of the selection).

For example, if you select:
DSC001
DSC002
DSC003
DSC004
... and then drag the selection into JuiceboxBuilder-Pro by clicking and dragging DSC003, the initial order will be:
DSC003
DSC004
DSC001
DSC002

At least this is the default action on my Windows PC. The same thing happens when I copy files from one folder to another (in Windows File Explorer): the copy process always starts with the file I initially click and drag within a selection (although if the sort order for the destination folder is by 'Name', then the images end up in the expected order and the copy process order is rarely noticed, especially if the files are small and the copy process is completed quickly).

You should be able to avoid this by dragging the selection into JuiceboxBuilder-Pro via the very first image in your selection (or by adding the images via the 'Browse...' button instead of dragging and dropping).

In any case, there's a very easy way to order the images (either by File Name or by File Date) once they are in JuiceboxBuilder-Pro.
Just go to 'Images -> Sort -> By File Name' or 'Images -> Sort -> By File Date' from the drop-down menu at the top.
Please see the screenshot attached.

I hope this helps.

With so many different ways to create a Juicebox gallery (the list of available plugins can be found here), having the plugins available separately avoids the need to update the core Juicebox package each time an individual plugin needs to be updated.

I hope that you've been able to install WP-Juicebox successfully.

A bug report has now been logged so the developers will address the issue in due course.
Thank you for reporting the bug.

Thank you for reporting this issue.
I cannot be sure if this is intended behavior or a bug but I have notified the developers.
Unfortunately, I do not know of a workaround (other than to always display the thumbnails) and, if it is indeed a bug, we may need to wait for the developers to fix it.
Thank you for bringing it to our attention, though.

I'm glad you're getting on well with Juicebox-Pro!

That'll work just fine but it's not actually using the firstImageIndex configuration option. What you are doing (adding #12, for example, to the end of the URL), is essentially using the enableDirectLinks functionality, a short description of which can be found in the General section of the Config Options page). (If you actually set enableDirectLinks="TRUE", then the # number will change in the browser's address bar to reflect the current image being displayed.)

If you wanted to use firstImageIndex, then you could either:
(1) Set a static value for firstImageIndex in your gallery's 'config.xml' file, e.g. firstImageIndex="12".
... or:
(2) Set firstImageIndex in your gallery's embedding code (see here for more information on setting configuration options) either as a static value or a JavaScript variable, e.g.

<!--START JUICEBOX EMBED-->
<script src="jbcore/juicebox.js"></script>
<script>
    new juicebox({
        containerId: "juicebox-container",
        galleryWidth: "100%",
        galleryHeight: "100%",
        backgroundColor: "#222222",
        firstImageIndex: "12"
    });
</script>
<div id="juicebox-container"></div>
<!--END JUICEBOX EMBED-->

If yourfirstImageIndex value is variable, then you might need to pass the variable to the gallery's web page via a query string in the URL or a session cookie, in which case it would be much easier to continue using the # notation (the enableDirectLinks functionality) that you currently use.

You can enable the Back Button in Small Screen Mode (when the gallery is displayed on mobile devices) by setting showSmallBackButton="TRUE" (in JuiceboxBuilder-Pro's 'Customize -> Back Button' section).
However, please note that the Back Button will be displayed only on the main image pages in Small Screen Mode (and not on the Splash Page or the thumbnail pages).
Y
ou could, if you like, force the gallery to be displayed in Large Screen Mode on all devices and in all browsers by setting screenMode="LARGE" (in JuiceboxBuilder-Pro's 'Customize -> General' section) where the Back Button should always be present.

Unfortunately, there is no easy way to introduce new swipe gestures within a Juicebox-Pro gallery.
Hopefully setting showSmallBackButton="TRUE" will be a suitable workaround for you, though.

Facebook opens images in a pop-up window and Esc closes the pop-up.
I'm not exactly sure how this would relate to Juicebox but you should be able to use the Esc key to close an expanded gallery (for example a gallery expanded from a Splash Page or an embedded gallery expanded to fill the browser window or screen) to go back to the gallery's original (unexpanded) state.

If you like, please feel free to post suggestions for future versions in the Feature Requests forum thread.
This keeps all the ideas together and ensures that they are not overlooked by the developers.
I do not know the likelihood of any suggestions being implemented in future versions but this is certainly the best place for all ideas.
Thank you.

That's great! Thank you for letting me know.

The only entities which are part of the XML standard are:

' (')
" (")
& (&)
&lt; (<)
&gt; (>)

All other similar looking entities, such as ü, are part of the HTML standard (rather than XML).

If you try using ü (without CDATA tags) in a gallery's 'config.xml' file and open the XML file directly in a browser, you'll see that the HTML entity breaks the XML syntax with an error message such as "XML Parsing Error: undefined entity".
It's an XML issue rather than a Juicebox issue.
However, as long as you wrap your image titles (or captions) in CDATA tags, your HTML entities will be displayed (in your gallery's HTML web page) as expected.

If you are using JuiceboxBuilder-Pro to enter your image titles and captions, then you should be able to enter either ü (copy and paste the actual character) or ü (on the 'Images' tab) and both should work fine. (I've just checked this myself and it works for me.)

If you are editing your gallery's 'config.xml' file manually in a plain text editor and are using &uuml;, be sure to use CDATA tags (<![CDATA[ ... ]]>) within your <title> or <caption> tags (incidentally, Juicebox does not support <comment> tags). CDATA tags are not required if you just use the ü  character directly (but it would be good practice to just always use CDATA tags anyway, as JuiceboxBuilder-Pro does).

For example, the following image titles should work fine.

<title><![CDATA[&uuml;]]></title>

<title><![CDATA[ü]]></title>

<title>ü</title>

... but the following image title will not work:

<title>&uuml;</title>

I hope this helps.

It might be worth posting your suggestion in the Feature Requests forum thread where it will be seen by the developers.
I do not know the likelihood of any suggestions being implemented in future versions but this is certainly the best place for all ideas.
Thank you.

Unfortunately, there are no configuration options available to change the font size of image titles and captions.

However, you can style individual image titles and captions (for example, to change the font-size) using HTML formatting as noted in this FAQ:
How do I add HTML formatting to image captions and titles?

A sample caption with a font-size of 12px (for example) would look like this:

<span style="font-size: 12px;">Image caption text goes here.</span>

In the gallery's XML configuration file, the caption would look like this:

<caption><![CDATA[<span style="font-size: 12px;">Image caption text goes here.</span>]]></caption>

... but the Drupal module should automatically add the <caption> and CDATA tags so you should only need to enter the <span> tag (as above).

Otherwise, you can set the size of all image titles and/or captions at once using CSS such as the following (changing the numeric values as appropriate):

/* IMAGE TITLE */
.jb-caption .jb-caption-title {
    font-size: 20px !important;
}

/* IMAGE CAPTION */
.jb-caption .jb-caption-desc {
    font-size: 18px !important;
}

/* IMAGE NUMBER */
.jb-cap-frame .jbac-number {
    font-size: 12px !important;
}

You could add this CSS to the end of your gallery's 'jbcore/classic/theme.css' file or wrap it in <style type="text/css"> ... </style> tags and add it to the end of your gallery web page's <head> section (if you have access to this within your Drupal site).