Search options (Page 11 of 39)

Thank you for running Showkase in debug mode and for trying the Showkase Server Compatibility Test.
They are usually the two most helpful things when trying to troubleshooting a problem.

The following is just a hunch but it may help.

Please check the PHP memory_limit value on your web server.
You should be able to check your PHP settings using phpinfo() as follows:

• Create a new file in a plain text editor with the following code: <?php phpinfo(); ?>

• Save the file with a .php file extension (for example, 'phpinfo.php').

• Upload the file to your web server and open it in a browser.

If memory_limit is set to -1 (to assign no memory limit) rather than an actual value, then this is likely to be the cause of your problem.

Showkase is not currently set up to handle such a memory_limit value and this prevents thumbnails from being generated. (I have seen this only once before it could be the cause of your problem.)

The developers are aware of this issue and it will be fixed in the next version of Showkase.
In the meantime, a workaround is to hard-code a suitable $memoryLimit value into Showkase's source code.
Open the 'admin/classes/thumbnail.php' file in a plain text editor and change line 27 from:

: ini_get('memory_limit');

to:

: '1024M';

After making this change, please republish your Showkase site (just click the 'Publish' button).
Please note that the line number above refers to the current version of Showkase (v1.7.3).

Hopefully this will solve your problem.
Please let me know how you get on and if I can be of any further assistance.

Try adding the following CSS to your site's '_themes/kosel/css/custom.css' file (changing the actual font-size value as necessary).

.type-galleryindex .thumbs figcaption a {
    font-size: 24px;
}

This should change the font-size for the Gallery Index Page thumbnail text.

If you have a lot of text to display and find that it is being truncated (and not all displayed), then you might like to try using the following CSS instead (which will leave more room between rows of thumbnails for text to wrap).

.type-galleryindex .thumbs figcaption {
    font-size: 24px;
}

There is no need to re-publish your site after making this change but you might need to clear your browser's cache before reloading your Gallery Index Page in order to see this change.

Thank you for providing the links.

I have downloaded your image and notice that the white area surrounding the picture is actually part of the image file itself (and is not originating from Showkase).
Open the image in an imaging program (such as Adobe Photoshop), crop the image to remove the white area surrounding the picture and then reupload the image file to Showkase.

This should solve your problem.

Unfortunately, Juicebox-Pro's direct download functionality does not work on iOS devices so Juicebox-Pro automatically hides the Download Button when an iOS device has been detected. (The Direct Download button should display and function fine on Android devices, though.)
As you have discovered, the best alternative for iOS users would be to include the Open Image button so that they can open the image in a new windows and download the image from there (using Mobile Safari's native 'Save Image' functionality).

With all default settings (for both Showkase and Juicebox-Pro), Showkase will dynamically resize a Juicebox gallery on a Juicebox gallery page so that the bottom of the gallery rests at the bottom of the browser window, no matter what the size or shape of the browser window is. Therefore, the gallery is always visible in its entirety and vertical scrolling is required only to see the page footer (below the gallery).

The default value for 'External fit px' (resulting in the behavior I described above) is '0' (zero).
If you have a large site header (taller that the default site header text), then this can push the gallery down the page slightly (resulting in vertical scrolling being required to see the bottom of the gallery).
'External fit px' was designed to compensate for a tall site header and using a small negative value will reduce the gallery's height a little to, once again, allow the entire gallery to be seen without vertical scrolling.
A value of '-25' seems very reasonable as your site header is not that much taller than default site header text.
Having changed the 'External fit px'  value to '-25', things look much better on a 15" screen now.

If you want your main images to be displayed even larger than they at are present, then you could actually increase the height of your gallery by using a positive value for 'External fit px'. This would mean that users would have to scroll vertically to see the whole of your gallery but this might be something you are willing to live with to have your images displayed as large as possible (in the gallery's unexpanded form).

You could also reduce the number of thumbnail rows on your gallery page (by limiting the number of thumbnail rows to just 1 by setting maxThumbRows="1").
Space is reserved for the thumbnails (the thumbnail are not dynamically resized) and the main images are displayed in the remaining space. If you have fewer rows of thumbnails on your gallery page, then this will leave more space for the main images to be displayed.

With regard to the 'Press Esc to exit full screen' message, when you set useFullscreenExpand="TRUE" (to expand the gallery fullscreen rather than just full browser), you are making use of the browser's implementation of the Fullscreen API and the text for the message actually comes from the browser (not Juicebox or Showkase) and cannot be changed.
However, using the Esc key to close the expanded gallery should have the have functionality as closing the gallery via the Button Bar's Expand/Close Button (and it does in Chrome, Edge, Firefox, Internet Explorer and Opera on my Windows 10 PC).
If this does not seem to work for yourself, then try completely clearing your browser's cache before reloading your web page and trying again. Your browser may have cached some older Juicebox or Showkase files which might be causing a problem after upgrading.

If this does not help, then please let me know exactly what you mean when you say that the 'menu bar' does not reappear.
Are you referring to the Showkase navigation menu (at the top of the page) or the Juicebox Button Bar?
Perhaps you could upload a couple of screenshots to let me see what you are seeing. It might help me to troubleshoot your problem further. Thank you.
Otherwise, if you are really concerned about the 'Press Esc to exit full screen' message and its functionality, then you could avoid the problem altogether by setting useFullscreenExpand="FALSE" (although the gallery will expand only to fill the browser window rather than the entire screen).

I hope these notes help.

You're welcome!

I'm glad you've been able to use the available options to configure your gallery appropriately.
Thank you for letting me know.

You're welcome. I'm glad you've got your original problem sorted out. Thank you for letting me know.

Notes on the width of the caption area:

When captionPosition (in the Juicebox gallery page's 'Caption (Pro)' section) is set to either OVERLAY or BOTTOM, then the width of the caption area will span the entire width of the gallery and will, therefore, remain constant no matter what the image dimensions are.

When captionPosition is set to either OVERLAY_IMAGE or BELOW_IMAGE (it sounds like you might be using one of these values), then the width of the caption area will span the width of the image.

When captionPosition is set to BELOW_THUMBS, then the width of the caption area will span the width of the thumbnail area.

Notes on the height of the caption area:

When captionPosition is set to OVERLAY or OVERLAY_IMAGE, the height of the caption area is variable (it will increase, if necessary, to accommodate long captions) up to a maximum value set via maxCaptionHeight (default value, 120px).

When captionPosition is set to BOTTOM, BELOW_IMAGE or BELOW_THUMBS, the height of the caption area is fixed at the maxCaptionHeight value (instead of being variable).

For reference, a list of all Juicebox-Pro Caption Options can be found here.

Possible solutions:

With the above information in mind, possible solutions to your problem would be to either:
(1) Set captionPosition to either OVERLAY or BOTTOM (to ensure that the caption area's width spans the entire gallery).
... or:
(2) Set captionPosition to either OVERLAY_IMAGE or BELOW_IMAGE and increase maxCaptionHeight (to give your captions more room with less likelihood that they will be truncated).

I hope you can use some combination of these options and values to configure your gallery as you'd like it to be.

You can change the 'Gallery background color' in the Juicebox gallery page's 'Lite Viewer Options' section.

If you would like to use an image for the gallery's background, you can enter the 'Background Url' to an image on your web server in the Juicebox gallery page's 'Background Image (Pro)' section. The 'Background Url' can be an absolute URL or a relative URL (relative to the gallery's embedding page).

Alternatively, you could make your gallery's background transparent (by setting the gallery background color's 'Opacity' to 0 (zero) and then set a background color or image for the entire site (rather then just the gallery) in the 'Site -> Customize Theme' tab.

If you want to set a custom color for the site's background, change the 'Color Scheme -> Overall color scheme' to 'custom' and then set the 'Background color' in the 'Custom Palette' section.

If you want to use an image for the site's background, first upload the image to the library ('Library -> Upload') and then select the image via 'Site -> Customize Theme -> Background -> Background URL'.

I hope this helps.

It looks like you've found a small bug.
After installing Juicebox-Pro to Showkase-Standard, the label on the 'Site -> Customize Viewers' tab should change from just "Juicebox" to "Juicebox-Pro 1.5.1".
Thank you for reporting this issue.

I've contacted the developers who will hopefully fix this for the next release.

In the meantime, I think I've found the root of the problem (Showkase being unable to read the Juicebox version number from the 'juicebox.js' file under PHP 7.1.0 and above) and you might like to implement the following fix manually. I've tested it myself (under PHP 5.6.36 and 7.2.7) and it seems to work fine.

Open your site's 'showkase/admin/classes/themeset.php' file in a plain text editor and change line 229 from:

$docBlock = file_get_contents($sourcePath, false, NULL, -1, 50);

... to:

$docBlock = file_get_contents($sourcePath, false, NULL, 0, 50);

(The problem seems to have happened with a change in PHP 7.1.0 so if you are running a version of PHP prior to 7.1.0, you will not see the problem.)

Please note that the line number above refers to the current version of Showkase (v1.7.3).

I hope this helps to fix the problem until the developers are able to incorporate it into the next release.

Incidentally, when installing Juicebox-Pro into Showkase-Standard, you need only copy the Pro 'jbcore' folder to the 'admin/plugins/juicebox/master/' location (overwriting the existing Juicebox-Lite 'jbcore' folder). On next publishing your site, Showkase will automatically copy the 'jbcore' folder from the 'master' location to the 'viewers' location.

I'm glad to hear that you have been able to resolve your problem.
Thank you for letting me know (and for sharing your solution).

Unfortunately, there are no configuration options to change the position of the menu icon. (It will always be on the right hand side of the page.)
You'd really need to delve into the Showkase source CSS to change its position.
I have a feeling that this may not be as easy as it looks. (I've already tried a couple of things using my browser's developer tools to no avail. One problem just leads to another...)

Having said that, if you are familiar with CSS, you could certainly give it a try.
Check out the Adding Custom Styles and the Creating Themes support sections for further information about customizing a site beyond the available configuration options. Knowledge of CSS (and possibly HTML and JavaScript, too) would be necessary and it would be much safer to just stick to what can be done within the Showkase interface.

Also, you could post 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 certainly is the best place for all ideas.
Thank you.

Sorry. I should have mentioned that you would need to republish your site after modifying the 'layout.tpl' file.
(There would have been no need to republish if just adding JavaScript code to the 'custom.js' file.)
I'm glad that you were able to figure this out and that it works for you. Thank you for letting me know.

You'll probably want the code to be present on all pages throughout your site (so that the cookie warning appears if a visitor initially visits a page other than your home page).

The location of the code depends on the code itself (whether it is JavaScript or HTML).

If the code is purely JavaScript, then you can add it to your theme's 'custom.js' JavaScript file (which is loaded into every page throughout your site and will not be overwritten each time the site is published).
For example, if you use the Boma theme, then add the JavaScript code to your site's '_themes/boma/js/custom.js' file.

If the code is HTML, then you can add it to your site's 'layout.tpl' file (which is the base template used for all pages).
Open the '_themes/base/pagetypes/layout.tpl' file in a plain text editor and add the HTML code wherever you want it to be on your web pages (perhaps just before the closing </body> tag at the foot of the page).

Please note that if or when you next upgrade Showkase (for example when a new version is released), both the 'custom.js' and 'layout.tpl' files will be overwritten (with the stock versions included in the installation package) so please make a copy of any custom modifications you make so that you can integrate them into an upgraded (or new) Showkase site.

I hope this helps.
If you experience difficulties with anything, please let me know the code you are looking to use and I'll try to help further.