1

(2 replies, posted in Showkase Support)

Thank you for bringing this to my attention.

Unfortunately, the latest (and last) open-source version of CKEditor 4 (CKEditor 4.22.1, the version used within my unofficial update patch for Showkase v1.7.6) is no longer receiving updates and the long-term support versions of CKEditor 4 (which should be more secure) require a license for commercial use (which we don't currently have).
It looks like CKEditor 5 would also requires a commercial license for use within Showkase (being free only for open-source projects).

If you are willing to accept the security risks, then you can at least suppress the warning by adding:

config.versionCheck = false;

... to Showkase's showkase\admin\settings\ckeditorconfig.js file.

I don't know exactly what the security risks are (I have not yet been able to find details on CKEditor's website) or, indeed, which versions of CKEditor they affect.
It might actually be beneficial to revert to CKEditor 4.16 (from the Showkase v1.7.6 zip package). If you'd like to do this, just overwrite the showkase\admin\ckeditor folder on your web server with the showkase\admin\ckeditor folder from the Showkase v1.7.6 zip package. I genuinely don't know if this will help (with the security itself or the warning message) but it might be something you'd like to try.
As always, when making changes manually to files on your web server, I'd recommend making a full backup of your site first, just as a precaution.

It looks like we might need to stick with CKEditor 4.16 (from the official Showkase v1.7.6 zip package) or CKEditor 4.22.1 (from my patch) for the time being until the developers can formulate a more long-term solution.

Maybe there's a fork of the open-source CKEditor 4.22.1 somewhere on GitHub that might be a suitable replacement? I'll take a look.
I'll post back here if I have any further news on the subject.

2

(3 replies, posted in Showkase Support)

@Kim

Please apply the patch I created in this post: https://showkase.net/forum/viewtopic.php?pid=2368#p2368

Further details on how to apply the patch can be found here: https://showkase.net/forum/viewtopic.php?pid=2376#p2376

This should resolve your issue and ensure that your Showkase installation is fully compatible with PHP 8.2.

3

(1 replies, posted in Showkase Support)

I'm sorry to hear that you're having problems.

You'll need to contact your web host (the company that provides you with the web space that you uploaded your Showkase site to). They should be able to tell you what has happened to your site.
We do not provide any web hosting at all and have no way of knowing where you uploaded your Showkase site to (or, indeed, what has happened to it).

Two things that sometimes help with ERR_NAME_NOT_RESOLVED are clearing your browser's cache and flushing your DNS but as yourself and a few friends all experience the same thing, it sounds like these suggestions would not help in your case.

The first thing to do is to contact your web host and, if you have a custom domain name, check in with your domain registrar, too, in case your domain name has expired.

I hope this points you in the right direction.

4

(8 replies, posted in Showkase Support)

You're welcome! Thanks for the update.

Not sure why I was having the problem with Chrome...

Sounds like a caching problem. (It works in Chrome for me.)
Have you tried completely clearing your Chrome browser's cache before accessing your Showkase admin again?
It should work in Chrome just as well as it does in Firefox (and any other modern browser).

5

(8 replies, posted in Showkase Support)

That's odd.
I've just double-checked (with a fresh Showkase v1.7.6 installation and the patch files from my box.com link) and I uploaded a .webp image to the Showkase Library as a test without any issues. (The image uploaded via the upload module without any problems or error messages and, afterwards, it appeared on the Images tab as expected.)
It looks like the files are fine.

The three most likely things I can think of that might be causing your problem (and, therefore, things you could investigate) are:
(1) The patch files have been uploaded to the wrong location on your server.
(2) When uploading the patch files to your web server, your FTP program has not been set to overwrite existing files.
(3) Your web hosting account has server-side caching enabled and your web server is still using older, cached files rather than the new patch files you've recently uploaded. It might take some time for the new files to become active on your web server.

Check that you're uploading the patch files to the correct location on your web server. If, for example, you installed Showkase to your root directory, then you would have uploaded the contents of the 'showkase' folder (from the Showkase zip file) to your root directory. If this was the case, then you would upload the contents of the 'showkase' folder (from the patch zip file) to your root directory.

Also, make sure that your FTP program is set to overwrite existing files (so that the patch files replace their original versions).
If you integrated the patch into a Showkase folder on your computer before uploading, make sure that your copy action replaced (and did not skip) existing files.

Finally, make sure that your web hosting account does not have server-side caching enabled. (Check in with your web host. They should be able to help you with this.)

I'll keep my fingers crossed that one of these suggestions helps you out.
Please let me know how you get on. Thanks.

6

(8 replies, posted in Showkase Support)

The patch zip file is not a complete Showkase installation. It contains only:
(1) certain files from the full Showkase v1.7.6 zip file which have been updated (to fix issues) and...
(2) some new files (to update third-party libraries).
As such, the patch zip file cannot be used to install and run Showkase on its own.

When you extract the full Showkase v1.7.6 zip file, you'll find a folder named 'showkase' which contains all the Showkase files.
When you extract the patch zip file, you'll also find a folder named 'showkase' which contains only the updated and new files.

If you are starting from scratch, you could extract the full Showkase v1.7.6 zip file to your computer and then extract the patch zip file on top of it, to the same location (overwriting pre-existing files) before uploading the resulting 'showkase' folder to your web server.
Alternatively, if you already have a Showkase v1.7.6 installation on your web server and you want to apply the patch to it, you could upload the extracted patch files to your Showkase directory (again, overwriting pre-existing files).
Just be sure to extract the patch files to the correct directory and make a full backup of your existing site first (just in case).

I hope this helps.

7

(3 replies, posted in Showkase Support)

That's great! Thank you for letting me know.

With the patch in place, there are no known issues with any version of PHP but if you run into any new problems, please let me know. Thanks!

8

(3 replies, posted in Showkase Support)

There are a couple of bugs when running Showkase v1.7.6 under PHP 8.1 and PHP 8.2 (one unique to PHP 8.1 and another unique to PHP 8.2).

If using PHP 8.1 or PHP 8.2, please apply the patch I provided in this forum post. This should provide full compatibility with PHP 8.1 and PHP 8.2 (and I've tested it with PHP 8.3, too).

9

(8 replies, posted in Showkase Support)

You've not missed an update. The latest (current) version is still v1.7.6.

Unfortunately, I do not know if or when Showkase may next be updated and it does look increasingly likely that an official update is not forthcoming. Sorry I cannot be more specific just now but I don't make the decisions around here and I don't have any news at the moment.

Having said that, even though I'm not the author of Showkase and cannot release new official versions, I am still a member of the official support team and I'll continue to do my best to see that Showkase stays alive and kicking.

This might be a good opportunity to post a round-up patch containing all of the fixes and updates that I've posted in the forum over the past few months.

Please note that this is an unofficial patch and that you should use it at your own risk. I have tested it myself on a web server running PHP 8.3.6 but it has not undergone extensive testing by anyone other than myself.
Please be sure to make a full backup of your existing site before applying the patch.
The patch files are in a folder named 'showkase' (like the official Showkase zip file) so you can just upload the 'showkase' folder to your web server, overwriting your existing files.

Here is the changelog for the patch:

  • Changed default body text on About and Basic pages for consistency across all page types

  • Fixed PHP 8.1 incompatibility - implicit incompatible float to int conversion is deprecated

  • Fixed PHP 8.2 incompatibility - dynamic properties are deprecated

  • Introduced webp support

  • Updated links in showkase.robots.txt file

  • Upgraded CKEditor to v4.22.1

  • Upgraded jsTree to v3.3.16

  • Upgraded PHPMailer to v6.9.1 for Contact page

  • Upgraded Plupload to v2.3.9

  • Upgraded Smarty PHP Template Engine to v4.5.2

NB:
(1) This patch should be applied to Showkase v1.7.6 (Pro or Standard) only. It should not be used for any other version.
(2) This patch now requires that a minimum version of PHP 7.1 should be used. (The previous minimum version required was PHP 5.2.)

Patch file download link: https://app.box.com/s/lel919xayj6hnhrf8ju0apsfeowoocal

As always, just give me a shout if you need a hand with anything. I'll be here to help!

10

(1 replies, posted in Showkase Support)

Sure! If you can describe your problem here, I'll do my best to help you out.
Otherwise, you can email me direct at steven@juicebox.net.

(I've split your post from the thread you posted in. It's always best to have each user's problem in its own unique thread.)

11

(2 replies, posted in Showkase Support)

Please see this forum thread.

I posted a patch (in this forum post) which addresses issues relating to PHP 8.1 and PHP 8.2 (including the one you experienced).
The patch will allow run Showkase v1.7.6 to run on PHP 8.1, PHP 8.2 (and I've also tested it on PHP 8.3).

Apologies for the inconvenience. I hope the patch helps.

12

(4 replies, posted in Showkase Support)

Unfortunately, this is no way to change the background color of an individual page from within the admin.
You'd need to do this with some custom CSS in the custom.css file.
You can, however, target individual pages (or page types) using this method.
Check out your page's <body> tag in your web browser's Developer Tools -> Page Source for classes that might help in targeting your page.
You might find something like this:

<body class="light type-basic page-12 group-0  body-arial headings-arial ">

You could target this page using the 'page-12' class (each page has a unique page number), e.g:

.page-12 {
    background-color: #000000;
}

... or you could target all basic pages as follows:

.type-basic {
    background-color: #000000;
}

I hope this points you in the right direction.
However, if you continue to experience difficulties, please post the URL of the web page and let me know what color you'd like it's background to be and I'll see if I can help further.
Thank you..

13

(4 replies, posted in Showkase Support)

I notice that you are using a custom.css file (_themes/kosel/css/custom.css) which sets background-color: #E9E3D3; for #wrapper.
This will override the color set in the Showkase admin so you might need to remove this custom CSS for admin-set colors to work.

14

(4 replies, posted in Showkase Support)

If you use a 'custom' Color Scheme, then the background color of a Basic page (all pages, in fact) should be controlled by the 'Background color' in the Custom Palette.
I've just checked this for a Basic page in a test Showkase v1.7.6 site (using the Kosel theme) and it works as expected for me.

If the background color of your Basic page does not seem to follow the 'Background color' in the Custom Palette, then try clearing your browser's cache before reloading your web page to see if this makes a difference. Otherwise, try loading your web page in a different browser (one which you have not used to view your site before) to make sure that browser caching is not the cause of your problem.

It might also be worth checking in with your web host to make sure that there is no server-side caching active on your hosting account.

Hopefully this will help.
Please let me know how you get on. Thank you.

15

(93 replies, posted in Showkase Support)

For anyone looking for WEBP support, please check out this forum thread.

16

(1 replies, posted in Showkase Support)

FIXED IT NEVER MIND

OK. I'm glad you've managed to sort things out. Thank you for letting me know.
Just let me know if you run into any further problems and I'll do my best to help you out.

17

(6 replies, posted in Showkase Support)

@Anglican

It's possible but I really don't know. I'm not the author of Showkase and I don't make such decisions.

However, the patch really just duplicates the way Showkase handles GIF images, but for WEBP images. All the complicated stuff (the actual image processing) is done by native PHP functionality so the extra code required in Showkase to get it working is minimal and I don't see there being any adverse effects.

I hope it will be picked up by the Showkase developers but, if not, at least the patch is here for those that want to use it.

18

(3 replies, posted in Showkase Support)

You're welcome!
I'm glad you've got it working. Thank you for letting me know.

19

(3 replies, posted in Showkase Support)

Sorry for the inconvenience.

This problem is caused by a deprecation in PHP 8.1: Implicit incompatible float to int conversion is deprecated.

Until Showkase is updated to address this issue, I've attached the fix to this post as a zip file. Just extract the zip file (it'll extract to a folder named 'showkase') and upload the whole 'showkase' folder to your own site, overwriting the existing source files.

The fix also addresses an issue relating to PHP 8.2: Dynamic Properties are deprecated.

You should not have any problems applying the patch but I'd recommend taking a complete backup of your site first, just in case anything goes wrong and you need to reinstate your original files at a later date.

I hope this helps.
Please let me know if I can be of any further assistance.
Thank you.

20

(6 replies, posted in Showkase Support)

Nothing will change to the original functionality of Showkase or to pre-existing galleries and their .jpeg, .png and .gif images.. The patch just allows .webp as a new file type and all .webp images will be processed in the same way that .gif images are currently processed.
If you have a Juicebox gallery with Large, Medium and Small checkboxes already selected, then just leave them all selected. (If you deselect the Large and Small checkboxes, then you'll lose the largeImageURL and smallImageURL entries from the gallery's 'config.xml' file on the next publish.)

I mentioned selecting the 'Medium image resize' checkbox as, if you don't, then .webp images will not be resized for the Medium size images in your Juicebox galleries (similar to the behavior for .gif images).

As long as the Large, Medium and Small checkboxes are all selected, then you should have large, medium and small .webp images in your Juicebox galleries (for a .webp image source).

Please bear in mind that the patch is unofficial and you might like to try it out in a test Showakse site (in a separate directory of its own so that it does not interfere with your live site) before integrating it into your live site.

21

(6 replies, posted in Showkase Support)

Thank you for posting your suggestion in the Feature Requests thread.
I don't know if or when this might be implemented officially but, in the meantime,you might like to try this patch that I created (attached).
It introduces .webp support to Showkase and allows .webp images to be uploaded via the upload module.
Just extract the zip file over your existing Showkase directory. The following files will be replaced:

  • admin/classes/gallery.php

  • admin/classes/imagesizer.php

  • admin/classes/thumbnail.php

  • scripts/plupload/queue.js

Notes:

(1) This patch is not official. It was made by myself, not by the author of Showkase. As such, it has not gone through a rigorous testing regime (although I've tried it out myself and it seems to work fine) and you should use it at your own risk. Be sure to make a full backup of your site first, just in case you need to reinstate your original files at a later date.

(2) The upload module (the third-party Plupload module) only resizes .jpeg and .png images client-side so .webp images are treated the same as .gif images (i.e. they are not resized when uploading). Either be sure to resize your .webp images before using them in Showkase or, if using a Juicebox-Pro gallery, go to 'Site -> Customize Viewers -> Juicebox-Pro (Edit) -> Pro Viewer Options -> Multi-Size Images (Pro)' and select the 'Medium image resize' checkbox.

(3) The files named above have been modified so, if you have made any other modifications to these files (from the stock Showkase v1.7.6 versions), then your modifications will be lost and you'll need to apply them to the files again.

(4) Please use this patch only if you are using Showkase v1.7.6. The original files that I modified were Showkase v1.7.6 stock files. Using this patch on a previous version of Showkase may break other functionality.

I hope this helps.

22

(6 replies, posted in Showkase Support)

No, sorry.
The Showkase upload module accepts only GIF, JPG/JPEG and PNG.

23

(3 replies, posted in Showkase Support)

You're welcome!

... I'm assuming the public_html folder of a website is the webroot.

Yes (although not all web servers are the same and the root directory on others may be labelled something else such as 'htdocs').

Is it really that simple?

Yes. The 'robots.txt' file has been a web standard for a long time now and all major web search engines ought to respect it. I cannot guarantee that they all do, but I'm sure there would be a huge outcry if they did not.
It's a lot easier to tell search engines to not crawl and index a web site that it is to ensure that a site is crawled and indexed.

No other settings? Lines 25 to 35 are activated by doing so?

That's right... no other settings. The actual lines of code in the file are not commented out. The file just needs to be renamed to become active.
Just replace lines 25 to 35 with the following to disallow everything (if you like):

User-agent: *
Disallow: /

Incidentally, I notice that the links in the file's comments (for more information) are no longer active.
Check out these links instead:
(1) http://www.robotstxt.org/robotstxt.html
(2) https://developer.mozilla.org/en-US/doc … Robots.txt
(3) https://en.wikipedia.org/wiki/Robots.txt

24

(3 replies, posted in Showkase Support)

When you extract the Showkase zip file, you'll find a file named showkase.robots.txt.
You can open this file in a text editor to read more about it (in the comments at the top of the file).
Here are the full contents of the file.

# robots.txt
#
# A robots.txt file prevents the crawling and indexing of certain parts
# of your site by web crawlers and spiders run by sites like Yahoo!
# and Google. By telling these "robots" where not to go on your site,
# you save bandwidth and server resources.
# This file will be ignored unless it is called robots.txt and is in the root of your host.
# You can either rename this file to robots.txt or copy the content to your existing robots.txt
#
# If you have installed Showkase in the root of your host then:
# 1. Copy this file to the web root OR
# 2. If you have an existing robots.txt file add this content to it.
#
# If you have installed Showkase in a subdirectory then:
# 1. Copy this file to the web root OR
# 2. If you have an existing robots.txt file add this content to it.
# 3. Edit the paths so they point to the files you want to disallow
#
# For more information about the robots.txt standard, see:
# http://www.robotstxt.org/wc/robots.html
#
# For syntax checking, see:
# http://www.sxw.org.uk/computing/robots/check.html

User-agent: *
Crawl-delay: 10
Disallow: /_data/
Disallow: /_library/
Disallow: /_showkase/
Disallow: /_smarty/
Disallow: /_themes/
Disallow: /_trash/
Disallow: /_viewers/
Disallow: /admin/
Disallow: /readme.html

By default, the file (once renamed and placed in the correct location) will disallow crawling throughout the Showkase admin area of your web server.
If you want to disallow everything (public pages as well as the Showkase admin), then use the following (instead of the stock code):

User-agent: *
Disallow: /

I hope this helps.

25

(16 replies, posted in Showkase Support)

@Koinelendot

It's a shame that a new version of Showkase has not yet been released with an implementation of the fix above but my code (from this post) is a complete solution to the problem with no known adverse side affects for those experiencing (or not experiencing) the problem.