Search options (Page 4 of 38)

Thank you for the update!
I'm glad you have been able to find the cause of your problem.
Thank you for posting back to let me know. It's most appreciated.

You're welcome!

I'm really glad that you've been able to resolve your problem.
Thank you for letting me know. It's most appreciated!

All the best!

I'm sorry to hear that you are having trouble with Showkase.
Unfortunately, an error 500 is a rather generic internal server error and it's not really specific enough to pinpoint the cause of the problem.
However, from the information you provide, the problem could actually be the permissions that you set (777).

777 permissions should work OK but because they are the most relaxed permissions that you can use, some web servers are configured to actually not respect the 777 permissions and, instead, treat them as a potential security risk which, is this is teh case, could certainly prevent Showkase from functioning.

Under normal circumstances on most web servers, there should actually be no need to set permissions of 777.
Showkase should work perfectly fine with default permissions of 755 for folders and 644 for files.

Try changing permissions to 755/644 (or just reupload Showkase using default permissions if it's easier) and see if this helps.

I hope this helps to resolve your problem.
Please let me know how you get on and if I can be of any further assistance.

If you continue to experience difficulties, then please let me know what type of web server you are installing Showkase on (e.g. Linux vs Windows, Apache vs IIS) and what version of PHP your web server has installed and I'll try to help further.

Also, it might help to check out your web server logs to see if anything more specific than an error 500 has been logged that might point us in the right direction.

Thank you.

Just to clarify, are you talking about the tree on the admin interface's 'Pages' tab (and not the navigation menu in the live site)?
As long as that's correct, then here's a suggestion.

Open up your site's 'showkase/admin/classes/pagesscreen.php' file in a plain text editor.

Change line 109 from:

$("#container").jstree({

... to:

$("#container").on("ready.jstree", function(event, data) {
    data.instance.close_all();
    data.instance.open_node("ref0");
}).jstree({

Now re-upload the 'pagesscreen.php' file to its original location on your web server (overwriting the existing file).

This will allow Showkase to build the 'Pages' tree and, once the tree is ready, the custom code will collapse all nodes and then open just the root node ('Public pages') so that you can see only your top-level pages.

I tried changing the state of each node (from open to closed) as Showkase creates the individual nodes but this has the unwanted effect that when you open an initially closed node, the tree registers this as a change. This results in an unnecessary reminder to 'Save' the change when you move to a different admin tab (without actually having made any functional changes to the tree, e.g. moving or renaming a node).
I think my suggestion above is perhaps the best option.

Notes:
(1) The line number above refers to the current version of Showakse (v1.7.6).
(2) Any changes to the Showkase source code should be done at your own risk. I do not foresee any problems with the code above but it would always be wise to make a complete backup of your site before modifying any source code, just in case anything unexpected happens and you need to reinstate your original files at a later date.

Just enter the 'Web Property ID' in the Showkase interface (above the 'Tracking Code' input) and Showkase will handle the Google Analytics code for you (without the need to modify any source code manually).

I noted the basetheme.tpl file only because you mentioned other properties and if you want to add an additional Google Analytics property to the code (such as MEASUREMENT_ID_2 in the sample code provided here), then you would need to do this manually.

If you just want to use the 'Web Property ID', then Showkase can take care of this for you.

It's probably just a browser caching issue.
Try refreshing the settings page (Ctrl + F5).
Otherwise, try completely clearing your browser's cache before reloading the settings page.
It should look like this screenshot: [Link removed.]

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.