In your http://www.reisedampfer.de/html5/norwegen_2014/ page, your gallery's embedding code uses the following line:

backgroundColor: 'rgba(204,204,204,1)'

However, when you embed the gallery in your http://www.reisedampfer.de/app595898963 … wegen-2014 page, the embedding code uses the following line (resulting in a white background):

backgroundColor: "rgba(255,255,255,1)"

Change the backgroundColor in the embedding code to either rgba(204,204,204,1) (to match the background color of your page) or rgba(0,0,0,0) (for the gallery's background to be fully transparent so that your own page's background shines through).

If you want to set a different color for the expanded gallery, use the expandedBackgroundColor configuration option (in JuiceboxBuilder-Pro's 'Customize -> Color' section).
Your gallery does not currently use an expandedBackgroundColor so the expanded background color will be the same as the normal (unexpanded) background color.

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

Rotation can certainly be challenging at the best of times and there seems to be little consistency between programs, even between browsers. (I've seen examples of images which display differently in Chrome and Firefox.)

Often, the best course of action is to strip the EXIF information (at least the orientation flag) from the image and then rotate it until it is visibly correct.

Please 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.
Thank you.

@ion.rogozea

Thank you for your suggestions.
Unfortunately, there is no built-in way to navigate between galleries within Juicebox.
(We have Showkase as an automated way to index and organize multiple galleries.)

Perhaps the easiest way to do something similar would be to include a link in the last image's caption.
For example:

<caption><![CDATA[<a href="http://www.example.com/gallery2/index.html" target="_self">Click here to view Gallery #2.</a>]]></caption>

First of all, I'd recommend upgrading to the latest version (v1.4.4.2) as many bugs have been fixed since v1.4.3.
Please see the Version History for a list of changes between versions.
Instructions for upgrading can be found on the Upgrading Juicebox support page.

If you want to disable the auto hide functionality of the image overlay overlay, set inactivityTimeout="0" (in the 'Customize -> Main Image' section).

If you want the image overlay to always be displayed, set showImageOverlay="ALWAYS" instead of its default value of AUTO ('Customize -> Main Image').

If you want the image navigation buttons to always be displayed, set showImageNav="ALWAYS" ('Customize -> Main Image'). The image navigation buttons can be positioned relative to the STAGE or the IMAGE via the imageNavPosition configuration option (also in the 'Customize -> Main Image' section).

I hope this helps.

For reference, a complete list of configuration options can be found here.

If you continue to experience difficulties, please post the URL to your gallery so that I can take a look.
Also, let me know what you see and what you expect (or hope) to see so that I can hopefully help further.
(I'm not sure which button you mean when you say "all of the buttons except the first".)
Thank you.

Unfortunately, not (at least not easily).
If you disabled the thumbnails and used only the main images, then only one main image would be displayed at any one time (although you could overlay the captions on top of the images and associate a unique link to each image).
If you hid the main images (it is not possible to disable them via configuration options), then although you could size the thumbnails as you like and display several in a row, it would not be possible to overlay the captions on top of the thumbnails (you would need to make the text part of the images themselves) and it would also not be possible to link thumbnails to different web pages. (When a thumbnail is clicked, the corresponding main image is displayed in the gallery.)

You could try something like the following (using the Juicebox-Pro API and knowledge of the internal classes of Juicebox) to open an image's linkURL when the corresponding thumbnail is clicked.
However, Juicebox was not designed to do this and a couple of small delays are necessary to get this to work.
You would also need to hide the main images via CSS.

<script type="text/javascript" src="jbcore/juicebox.js"></script>
<script type="text/javascript">
    var jb = new juicebox({
        containerId: "juicebox-container"
    });
    jb.onInitComplete = function() {
        window.setTimeout(function() {
            $('.jb-idx-thumb').click(function() {
                window.setTimeout(function() {
                    var index = jb.getImageIndex();
                    var info = jb.getImageInfo(index);
                    var url = info.linkURL;
                    window.open(url);
                }, 500);
            });
        }, 500);
    };
</script>

I hope this points you in the right direction but please note that Juicebox was not designed to do this so getting it working exactly as you want it to might be quite tricky.

You're welcome.
I'm glad I was able to point you in the right direction and that you're getting on well with Juicebox.

Thank you for spreading the word!

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

There are a couple of small errors in the code you posted above.

In your embedding code, change:

<script src=""/drupal8/sites/all/libraries/juicebox/juicebox.js">

... to:

<script src="/drupal8/sites/all/libraries/juicebox/juicebox.js">

In your 'config.php' file, change the opening:

?php

... to:

<?php

The 'config.php' file generates XML code (using the required syntax for a Juicebox gallery) and feeds it directly to the browser (without actually saving anything to your web server).

I have just tried using the 'config.php' file with the user information you posted above and it works fine, displaying a gallery with 32 images so once you make the small corrections I noted above, it should work fine for you, too.

Your gallery is certainly using the Pro files (there is no Juicebox badge/link in the lower-right corner of the gallery) and when I view your gallery, it displays 127 images.
If you are still seeing only 50, then please double-check that you have completely cleared your browser's cache and history before reloading your gallery's web page or try using a different browser (which you have not yet used to view your gallery) as a test. It sounds like your browser is still using a cached version of the Lite 'juicebox.js' file.
Hopefully this will help.

That's great!
I see no problem with your logic and I would expect this to work fine (as confirmed by your own tests).
I'm glad you've got it working as you like.
Thank you for sharing your solution!

When using a PHP script as a configURL, Juicebox should not use the dynamic XML file until it is complete. As long as the PHP script is generated in a timely manner and is complete with no syntax errors, the gallery should display OK.
An incomplete dynamic XML file (perhaps due to a server timeout) may produce a blank area where the gallery should be.

I just had a folder of 18 images on my server and had a PHP script randomize the order of them and then display the first 8. I did not use a database.

I suspect (but am not certain) that the problem may be a side-effect of the following fix from v1.4.3:

(Please see the Version History for a full list of changes between versions.)
Prior to v1.4.3, if randomizeImages="TRUE", the image order would change when the gallery was expanded (whether browser caching was enabled or not). This was unwanted behavior which really had to be fixed.

I think you may need to have your web server allow browsers to cache files in order for your scenario to work correctly.
If your PHP script did not choose images from a pool of many but just randomized a complete set of images, then you could set randomizeImages="TRUE". I realise that this will not work with your scenario but I thought I should point it out in case it helps and somehow points you towards a suitable solution or workaround.