1

(1 replies, posted in Juicebox-Lite Support)

Hello.

We are a software company with a web gallery product named Juicebox-Pro.
From the information that you provided, it sounds like you are referring to a JuiceBox from Enel X, a completely unrelated company to our own (although the product names are similar).

Please see this informational page about JuiceBox in North America: https://www.juiceboxnorthamerica.com/
You should be able to contact Enel X/VoltiE Group directly via their contact page here: https://powerup.voltie.us/contact

I hope this points you in the right direction and that they are able to help you with your query.

Perhaps the two most influential factors in the loading of a gallery are the speed of the web server (where the gallery files are hosted) and the user's internet connection. Unfortunately, there is little you can do about either of those.

You could maybe tweak the size of your images. From memory, if you allow JuiceboBuilder-Pro to resize your images at default settings (medium sized images at 1024 x 768), the resulting images tend to be around 120KB each. This is significantly smaller than your current average of 300KB and images should, therefore, load faster (and they should still hopefully be of a reasonable quality for web gallery use).
You could also take advantage of Juicebox-Pro's Multi-Size Image Support (see here for details) where the gallery stores different sizes of images and serves up smaller ones on mobile devices. It might make a difference (depending on factors such as the device's screen size and pixel density).

I don't think the imageScale mode will make a big difference to the loading speed but the imagePreloading value (Large Screen Mode only) might. (Both of these configuration options can be found in the Main Image Options section here). When setting the preloading to the default value of PAGE, Juicebox will preload all images on the current thumbnail page so reducing the number of thumbnails per page should speed up the initial load a bit. Alternatively, you could set the preloading to NEXT, whereby only the next image in the gallery is preloaded. This should provide the fastest possible loading time (less initial burden on the browser) but I can't say whether it will make a difference on your Android device. It's something you can experiment with, though.

3

(1 replies, posted in Juicebox-Pro Support)

Unfortunately, the Juicebox module for Drupal is an unofficial plugin which was not written by ourselves and we have little knowledge of it.

For support with the module, please post in the Juicebox Issues section of the Drupal forum (here) where the current maintainers of the module should be able to help you out.

I hope that this points you in the right direction.

Unfortunately, the Juicebox module for Drupal is an unofficial plugin which was not written by ourselves and we have little knowledge of it.

I notice that the latest release is an alpha version (4.00-alpha2) so perhaps the current maintainers released a version with basic functionality and plan to add to it later (although this is just speculation on my part).

Maybe you could post in the Juicebox Issues section of the Drupal forum (here) where the maintainers might be able to give you more information.

I know this does not directly answer your question or resolve the issue but I hope that it at least points you in the right direction.

Perhaps some other Drupal users can post here with more information, too.

I don't think Filezilla has a setting to specifically ignore contents of a folder (at least I can't find one) and using Filezilla with default settings should work fine. There should be no need to delve into the settings to change things before upload Juicebox gallery files.

I guess if you wanted to troubleshoot your Filezilla methodology, you could check the transfer window (at the bottom) to make sure that the contents of the 'jbcore' folder are in the 'Queued files' tab, i.e. have been scheduled to be transferred to your web server (each individual file should be listed), and then switch to the 'Failed transfers' tab (after uploading) to see if (and why) any files have not been uploaded succesfully.

If the files are not even listed in the 'Quesed files' tab, then the contents of the 'jbcore' folder could be hidden in your Mac's file system and they simply have not been added to the queue (and Filezilla knows nothing about them).

In any case, I'm glad you have a workaround (and there are certainly other FTP programs out there, although I use Filezilla myself).

Perhaps the latest FileZilla upgrade does not recognise the the inside components of the JBCore folder?

Filezilla 3.69.1 works fine (uploads all files inside the 'jbcore' folder) on my Windows 11 PC. Tested on a fresh gallery created with JuiceboxBuilder-Pro v1.5.1.2 and Filezilla 3.69.1 with all default settings. Even after changing the attributes of the 'jbcore' folder to hidden (including all subfolders and files), dragging and dropping the gallery folder into Filezilla uploaded everything, including the 'jbcore' folder and all its contents.

I'm glad you've got all your galleries working but I'm still no closer to being able to explain what caused the problem.
If there was a setting in a program somewhere that was set to not upload files in subfolders, then the 'images' and 'thumbs' folders should have been empty as well as the 'jbcore' folder and this does not seem to be the case (as far as I can tell).
Maybe the permissions on the 'jbcore' folder specifically rendered it hidden and the FTP program did not see it when uploading the gallery? That's my best guess at the moment.
In any case, I'm glad everything is working as it should. Thanks for the update.

I have found another error which may be stopping SFTP from loading the theme.css properly.

I doubt that any errors in a file would prevent a file from being uploaded (via FTP or SFTP). Filezilla (for example) does not check files for style or syntax errors. it just uploads what it's given.
Likewise, I doubt a web server would check files for problems. If a file had any errors in it, the first anyone would likely know about it is if the file is opened in a browser (and then the browser could potentially choke on the error).

There is a HTML coding error in the Juicebox jbcore/theme.css.

It's not really an error. It's just three lines of CSS code which contain browser-specific prefixes (so that the 'transform' can be performed in all browsers).
Any line of CSS code that is not recognised by a browser might be flagged with a warning (by the browser) but the browser ought to just ignore the line of code that it does not understand and then carry on parsing the file.
These days, all major browsers should recognise 'transform' and so the code now could be replaced by:

.jb-idx-thb-list .jb-idx-thumb img:active {
    transform: translate(2px, 2px);
}

... or, for backwards compatibility with older browsers:

.jb-idx-thb-list .jb-idx-thumb img:active {
    -webkit-transform: translate(2px, 2px);
    -moz-transform: translate(2px, 2px);
    -o-transform: translate(2px, 2px);
    transform: translate(2px, 2px);
}

I'm not sure that your solution is best as it's not actually valid CSS.
Try entering the original code into the W3C CSS Validation Service and you'll see that the code is valid.
However, try validating your code and you'll see errors reported.

I'm really not sure why your gallery is not loading with the untouched CSS file. As I mentioned above, I think it's more likely to be your browser that your FTP/SFTP program or web server. What browser and version are you using?

However, if for whatever reason your browser does not like the original (valid) CSS code, try:

.jb-idx-thb-list .jb-idx-thumb img:active {
    transform: translate(2px, 2px);
}

... instead. It should work just fine (in a modern browser).

Strange... I've just used Filezilla 3.69.1 to upload a test Juicebox gallery folder to two different servers and all the files (including the ones inside the 'jbcore' folder') were copied successfully.
Maybe there's a setting in your Filezilla preferences that is preventing files in subdirectories from being transferred. It's worth checking 'Edit -> Settings' (Windows) or 'FileZilla -> Settings' (Mac) to see if there is anything there that might be causing your problem.

There is a minor problem with the JB Java Script component but it may not matter?

This is just informational rather than an actual warning or error. It's nothing to worry about.
An extra semi-colon in JavaScript (denoting the end of a line of code) will just be ignored by all browsers.
I guess the packing program (which minimizes the source code into the 'juicebox.js' file that you see) just errs on the side of caution and leaves the semi-colon there.

I hope you get on OK.
You could try re-uploading your gallery before contacting your web host (in case something happened during the original upload resulting in missing files). This might be enough to resolve your problem.
However, if this does not help, then maybe your web host could shed some light on things.
Just for the record, it looks like the entire jbcore folder is missing. Maybe it has been uploaded to a different location and the path to the juicebox.js file in your gallery's embedding code needs to be adjusted? Just a thought.

Check out this gallery as an example: https://www.shelbourne-america.net/SunB … index.html

The gallery's 'juicebox.js' file should be located here: https://www.shelbourne-america.net/SunB … uicebox.js
... but going to that location directly in a browser results in an error 404 (file not found).

It looks like your gallery's 'juicebox.js' file is simply not present on your web server. (This would account for the error message you've been getting, too.)

Try re-uploading your gallery and make sure that its 'jbcore' folder is complete.

This should hopefully resolve your problem.

It's not possible to change the installation directory or the working folder (the hidden .tempGallery folder) but you can save and load galleries to and from any location you like (it does not need to be the Desktop).

The installation directory should not really be a problem (iCloud will not, be default, be backing up installed applications) and the fact that gallery folders can be moved (manually by the user) to a location not being synced means that iCloud can be worked around here, too.

The problem seems to be the location of the working folder which JuiceboxBuilder puts in the Documents folder which is a folder commonly synced by iCloud (and other similar services). Competing applications both trying to work on the same folder at the same time is most likely the issue.

Unfortunately, JuiceboxBuilder hard-codes the location of the working folder within its code and it is not user-changeable.
Ensuring that the Documents folder is not being synced (or, more specifically, the JuiceboxBuilder-Lite or JuiceboxBuilder-Pro subfolder within the Documents folder) is the best solution we have at present.

I'm glad you found the root of your problem and have been able to fix it.
Thank you for letting me know. It's most appreciated.

If I use just the configuration options shown in your post, the thumbnails in my test gallery are positioned at the bottom as expected.

Please check your gallery's 'config.xml' file to see if there are any other configuration options being set which might account for the gallery layout you are seeing.

Also, check to see if there is any custom CSS on your gallery's embedding page which is perhaps overriding the gallery's own CSS and interfering with its layout.

If you continue to experience difficulties, please post the link to your gallery so that I can examine your gallery and its embedding page. (If you don't want to post it publicly here in the forum, you can email it to me at steven@juicebox.net.)
Once I'm able to see the gallery live on your web server, I should hopefully be able to determine the cause of the problem and propose a solution.
(Just for the record, there are no known bugs with thumbsPosition but without knowing exactly what is causing your problem, I can't rule it out.)

Thanks!

@Ann

Thanks for sharing your recent experience.

Backing up important files is definitely recommended (and can often turn out to be essential) but automated systems such as iCloud can be backing up stuff without people being aware of what is going on (and this can cause slow-downs or, in the case of JuiceboxBuilder, problems).

Similar problems can happen with OneDrive on Windows PCs.

I help a lot of friends with their PCs and the majority have no idea what OneDrive is, let alone what it is doing. OneDrive quite often backs up files that my friends have no interest in having duplicates of. My friends often contact me when they get a message saying that their OneDrive storage is full and wonder what is going on! This might not be representative of Juicebox-Pro users but it's a problem I encounter frequently.

Maybe it's for the best that locations like default 'Documents' folders are being backed up automatically (backing up a lot of unwanted files at the same time). At least the important files are being backup up.

Having said that, it's important to know what locations are being backed up so that problems (such as the JuiceboxBuilder one) can be worked around.

Ideally, JuiceboxBuilder should maybe choose a different location for its temporary work folder (knowing that iCloud and OneDrive backup the system's 'Documents' folder by default) but that would require a recompiling of the application and unfortunately, I don't see an update forthcoming.

In the meantime, the best course of action (as you have discovered), is to ensure that iCloud (or OneDrive or any other online backup service) is not backing up any locations used by JuiceboxBuilder (i.e. the 'Documents' folder and the folders you choose to save galleries to).

In any case, I'm glad you're able to use JuiceboxBuilder without all the problems and frustration that iCloud was causing!

@nono

If your problem is that you're live preview obscures other content within JuiceboxBuilder and you truly are using the latest version of AIR (v51), then the version of AIR is the problem.
You'll need to use the most recent version of AIR which has support for WebKit (the embedded browser that JuiceboxBuilder uses for the live preview). This is currently AIR v33.1.1.744. It can be downloaded from the foot of the AIR download page: https://airsdk.harman.com/runtime

Please uninstall AIR v51 first before installing AIR v33.1.1.744.
Please see this forum post for further details: https://juicebox.net/forum/viewtopic.php?id=5319

I hope this helps to resolve your problem.

17

(1 replies, posted in Juicebox-Pro Support)

As far as I recall, I don't think true fullscreen is possible in Mobile Safari on an iPhone.

This web page states that the Fullscreen API is only partially supported in Safari on iOS ("Partial support refers to supporting only iPad, not iPhone.").

I'm not sure if this will help at all but here's a short section entitled Expand Gallery Behavior from our own web site.

Maybe you could try in an alternate browser on your iPhone (e.g. Chrome or Firefox) to see if you get different results.

I know this will not directly resolve your problem but I hope it at least adds a little information to the subject.

The "trailing slash on void elements" messages are listed on the W3C Markup Validation site as "Info" (rather than "Warning" or "Error"). As such, the messages are just informational and should not cause any problems.
Trailing slashes on void elements are optional in HTML 5 and can, indeed, interact badly with unquoted attribute values but Juicebox does not use any unquoted attribute values (all attribute values in the code generated by Juicebox-Pro are quoted) so the trailing slashes are fine (although unnecessary) in this scenario.
I cannot be 100% sure how Google's SEO crawling and indexing works but as the trailing slashes are valid HTML 5, there should not be any problems with SEO or anything else.

19

(1 replies, posted in Juicebox-Pro Support)

Hi.
Please check your email. I have sent you a new download link.
Thanks!

[Conversation continued via email. No Problem with gallery. I'll post back here if a solution to the problem is found.]

It's interesting to hear that you are having trouble opening one particular gallery.

Two things spring to mind...

(1) There could be a corrupt image in the gallery that JuiceboxBuilder-Pro is choking on.
Even something as seeming innocuous as badly formatted metadata (which might not be enough to cause a visible problem when opening the image in a regular imaging program), could potentially cause JuiceboxBuilder-Pro to fail when adding the image to a gallery.
If you try to recreate your gallery from scratch and add your images in small batches, you should be able to find out if there is a rogue image.

(2) It could be a memory allocation problem.
If you try to add too many images to JuiceboxBuilder-Pro at once (maybe when opening a very large gallery), then Adobe AIR may not be able to allocate enough memory for the task at hand (causing JuiceboxBuilder-Pro to crash or hang). Even if your computer has plenty of free RAM, I seem to remember that Adobe AIR applications are limited to around 1GB of memory allocation.
The workaround for this is to add your images to your gallery in smaller batches. Trial and error will help to determine a safe number of images per batch (it will depend on your own images).
Having said that, I've seen this happen when adding images to a gallery but not when opening an existing gallery. Also, this usually only happens when trying to add hundreds of images at a time (and not just 70). I thought I should mention it, though.

To help with troubleshooting, you might like to send me your 70-image gallery to see if I can open it on my own computer.
I have a Windows 11 PC (admittedly nothing like your own setup) but I'll try to open the gallery using AIR v33.1.1.744 and JuiceboxBuilder-Pro v1.5.1.2 and let you know if it works for me (or if I find anything amiss). If you'd like me to try this, just zip your gallery, upload the zip file somewhere and send a link to me at steven@juicebox.net. Thank you.

@jerryfields

I'm sorry to hear that you are having trouble with JuiceboxBuilder-Pro on your Mac.
I wish I could be of more help but it sounds like you might already have tried everything that I'm aware of.

Over the years, I've been able to collate all the problems and solutions that users have run into and I've documented them here in the forum.

You've no doubt seen and tried most of (if not all) the suggestions but, for the sake of completeness, here are the two threads/posts I think might be most relevant to your problem.
Unresponsive New Gallery and Open Gallery buttons in JuiceboxBuilder - https://juicebox.net/forum/viewtopic.php?id=5295
Troubleshooting JuiceboxBuilder installation and usage problems - https://juicebox.net/forum/viewtopic.php?id=5114

... installed Adobe Air update...

It's also worth noting that you'll need to be using AIR v33.1.1.744 (and not the latest version, AIR v51. See here for details: https://juicebox.net/forum/viewtopic.php?id=5318

Also, if you have a Mac which uses Apple Silicon (M1, M2, M3, M4 hardware), you may need to open JuiceboxBuilder-Pro using Rosetta.
This is noted as a Known Issue for Mac users on the AIR download page: https://airsdk.harman.com/runtime

Launch failure on M1 hardware. Some AIR applications will fail to launch when run on a device using Apple Silicon (M1 / ARM hardware). To work around this, please right-click on the application icon within Finder, choose "Get Info", and on the resulting dialog, select the checkbox "Open using Rosetta".

It's also mentioned here in our forum (with instructions and further links): https://juicebox.net/forum/viewtopic.php?id=5289
Here is the Apple support page regarding Rosetta 2: https://support.apple.com/en-us/102527

I don't think the AIR or Rosetta issues will be relevant to your problem (I don't think you'd have made it as far as JuiceboxBuilder-Pro's 'Start' panel otherwise) but I thought I should mention it.

Once again, I'm sorry I don't have a definitive answer for you but maybe other Mac users reading this can chip in and help out.
If I think of anything else that might help, I'll be sure to post back to let you know.

I'm glad that worked for you. Thank you for letting me know.

I'm sorry to hear that you are having trouble with JuiceboxBuilder-Pro on your Mac.
I hope my notes below help to resolve your problem.

If you have a Mac which uses Apple Silicon (M1, M2, M3, M4 hardware), you may need to open JuiceboxBuilder-Pro using Rosetta.
This is noted as a Known Issue for Mac users on the AIR download page: https://airsdk.harman.com/runtime

Launch failure on M1 hardware. Some AIR applications will fail to launch when run on a device using Apple Silicon (M1 / ARM hardware). To work around this, please right-click on the application icon within Finder, choose "Get Info", and on the resulting dialog, select the checkbox "Open using Rosetta".

It's also mentioned here in our forum (with instructions and further links): https://juicebox.net/forum/viewtopic.php?id=5289
Here is the Apple support page regarding Rosetta 2: https://support.apple.com/en-us/102527

I hope that these notes help you to get JuiceboxBuilder-Pro up and running.
Please let me know how you get on. Thank you.

At least for the moment, SUCCESS!

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