Search options (Page 7 of 39)

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.

I'm glad you've got it working. Thanks for letting me know!

I'm glad to hear that you've been able to resolve your problem.
Thank you for letting me know. It's most appreciated.
I hope everything runs smoothly from now on!

Hi! Welcome to the forum!
I hope you find everything you are looking for here in the forum and in the online support section.
If you run into any problems using Juicebox, just post here in the forum and I'll do my best to help you out.
I wish you well with Showkase!

OK, I'm glad everything is well! Thank you for letting me know.

I'll mark this thread as [SOLVED] but I'll not lock the thread so please post back if you have any further problems.

Yes. You can hide pages (of any page type under any theme) by dragging the pages onto "Hidden pages" (just above "Trash") on the 'Pages' tab (and then clicking 'Save' and 'Publish').
When a page is hidden, there will be no link to the page within the site's navigation menu but the page will still exist within the site so you can use the page's URL as you wish (e.g. send it to someone, use it as a link in another web page, etc.).

You're welcome!

Unfortunately, the Showkase Server Compatibility Test cannot check for every PHP function used by Showkase. (It checks for the most likely causes of problems.)

It sounds like your web host might have disabled the parse_ini_file PHP function: https://www.php.net/manual/en/function. … i-file.php

Showkase requires this PHP function to be enabled and there is no way to run Showkase without it (and no alternate version of Showkase which does not use it).

Please contact your web host and ask if the parse_ini_file PHP function has been disabled on your hosting account and, if so, ask them if they could enable it for you.

I hope this points you in the right direction.
Please let me know how you get on and if I can be of any further assistance.

Please try installing and running the Showkase Server Compatibility Test.
Even if you ran the test before originally installing Showkase, please try again in case your web host has made any changes recently which might be contributing to your problem.
The results of the tests may point us in the right direction and let us know the exact nature of the problem.
There are troubleshoting tips on the test's web page (link above)

If everything was working well previously, then please contact your web host and ask if they have made any changes to your hosting account recently which might somehow be contributing to your problem.

Also, if you are not already using the latest version of Showkase (v1.7.4), please try upgrading to see if this helps to resolve your problem.
If necessary, full instructions for downloading the latest version and upgrading an existing site can be found on the Upgrading Showkase support page.

I hope this helps (at least as a starting point to figuring out what is causing your problem).
Please let me know how you get on.
Thank you.

Thank you for the update and additional information.

This certainly suggests that the problem has been a browser cache issue. (As you are aware, clearing your browser's cache does not change anything on the web server and, if clearing your browser cache has resulted in you being able to see what you expect to see, then the files must have always been present and correct on the web server.)

Weird, indeed...

Here are a couple of things you could try to prevent browsers from caching your Showkase web pages.

Suggestion #1:
If you want to prevent browsers from caching Juicebox gallery XML files, then try defining the gallery XML files with a unique identifier (e.g. the current time which will be different each time the browser loads the page) via the configUrl option in each gallery's embedding code.

Open your 'showkase/_themes/base/pagetypes/juicebox.tpl' file in a plain text editor and change line 26 from:

... to:

Now republish your site for this change to propagate throughout all your Showkase Juicebox galleries.

Suggestion #2:
You may also be able to dissuade browsers from caching HTML pages by using certain <meta> tags.

Open your 'showkase/_themes/base/pagetypes/basetheme.tpl' file in a plain text editor and add the following code in the {block "meta"} ... {/block} section, between lines 9 and 23 (but not inside {if $ss_ogImageUrl ne ''} ...  {/if}).

<meta http-equiv="cache-control" content="no-cache" />
<meta http-equiv="expires" content="0" />
<meta http-equiv="pragma" content="no-cache" />

Again, republish your site for this code to appear in all your Showkase pages.

If you ever need to contact me via email my email address is below my username here in the forum (visible only when you are logged in).

I hope my notes above help.