101

(3 replies, posted in Juicebox-Pro Support)

I doubt it's corrupted,

Indeed. If you were able to extract the Juicebox-Pro zip file without any errors then it's unlikely that your JuiceboxBuilder-Pro.air file is corrupt.
Your SHA256 checksum is correct for JuiceboxBuilder-Pro v1.5.1. However, there is a slightly more recent version (technically v1.5.1.2 but still labelled as v1.5.1 within JuiceboxBuilder-Pro) which you might like to try.

You can download it using your original download link. Upgrades are free within the same major version number you purchased and download links always point towards the latest version rather than the version you purchased. If you can't find your download link or it has expired, then please fill in the Download Link Request Form and we'll send you a new one.

You'll find checksums for the v1.5.1.2 zip and AIR files here.

If this does not help, then there are some hints and tips in the 'Troubleshooting JuiceboxBuilder installation and usage problems' forum post here.

The suggestions in the post which I think may be most relevant to your problem are #4 (regarding the location of the JuiceboxBuilder installation file), #9 (regarding anti-virus programs) and #10 (regarding the system clock).

#4 Make sure that you have actually extracted the 'juicebox_pro_1.5.1.zip' file to your hard drive (rather than just looking inside the file with a zip program or with Windows File Explorer) and that you are not running the 'JuiceboxBuilder-Pro.air' file from a restricted file system or network drive.

#9 Try completely disabling any third-party security software that you might have installed (e.g. Avast or AVG), including real-time protection and ransomware detection, before attempting to install JuiceboxBuilder-Pro in case this may somehow be interfering with the JuiceboxBuilder-Pro installation. (Please do so at your own risk and be sure to disconnect from the internet first.)

#10 Check that your system clock is accurate (and resync with a known time server if necessary) before attempting to install JuiceboxBuilder-Pro. (One user actually claims to have had to wind back his system clock 2 years in order to install JuiceboxBuilder-Pro. This seems to have been an isolated incident and no-one is quite sure why this was necessary but it might be something worth trying if nothing else works.)

Can I expect this to work fully?

It's certainly not something I'd recommend but I think it should be OK.
As far as I am aware, the JuiceboxBuilder-Pro installer does not add any entries to the Windows registry so as long as all the files are in place, things should work OK.
Please note that this is not an official 'yes' and it is untested but I don't foresee any problems with it (other than the lack of an automated shortcut and uninstall entry).

Hopefully my notes above will help you to install JuiceboxBuilder-Pro using the regular AIR installer file.
Please let me know how you get on and if I can be of any further assistance.
Thank you.

Nice!
I'm glad that you've got things working. Thank you for posting back to let me know. It's most appreciated.

Thanks for trying. I'm sorry it didn't work.

The good news is that Juicebox galleries do work with "Enable HTTPS-Only Mode in all windows" in Firefox on https:// sites.
Check out our demo galleries here: https://juicebox.net/demos/
Every gallery displays and functions OK.

The problem seems to lie somewhere within your own website.
Unfortunately, we're in uncharted territory here as no-one has reported this before (as far as I can recall) and I don't know what's causing it so were going to have to do some trial and error to try to track the problem down.

First of all, try completely removing the Juicebox embedding code from your web page and see if the rest of your web page displays OK.

One thing I notice is that at the foot of your gallery page, you have some Statcounter code which includes a couple of http:// links (not https://) in two separate <noscript> sections.
Try changing them to https://. Maybe this is breaking the page in HTTPS-Only Mode.
In your Auto Body Repair page (for example), I see that the Statcounter links are https:// (and not http:// like in your gallery page).

I'll keep my fingers crossed that this helps.

Thank you for posting your troubleshooting results.
I see the problem when I "Enable HTTPS-Only Mode in all windows" in Firefox.

Here are a couple of suggestions which might hopefully help.

Try changing your embedding code to:

<script src="//www.superiorfleetbodyrepair.com/photogallery/jbcore/juicebox.js"></script>
<script>
    new juicebox({
        baseUrl: '//www.superiorfleetbodyrepair.com/photogallery/',
        containerId: "juicebox-container",
        galleryWidth: "100%",
        galleryHeight: "1000",
        backgroundColor: "rgba(255,255,255,1)"
    });
</script>
<div id="juicebox-container"></div>

The leading double slash in the paths will inherit the protocol from the page's URL.

Failing that, try hard-coding https:// into the paths:

<script src="https://www.superiorfleetbodyrepair.com/photogallery/jbcore/juicebox.js"></script>
<script>
    new juicebox({
        baseUrl: 'https://www.superiorfleetbodyrepair.com/photogallery/',
        containerId: "juicebox-container",
        galleryWidth: "100%",
        galleryHeight: "1000",
        backgroundColor: "rgba(255,255,255,1)"
    });
</script>
<div id="juicebox-container"></div>

I hope that helps.

Your gallery displays OK in my own Firefox browser (Firefox 119.0.1 Windows 64-bit) and I see no problem with the embedding code.

Try completely clearing your browser's cache and reloading the web page to see if this makes a difference.

Please let me know how you get on. Thank you.

Unfortunately, an error 500 is a rather generic server error which doesn't really help to pinpoint the cause of the problem.

I think the best course of action at the moment would be to install and run the Showkase Server Compatibility Test.

Even if you ran the test prior to initially installing Showkase, please run it again just now in case your web host has made any changes to your hosting account recently which might somehow be contributing to the problem.
If any of the tests fail, there are troubleshooting tips on the test's support page (link above).

Please let me know how you get on.

If the error message is correct, then you might need to increase your PHP memory_limit.

Please check to see what the PHP memory_limit on your web server is currently set to and try increasing it. (Your web host should be able to help you out with this.)
You can check your PHP settings using phpinfo() documented here: https://www.php.net/manual/en/function.phpinfo.php

The default value for memory_limit in the current version of PHP is 128M (as noted here: https://www.php.net/manual/en/ini.core. … ce-limits) so if yours is lower than this, I would recommend increasing it to 128M to see if this helps.

Also, please check post_max_size and upload_max_filesize and try increasing their values, too.

The following quote is from the description of post_max_size in the PHP documentation here: https://www.php.net/manual/en/ini.core. … t-max-size

post_max_size int
    Sets max size of post data allowed. This setting also affects file upload. To upload large files, this value must be larger than upload_max_filesize
.

Please check with your web host to find out how to change PHP settings on your web server.
You might be able to do this with a php.ini file or via your web hosting account's online control panel.

I hope this points you in the right direction.
However, if you continue to experience difficulties, please post back to let me know your Showkase version number and your PHP version number.
Also, if possible, please provide the source image that is causing the problem so that I can try to replicate the problem myself (in case the image is somehow corrupt). If you don't want to upload the image publicly, you can contact me at steven@juicebox.net.
Thank you.

I've just checked my email and see that you've already filled in the Download Link Request Form.
Thanks!

Hi.

I've reactivated your download link (and sent you a separate email containing the link).

You can find instructions for installing the Juicebox Plugin for Photoshop here: https://www.juicebox.net/support/photoshop/

If you encounter any problems installing via Adobe Exchange, then just use the manual method of installation noted under the heading "Photoshop CS2 to CS6".

The plugin files are the same for the CS2/CS6 version as for the CC version, it's just the method of installation that differs.

Incidentally, if you ever need a new download link in the future, just fill in the online Download Link Request Form (https://www.juicebox.net/admin/download_request/) and we'll send you a new one.

I hope this helps.

110

(3 replies, posted in Juicebox-Pro Support)

You're welcome!

111

(3 replies, posted in Juicebox-Pro Support)

Here's (probably) the easiest way to do it:

(1) Copy your gallery folder.
(2) Open one of the gallery folders in JuiceboxBuilder-Pro (see here for details).
(3) On the 'Images' panel, delete the images that you don't want in your first gallery. You can select an image with a single left-click and you can also Ctrl+Click a selection of images or Shift-Click a block of images. You can then delete the images(s) via Crtl+D or 'Images -> Delete' from the drop-down menu at the top.
(4) Re-save the gallery on the 'Publish' panel.

Now repeat the process with the other gallery folder and delete the images you don't want in your second gallery.

(Incidentally, you can do this manually by editing the gallery's 'config.xml' file in a plain text editor and manually removing <image> tags (and then deleting the corresponding images and thumbnails from the 'images' and 'thumbs' folders) but using JuiceboxBiulder-Pro to automate the process is easier.)

You might want to keep a copy of your complete original gallery as if you delete an image, you'll lose the image's caption and if you decide to re-add the image to the gallery at a later date, you'll need to manually re-add it's caption, too.

Also, I don't know if you already do this but you might like to embed your captions within your images as IPTC metadata.
That way, the caption text will become part of the image file itself and wherever the image goes, the caption goes too.
JuiceboxBuilder-Pro has the ability to extract the IPTC Document Title as the image title and the IPTC Description as the image caption (so image titles and captions can quickly be set without any manual entry) via the 'Images -> Titles -> Use IPTC Title' and 'Images -> Captions -> Use IPTC Caption' options from the drop-down menu at the top.
You can add IPTC data to images (multiple images at once) in imaging programs such as Adobe Lightroom and Photoshop.
Please note that when instructing JuiceboxBuilder-Pro to extract IPTC metadata, all image captions are processed at once (it is not possible to extract IPTC metadata on an image-by-image-basis).

I hope this helps.

112

(1 replies, posted in Juicebox-Pro Support)

Please fill in the Download Link Request Form (I can't find a transaction with the email you use here in the forum) and I'll send you a new download link. Thanks!

Download Link Request Form: https://www.juicebox.net/admin/download_request/

113

(3 replies, posted in Juicebox-Pro Support)

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

114

(3 replies, posted in Juicebox-Pro Support)

Please see this forum post for a description of the problem and a solution.
https://juicebox.net/forum/viewtopic.ph … 223#p18223

115

(12 replies, posted in Juicebox-Pro Support)

Not yet, sorry.
The Fotomoto functionality is baked into the 'juicebox.js' JavaScript file (which is packed and obfuscated) and it's not user-changeable so we'll need to wait on a new release. (Still no news on that front, I'm afraid.)

116

(5 replies, posted in Juicebox-Pro Support)

Set showImageNav="NEVER" ('Customize - Main Image').

117

(5 replies, posted in Juicebox-Pro Support)

I think you're probably referring to the gallery's Button Bar.
Try setting buttonBarPosition="NONE" (in JuiceboxBuilder-Pro's 'Customize -> Button Bar' section).

118

(5 replies, posted in Juicebox-Pro Support)

Yes, you should be able to embed a Juicebox gallery into a <td> table cell.
The easiest way to do this would be to assign fixed pixel dimensions to your galleryWidth and galleryHeight, e.g.:

<table>
    <tr>
        <td>
            <script src="jbcore/juicebox.js"></script>
            <script>
            new juicebox({
                containerId: 'juicebox-container',
                galleryWidth: '600',
                galleryHeight: '400',
                backgroundColor: 'rgba(34,34,34,1)'
            });
            </script>
            <div id="juicebox-container"></div>
        </td>
    </tr>
</table>

If you use a percentage for your galleryHeight (for example) such as 100%, then you might need to make sure that all parent containers of the gallery (e.g. <tr> and <table> up to and including the <body> tag) have a height specified via CSS, otherwise Juicebox and the browser might not know what the gallery's actual height should be 100% of.

Here are updated font files for those wishing to use the new Twitter icon (X instead of the bird).
Just extract the attached file (fonts.zip) and replace the fonts folder in your gallery's jbcore/classic/ folder.
You might need to clear your browser's cache to see the change but no other modifications are necessary.

That's great! Thank you for posting back to let me know. It's most appreciated.

When I get to the “Publish” option the screen just shows a preview of the Gallery I have created but there is no option to Save it to a specific folder.

Unfortunately, Harman, the current developers of AIR, have recently removed support for WebKit (the embedded browser which JuiceboxBuilder uses for the live gallery preview on the Customize panel) from the AIR runtime package.
The symptoms you describe in your quote above (content from the Customize tab obscuring content on the Publish tab) are a result of using the very latest version of AIR (v50.2.1.1) which does not include WebKit support.

The solution is to use the most recent version of AIR with WebKit support. This is currently AIR v33.1.1.744.
Harman have made this available at the foot of their AIR runtime download page: https://airsdk.harman.com/runtime
Here are direct links to AIR v33.1.1.744 (I include the Windows link for any PC users reading this thread and encountering similar issues):
Mac: https://airsdk.harman.com/assets/downlo … obeAIR.dmg
Windows: https://airsdk.harman.com/assets/downlo … obeAIR.exe

Please be sure to uninstall AIR v50.2.1.1 first before installing AIR v33.1.1.744.

Incidentally, I have noted this in sticky posts at the top of both the JuiceboxBulder-Pro and JuiceboxBuilder-Lite forums:
JuiceboxBuilder-Pro: https://juicebox.net/forum/viewtopic.php?id=5318
JuiceboxBuilder-Lite: https://juicebox.net/forum/viewtopic.php?id=5319

According to this comment (over in the Harman Github Issues pages), it looks like Harman are currently looking to replace WebKit with a new embedded browser: https://github.com/airsdk/Adobe-Runtime … 1216482803

We've been looking at enabling third-party html rendering engines to be hooked into AIR so that the earlier behaviour could be restored...

If/when Harman implements this, there will no longer be a need to use AIR v33.1.1.744, although there is no problem in sticking with AIR v33.1.1.744 as JuiceboxBuilder actually requires only AIR v2.0 or later to function fully.

...all kinds of warnings about Adobe Air might “damage my computer”.

Unfortunately, I'm really not sure what might be triggering these warnings. We've not had reports of similar warnings from any other users.
Using AIR v33.1.1.744 should hopefully resolve your problem, though.

Please let me know how you get on and if I can be of any further assistance.
Thank you.

You're welcome! I'm happy to help if I can.
I know my reply won't instantly solve your problem but I hope that it might shed some light on things from a Juicebox perspective.

Thinking more about your problem, it's certainly possible that a buggy PHP script could be responsible for high memory and CPU usage so the first thing I'd do is update all your active plugins, your current theme and WordPress itself in case a bug in a version that you are using has been fixed.

I hope that you are able to track down the root of your problem.

As I'm sure you're aware, there is no actual limit to the number of galleries you can have on a site (or a page) but finite resources in a real world scenario could prove to be a restrictive factor.

Unfortunately, every server is different (with different limits) and each user's galleries are different (with different numbers of images at different filesizes) so it's really difficult to give you a number as to how many galleries is too many.

Having said that, if you only have one gallery per page, then there really shouldn't be a problem at all.
The browser will just be parsing one page at a time (as and when they are viewed) and, thus, only one gallery will be consuming resources at any one time. Galleries on other pages should have no bearing on this problem.
As far as I can see, a problem regarding gallery numbers would only occur if you were displaying multiple galleries on a single page, (i.e. multiple galleries were all being loaded at the same time and many images would be preloaded at once).

Do you maybe have any plugins which preload web pages throughout your site before they are viewed (maybe preloading pages which are linked to from any particular page)? This could potentially cause a large server load (loading a lot of gallery pages in the background).

I notice that you already use imagePreloading="NEXT" in your galleries, preloading just the next image rather than all the images on the current thumbnail page (PAGE) or all the images in the gallery (ALL), so that's good. There's no need to change that.

There's really no other gallery confirmation options you could change that would help with such a problem.
Storing your images locally (instead of using Flickr) might make a difference but I realise that it would be a mammoth task to switch over to this method of image storage (and, to be honest, I really don't know if it would help... it's just something you could theoretically try).

Check your plugins, though. There's may be something there that's contributing to the problem.
As I mentioned above, if you only have one Juicebox gallery per page, then there really shouldn't be a problem (at least where Juicebox galleries are concerned).

No worries at all! Just glad to hear that you've got it working.
Thanks for posting back to let me know. It's most appreciated.

That's odd... I've just uploaded some images to a completely empty Flickr account, created an album/set (using just a couple of the uploaded images) and used the album/set id (grabbed from the URL) as the Flickr Set Id in JuiceboxBuilder-Pro. The album/set displayed as expected.

The only thing to note is that it took a good 5 or 6 minutes after uploading the images before they actually appeared in my Photostream but everything worked fine without a hitch.

The functionality certainly seems to be working OK (art least for me) but there are a couple of things you can do to try to troubleshoot your problem.

The first thing to do is to make sure that your images are public (and not private).

The next thing to do is to head on over to Flickr's own API Explorer (link below), enter your album/set id into the 'photoset_id' box (the second one down) and click the 'Call Method...' button.
There should be one <photo> tag for each and every image in your album/set shown in the output box.
If there are no images found, then there's definitely something wrong with your album/set at Flickr's end (if Flickr cannot find your images using the album/set id, then JuiceboxBuilder-Pro will not be able to do so either) and you might need to contact Flickr's own support team to figure out what's wrong.

Flickr API Explorer - flickr.photosets.getPhotos: https://www.flickr.com/services/api/exp … .getPhotos

I hope my notes above at least reassure you that the functionality should still be working OK (as it does for myself) and point you in the right direction.
If you continue to experience difficulties, then please let me know and I'll try to help further. (Are your images super-small or super-large? Maybe their size (in both filesize and/or resolution) has something to do with this? Perhaps you could try again with different images to see if this makes a difference.)