Please see my reply to your query in this forum thread.

For reference, instructions for installing the Juicebox plugin for Lightroom can be found on the plugin's support page here.

On a Windows PC, you should be able to drag and drop the 'juicebox_lite.lrwebengine' folder onto the Lightroom desktop shortcut. Lightroom should then open with an 'Install Web Layout Style' dialog box.

The 'juicebox_lite.lrwebengine' folder can be found inside the Juicebox-Lite zip package in this location: juicebox_lite_1.4.4.2\adobe-lightroom-plugin\juicebox_lite.lrwebengine.

If this does not work, then you can still install the plugin manually by copying the entire 'juicebox_lite.lrwebengine' folder into Lightroom's 'Web Galleries' folder.

The 'Web Galleries' folder can be found in this location: C:\Users\username\AppData\Roaming\Adobe\Lightroom\Web Galleries\
Note that it is in 'AppData\Roaming\' and not 'AppData\Local\'.

In order to navigate to the 'Web Galleries' folder in Windows File Explorer, you will need to show hidden files.

Alternatively, to get to the 'Web Galleries' folder:
(1) Open Lightroom
(2) Go to 'Edit -> Preferences' from the drop-down menu at the top
(3) Go to the 'Presets' tab
(4) Click the 'Show Lightroom Presets Folder...' button (the C:\Users\username\AppData\Roaming\Adobe\ folder will be opened in Windows File Explorer)
(5) Go inside the 'Lightroom' folder.
(6) Go inside the 'Web Galleries' folder.

The plugin will function exactly the same no matter whether it is installed automatically (via drag-and-drop) or manually.
Whatever method you use, just make sure that you use the 'juicebox_lite.lrwebengine' folder and not the 'adobe-lightroom-plugin' folder.

I hope this helps.

If you continue to experience difficulties, please let me know exactly what steps you take to see the "suchpfad nicht gefunden" message and when the message is displayed. Thank you.

If you are trying to display a new gallery created within the Google Photos interface (rather than trying to display a gallery that was originally created within the old Picasa interface), then you might need to enter the Album Id (instead of the Album Name) and this is not available within the new Google Photos interface.

Visit this URL in your browser and you'll get an RSS feed of your albums.
https://picasaweb.google.com/data/feed/api/user/<User Id>

If you then hover over (or click on) an album, you'll see a 19 digit number at the end of the URL. This is the Album Id which you can use in the WP-Juicebox interface.

I've tested this myself with an album I created today in Google Photos and it seems to work fine.
Here are the details if you'd like to try to display it yourself (just for testing purposes).
Google User Id: 109901943277912891450
Google Album Id: 6278925468933743905

I hope this helps.

Edit:
Also, visit https://picasaweb.google.com/<User Id>/<Album Id> (corresponding to the album that you are trying to display) and, in the right-hand sidebar next to the thumbnail representing the album, make sure that the visibility setting is 'Public on the web'. If the visibility is set to any other value (e.g. 'Limited' or 'Only you'), the click the 'edit' link and select 'Public on the web'.

This looks like it might be a timing issue caused by setting imageTransitionTime="1". If you use the default value of 0.3 instead, you should hopefully find that a URL ending with something like #21expanded displays the expected image.
I have notified the developers of this issue. However, please note that Juicebox was not designed to jump straight into expanded mode and it is not advisable to manually add #expanded to a URL. Juicebox should be expanded using the Expand Button (from a non-expanded gallery) so that it can be expanded appropriately depending on the device being used and configuration options such as expandInNewPage and useFullscreenExpand.

If you set debugMode: 'TRUE' in your gallery's embedding code, then you can set configuration options via a query string in the URL as noted in the Setting Config Options support section.
Your gallery's embedding code would look something like:

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

... and you could use a URL such as the following to set autoPlayOnLoad to FALSE:
http://www.example.com/gallery/index.ht … 21expanded

As you are using WP-Juicebox, you can add the debugMode configuration option to all of your galleries by opening the plugin's 'wp-juicebox.php' file in a plain text editor and changing line 285 from:

$string_builder .= '    var jb_' . $clean_gallery_id . ' = new juicebox({' . PHP_EOL;

... to:

$string_builder .= '    var jb_' . $clean_gallery_id . ' = new juicebox({ debugMode: "TRUE",' . PHP_EOL;

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

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

You can set the height for a gallery in the JuiceboxBuilder-Pro interface (in the 'Customize -> Lite' section).
The chosen height will be included in the embedding code presented on the 'Publish' tab (and in the gallery's 'index.html' page after the gallery has been saved) which you can copy and paste into your own web page.

You can certainly have multiple galleries with different heights embedded into a single web page.

Here's sample code for two galleries (with different heights) being embedded into the same page.
The first gallery on the page has a height of 400px whereas the second gallery on the page has a height of 600px.

<script src="gallery1/jbcore/juicebox.js"></script>

<script>
    new juicebox({
        baseUrl: 'gallery1/',
        containerId: 'juicebox-container-1',
        galleryHeight: '400px',
        galleryWidth: '100%'
    });
</script>
<div id="juicebox-container-1"></div>

<script>
    new juicebox({
        baseUrl: 'gallery2/',
        containerId: 'juicebox-container-2',
        galleryHeight: '600px',
        galleryWidth: '100%'
    });
</script>
<div id="juicebox-container-2"></div>

I hope this helps.

However, if you continue to experience difficulties, please post the URL to your web page so that I can see the problem for myself and hopefully help further.
Thank you.

Due to the nature of how Facebook works (taking the share image from an og:image tag in the web page), it would be very difficult for a gallery which is displayed from a single web page (such as a Juicebox gallery) to have the share image correspond to the image being shared.

As I mentioned above, although the share image (the thumbnail displayed in the Facebook pop-up share window) will always be the same one, the link being shared will still point towards the correct image in the gallery (the image currently being displayed in the gallery when the Facebook button is clicked).

For Juicebox, you really need to think of the share image as representing the gallery as a whole.
With this in mind, you could change the og:image tag in your gallery's web page to have the share image be any image you like. It does not need to be an image in your gallery.

If you really want to have the share image correspond to the image being shared, then you would need to find a gallery type which creates a separate web page for each image (so that each page/image can have its own og:image entry).
The downside to this type of gallery would be that it would likely be a standalone set of web pages rather than something that you could embed in an existing web page alongside other content (like you can with Juicebox).
Ideally, you would need to find a gallery that not only creates a separate web page for each image but also one that has built-in Facebook support so that og:image entries are generated automatically. Otherwise, it might be quite a time-consuming task to add an og:image entry manually for each image in your gallery.

Unfortunately, off the top of my head, I do not know of such a gallery type and a web search might be helpful.

Three weeks have passed and I have had not heard directly from ClamAV regarding the false positive reports I filed but there have been 23 ClamAV virus database updates in this period so, if you have not tried recently, it might be worth uploading a Juicebox album to your web server now to see if it works.
If you do try again, please let me know how you get on.
Thank you.

It is not possible to have the shared image's thumbnail displayed in the pop-up Facebook share window due to limitations imposed by Facebook on what data can be passed via their share URL. Only one thumbnail image can be used per web page. (The link will still point towards the correct image within your gallery, though.)

The image used in the pop-up Facebook share window is set using an Open Graph og:image meta tag in the <head> section of your web page, such as the following:

<meta property="og:image" content="http://www.example.com/images/thumbnail.jpg" />

Please see here for more details on the Open Graph protocol.

If you create a gallery with JuiceboxBuilder-Pro, an og:image meta tag will be automatically generated and included in the gallery's 'index.html' file (pointing towards the first image in the gallery). If you are embedding your gallery in an existing web page alongside other content, then you will need to add an og:image meta tag manually.

Although the thumbnail image displayed in the pop-up Facebook share window will always be the same one (specified via the og:image meta tag), the link being shared will still point correctly towards the shared image in the gallery. You should notice that the URL being shared ends with something like #2 or #17 where the number represents the image in the gallery. When a user clicks on a shared link, the corresponding shared image will be opened in the gallery.

No problem!

In order to not get the "Juicebox can not display locally in this browser." message, the gallery's web page must be viewed over http:// or https:// (or viewed in Firefox or Safari). If the file:/// protocol is used (as it would be for local use), the gallery will fail to display in any browser other than Firefox and Safari.

The gallery structure and location of the 'config.xml' and 'juicebox.js' files (and images) does not matter for this error message.

I'm guessing your mobile app is not loading the web page containing the gallery's embedding code over http:// or https:// (it sounds like everything is hosted locally within the app) which is probably where the problem originates.