Search options (Page 5 of 38)

Support for Google Analytics 4 was introduced in Showkase v1.7.5.

If you go to 'Site -> Site Settings' and expand the 'Google Analytics' section (at the foot of the page), you'll see a drop-down menu for the 'Tracking code'.
Version numbers are not mentioned but if you select 'Global Site Tag (gtag.js)' (and enter your 'Web property ID' above it), the code which is entered into your Showkase pages exactly matches the code shown on Google's own 'Google Analytics 4' support page here.

(Showkase still supports the older version of Google Analytics, too. Just select 'Legacy (ga.js)' from the drop-down menu for the 'Tracking code'.)

I hope this helps to answer your query.

If everything was working fine but now is not and you have not changed anything yourself, then it sounds like something may have changed on your web server which is causing the problem.
Please check in with your web host to see if they have made any changes to your hosting account recently (e.g. change of PHP version, migration to a different web server, etc.) which might somehow be contributing to the problem. This might give us a clue to the nature of the problem and point us in the right direction.

If you have not already done so, then try running the Showkase setup (in case your web host has moved your site to a different web server).

If running the Showkase setup does not help, then perhaps upgrading Showkase will help.
If you are not already running the latest version of Showkase (v1.7.6), then please try upgrading to see if this helps.
Showkase is kept up-to-date to be compatible with the latest versions of PHP and, but if you are currently using an older version of Showkase and your web host has upgraded the version of PHP on your hosting account, then this might be the cause of the problem and upgrading Showkase may help.

You can find full instructions for downloading the latest version of Showkase and upgrading on the Upgrading Showkase support page.

Even if you are already using the latest version of Showkase (v1.7.6), try going through the upgrade process but with the v1.7.6 files. If there are any missing or corrupt source files within your Showkase site, going through the upgrade process will reinstate them with fresh versions. (Make sure that your FTP program is set to overwrite existing files.)

When upgrading your Showkase site, please be sure to make a complete backup of your existing site first, just in case anything should go wrong and you need to reinstate your original files at a later date. You should not encounter any problems upgrading Showkase but it would be wise to have a backup of your site should anything unexpected happen. Also, if you have made manual customizations to any Showkase source files (or to your theme's custom.css or custom.js files), then please note that they may be overwritten when you upgrade and you'll need a backup in order to reinstate them afterwards.

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

I'm sorry to hear that you are having trouble with your Showkase site.
I hope my notes below help.

Checking out the web page you provided a link to, I notice that none of the external CSS and JavaScript resource files are being loaded.
If you try to view one of them directly in a browser (e.g. http://bobsgallery.digido.com/_themes/k … styles.css), you'll see the following error message:

This error message suggests that the permissions on the CSS and JavaScript files are too restrictive.
Please check the permissions of your site's CSS and JavaScript files. (Default permissions of 644 should be fine.)
It looks like all your CSS and JavaScript files are affected so it appears that something might have happened on your web server to have caused this problem.
Ask your web host if they have made any changes to your hosting account recently which might be contributing to the problem.
If they have made a change, then perhaps they can reverse it.

Here are some other suggestions...

First of all, please make a complete backup of your site, just in case anything goes wrong and you need to reinstate your original files at a later date. (Even though the site is not currently functioning, a backup might come in useful if you need to rebuild your site.)

Assuming you can log in and navigate around the interface without any CSS, go yo 'System -> Files' and click 'make writeable' against every entry. This should change the permissions throughout your site and might hopefully resolve your problem.

If you need to rebuild your site, there are a couple of things that you can do to reduce the workload.

(1) You can retain the Showkase settings from your original site by manually copying the following files and folders from your original site to your new site (overwriting the default versions which will be in place after a fresh install).

• _data/sitedata (folder)

• _data/themedata (folder)

• _data/pagesprefs.txt (file)

• _data/theme.txt (file)

Do not copy the _data/pagesdata.txt file though, as this lists the pages present in each site (which will be different after a fresh install).

If you use a custom logo via an image stored in the library, for example, then you might also like to copy the _library folder from your original site to your new site.

If you have modified any Showakse source files or used the custom.css or custom.js files, then please remember that you will need to reinstate your customized files after a fresh install.

(2) You can import all the pages from your original site (via 'Site -> Import') to avoid having to recreate all your pages from scratch. You can import multiple pages at once so recreating your original site should be relatively quick and easy. (You'll need the page folders from your backup to do this.)

Just in case you need a new Showkase-Pro download link, I've emailed you a new one so you can downland the latest version (v1.7.5).

Having said al of the above, it looks like all the CSS and JavaScript files are in their correct locations on your web server but just not being loaded due to a permissions problem.
I am hopeful that your web host will be able to help you fix the problem quickly and without too much effort.

If you run into any difficulties trying to explain things to your web host, just ask them why trying to view this file: http://bobsgallery.digido.com/_themes/k … styles.css
... results in an error 403 when this has not always been the case and what might have caused this problem (as I'm quite you you didn't go changing permissions on all CSS and JavaScript files manually yourself).

I hope my notes help and point you in the right direction.

I am not the author of Showkase (and I don't make design decisions) but please feel free to post suggestions in the Feature Requests forum thread.
This keeps all the ideas together and ensures that they are not overlooked by the developers.
I do not know the likelihood of any ideas being implemented in future versions but this is certainly the best place for all ideas.
Thank you.

Also, please bear in mind that the 'Basic' page type is really just a blank slate and allows a lot of flexibility as you can put whatever you like on the page. As well as adding text and images via the editor's toolbar, you can switch the editor to source mode (click the 'Source' button) and add whatever HTML code you like.

I'm glad that you have found a way to resolve your problem but there is an easier way to remove a Juicebox gallery title (from within the Showkase interface) without the need to edit the gallery in JuiceboxBuilder-Pro and re-import the gallery into Showkase.

Edit your Juicebox gallery page in Showkase (on the 'Pages' tab).

Now, either:
(1) Scroll down to (and expand) the 'Lite Viewer Options' and delete the 'Gallery Title'.
... or:
(2) Scroll down to (and expand) the 'General (Pro)' section and set 'Gallery Title Position' to 'None'.

Now, scroll back up to the top of the page and click 'Save' and then 'Publish'.

If you still see the gallery title after doing this, then the problem is likely to just be a browser caching issue and clearing your browser's cache before reloading your gallery's web page should resolve the issue.

You're welcome! I'm glad I was able to be of some help.
I hope you get on well with your customizations.

If there are multiple different sizes associated with an image, then the dimensions shown on the 'Images' tab are those of the medium images. There may or may not be large and small size images, too, but there will always be a medium image and it is always the medium image whose dimensions are shown. For clarity, the medium image is the image directly inside the corresponding gallery's 'images' folder (i.e. not inside the 'large' or 'small' folders).

Also, when I say there is always a medium image, this is just a label. The medium image could, in theory, be the only image size being used but it could actually be a very large image (in terms of both filesize and resolution) if you want.

Under most circumstances (check the Multi-Size Image support page for details), it will be the medium image which is used for the gallery display and, if there is a corresponding large image, the the large image will be used if the image is opened in a new tab (via the 'Open Image' button), downloaded (via the 'Download' button) or if the gallery is expanded. (If there is no large image, then the medium image will be used for all occasions.)

Whatever image is displayed in the gallery, it will be dynamically scaled (at the time the gallery is displayed) according to the value of the Juiecbox-Pro imageScaleMode configuration option.
A short description of this configuration option and all its possible values can be found in the 'Main Image' section of the Config Options page here.
By default, imageScaleMode is set to SCALE_DOWN whereby images that are too large (in terms of resolution) to fit within the gallery's image area are dynamically scaled down to fit within the gallery's image area whilst respecting the image's aspect ratio and without cropping. Images that are smaller than the gallery's image area are not scaled up (as this would reduce their visual quality). Such images will be displayed at their actual size (perhaps with some space surrounding the images).
You could (if you wanted to), have small images dynamically scaled up to fill the gallery's image area (again whilst respecting the image's aspect ratio and without cropping) by setting imageScaleMode to SCALE (although I would not recommend it for most users).

The AcquaPhoto Fashion gallery (for example), is a single image size gallery (there are no large images).
All images in the gallery are 1024 x 640 (except for one which is 1024x648).
In this gallery, imageScaleMode is set to SCALE so, on a large monitor where the gallery's image area is larger than the actual image dimensions, the images are dynamically scaled up to fill more of the gallery's image area than they would if displayed at their actual size. (This accounts for the drop in quality that you see when you expand the gallery on your high resolution monitor.)

It is just a demo gallery but the following changes would be beneficial:
(1) Larger gallery images could be used so that when the gallery is viewed on a high resolution monitor, the images do not need to be scaled up to fill the gallery's image area.
(2) imageScaleMode could be set to SCALE_DOWN to prevent small images from being dynamically scaled up.
(3) Two images sizes (medium and large) could be used so that, when the gallery is expanded, the large images are used instead of the medium images.

I can't really tell you which settings to use. It's a personal decision that only you can make. Different settings are useful for different audiences.
If your target audience is likely to be viewing your galleries on mobile devices, then there's perhaps little point in providing the gallery with large images and setting imageScaleMode to SCALE might actually be useful.
Having said that, it sounds like my three points above referring to the AcquaPhoto Fashion gallery would probably be useful to you, though.

If you want to use different image sizes, then it would be best (certainly easiest) to let Showkase resize them for you.
Just make sure your source images are large enough and set your image sizes on the 'Multi-Size Image (Pro)' section.
Showkase will not upscale source images when resizing them during upload. For any given image size (small, medium or large), if an image is already within the maximum dimension bounds ('Max width' x 'Max height'), then the image will just be copied across to the gallery folder without being resized.

I hope these nuggets of information help to put some of the pieces of the puzzle together for you.

That's a step in the right direction.

How are you determining the dimensions of the images being displayed in the gallery? Are you using your browser's developer tools?

By default, Juicebox-Pro dynamically scales images to fit within the bounds of the gallery's image area and it can be hard to tell at a glance what the actual dimensions of a gallery image are.
If you want Juicebox-Pro to display an image at its actual size (without any dynamic scaling), then set imageScaleMode="NONE" (in the 'Main Image (Pro)' section of the gallery's page settings). However, unless you have a fixed size gallery whose dimensions match those of the images, the images may not fit well within the gallery without any dynamic scaling and are likely to be cropped.

In any case, if things don't look as expected when you view your gallery after making any changes, try completely clearing your browser's cache before reloading your web page to ensure that your browser is using the current files from your web server (instead of older, cached versions).
Caching can certainly be useful but it can also sometimes be a hindrance to development.
Maybe this accounts for what you are seeing.

The Photoshop script for Juicebox only contains Lite options (even if the Pro 'jbcore' folder is present within the script's files).
If you want to configure a gallery created by Photoshop with Pro options, you'll need to do so with JuiceboxBuilder-Pro (or by editing the gallery's 'config.xml' file manually) afterwards.

As long as the Pro 'jbcore' folder is present within the script's files though, your galleries will be Pro (with no branding and no image limit).

For reference, JuiceboxBuilder-Pro and the Juicebox-Pro plugin for Lightroom both have full support for all Pro options in their respective interfaces.

You're welcome!

Thank you very much for your kind words and for the update.
I appreciate you taking the time to let me know that your Showkase site is back up and running. I'm very happy to hear that your problem has been resolved.

I hope that everything goes smoothly in the future but, if you encounter any further problems, just post back here in the forum and I'll do my best to help you out.

I'll mark this thread as [SOLVED].

All the best!

Delving into the Showkase source code, it looks like the problem is that NULL is being returned when the JSON string used for the tree on the 'Pages' tab is run through the PHP json_decode function.
What I don't know at this point is why this is happening in your site (i.e. why your site's JSON string cannot be decoded). I cannot replicate this problem with my own test sites.
When I'm able to see the actual JSON string that your own site uses, I should hopefully be able to advance the investigation and figure out why it cannot be decoded. Maybe there's a syntax problem with Showkase's formatting of the JSON string or maybe what should be a JSON string is NULL before decoding is attempted or perhaps there's even a bug relating to the json_decode function in PHP 5.3.19 (unlikely, but in the absence of knowing what is causing the problem, I'll not rule anything out quite yet).

I'm sorry to hear that you are having difficulties with Showkase.

Unfortunately, this is not an error that I've encountered before (wither personally or via a user report) so, at the moment, I do not know what might be causing it.

Has anything changed on your web server (e.g. PHP version) recently which might somehow be contributing to your problem?

What version of PHP does your web server use? Do you have the option of updating it? If so, it might be worth trying. (The current stable version is PHP 7.4.12.)

Before trying anything, please make a full backup of your current site, just in case anything further goes wrong and you need to reinstate your files at a later date.

It sounds like the error is a server error (rather than specifically a Showkase error) but I'd try running Showkase in debug mode in case any more descriptive error messages are displayed in the Showkase status bar before the JSON error occurs.
Open your 'showkase/admin/settings/constants.php' file in a plain text editor and change line 12 from:

define('DEBUG', false);

... to:

define('DEBUG', true);

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

If you have recently upgraded to Showkase v1.7.5, then I'd also try going through the upgrade process again (with the same v1.7.5 files) to ensure that all Showkase core files are present and correct on your web server (in case anything went wrong during the initial upgrade process resulting in corrupt or missing files).

One more thing I'd try is to go to 'System -> Repairs -> Repair' (in Showkase's interface) to rebuilt the page records.

If none of the suggestions above work, then the best course of action would be to determine the exact nature of the problem.
If you can access your web server error logs, then there should be an entry corresponding to the JSON error which might hopefully let us know exactly what Showkase file (and what line of code within the file) is causing the error.
Please let me know what your error log records for the problem.

I hope these notes help.
Please let me know how you get on and if I can be of any further assistance.
I'd be happy to help further might it would be helpful if I had access to your web server and Showkase site so that I can reproduce the error for myself and investigate further.
If you continue to experience difficulties and are agreeable to allowing me access, then please email me (my email address is below my username to the left of this post) with your FTP and Showkase login details. (I believe that I have previously logged into your web site a while ago.)
Thank you.