76 Reply by Steven @ Showkase

(5 replies, posted in Showkase Support)

This might be a little difficult to troubleshoot, especially as there's no error message to point us in the right direction.

I don't think the fact that the Contact Form used to work from a different folder is part of the probleem. I can't think of any reason why the Contact Form should work from one folder but not another. (Thank you for letting me know, though. The more information we have about a problem, the better.)
However, the fact that it used to work (albeit in a different location) but now does not suggests that something may have changed on your web server (round about the time you moved your Showkase site) to have caused the problem.

Try asking your web host to see if they have changed anything on your hosting account recently. Perhaps they've changed the PHP version and the new version uses different settings than the previous version.

Also, if you have access to your web server's error logs, please take a look at them. There may be an entry corresponding to each non-functional click of the 'Send' button which might give us a clue as to what is going on.

I expect you may already be using the latest version of Showkase (v1.7.6.) but, if not, please try updating as the internal version of PHPMailer was updated in Showkase v1.7.6. If necessary, instructions for Upgrading Showkase can be found here.

It's a long shot (and it shouldn't really be necessary) but you could try using the very latest version of PHPMailer (v6.6.4).
I've uploaded the file you'll need here: [Link removed.]
I've not zipped the file so when you click on the link above, you'll see the file's code. Just click the Download button near the top right of the page to download the file to your computer's hard drive.

Now, the file you'll need to replace within your Showkase site is showkase/admin/plugins/contact/master/contactcore/PHPMailer.php
Make a backup of the existing 'PHPMailer.php' file first, though (just rename it before uploading the new version), in case you need to reinstate it at a later date. (Remember this new version has not been tested by the Showkase developers.)

After replacing the 'PHPMailer.php' file, you'll need to republish your site (just click the 'Publish' button) for the new file to propagate throughout your site.

I hope this helps or at least points you in the right direction.

Go to forum: Showkase Support

77 Reply by Steven @ Showkase

(5 replies, posted in Showkase Support)

Thanks Steven that worked perfectly!

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

... is this correct and okay to do?

Yes, that's absolutely fine.

You could also use the following one-liner (separating the selectors with a comma):

$('.page-6 .page-body, .page-8 .page-body').detach().prependTo('.content');

... but I actually prefer your two-line approach. It's easier to see at a glance what is going on and is easier to maintain.

It seems to have worked but I know nothing about coding...

The code basically uses the jQuery detach() function to cut the body text (the page-body CSS class) from its regular position on the web page and then uses the jQuery prependTo() function to paste the detached content to the beginning of the page's content section. Adding page-6 to the selector (for example) ensures that this happens only on the page which includes the page-6 CSS class.

Therefore, the first line of your code will have an effect only on page 6 of your site whereas the second line will have an effect only on page 8.
As the same thing is happening to both pages, you can condense the code by combining both selectors (and separating them with a comma) if you like, as I've done with the one-liner above. I'd stick with the two separate lines for readability, though.

Thanks again for all your help!

You're welcome!

Go to forum: Showkase Support

78 Reply by Steven @ Showkase

(5 replies, posted in Showkase Support)

That's a little more difficult to do as all Juicebox gallery pages use the same template.
Being that a modification of the template won't help in this scenario, the first thing to do is to revert the changes I suggested above and just use the stock juicebox.tpl file.

One possible solution would be to use JavaScript to effectively cut and paste the text to a different area of the page. (The suggestion below actually uses jQuery but that's fine as the jQuery JavaScript library is already automatically loaded into each and every Showkase page.)

Try the following:

(1) Make sure you use the stock, unmodified juicebox.tpl file.

(2) Check the id of the page that you want to change. View the source of the page in a web browser, scroll down to the opening <body> tag and it'll look something like this:

<body class="dark type-juicebox page-2 group-0  body-arial headings-bebas ">

The id (CSS class selector) you'll need to remember from this would be 'page-2'.

(3) Now,you'll need to find your theme's custom.js file.
If you use the Kosel theme (for example), then the file you'll need to modify is showkase/_themes/kosel/js/custom.js.
If you use a different theme, just replace 'kosel' in the path with the name of your theme to find the relevant file.

(4) Here's a one-liner which should be added to the file in #3 above to shift the text from below the gallery to above the gallery (but only on the specified page).

$('.page-2 .page-body').detach().prependTo('.content');

Just change 'page-2' to whatever the id of your own page happens to be.

(5) There's no need to republish your site after making this change but you might need to clear your browser's cache before reloading your site.

Go to forum: Showkase Support

79 Reply by Steven @ Showkase

(5 replies, posted in Showkase Support)

There is no interface option to move the body text from below the gallery to above the gallery in a Juicebox gallery page but it can be done by editing a Showkase source file.

Open the 'showkase/_themes/base/pagetypes/juicebox.tpl' in a plain text editor.
Cut lines 32-37 inclusive:

      <section class="page-body">
        <h2 class="page-title">{$ss_pageTitle}</h2>
        <div class="body-content {$pageBodyLayout}">
          {$ss_pageBody}
        </div>
      </section>

.. and paste them to immediately below line 16:

{block "content"}

Please note that the line numbers above refer to the current version of Showkase (v1.7.6).

Just republish your site after making this change (log into your Showkase admin and click the 'Publish' button) and the body text in all Juicebox gallery pages will appear above the gallery. (If you don't see this immediately, then try clearing your browser's cache to ensure that your browser is fetching the most recent files from your web server.)

I hope this helps.

Go to forum: Showkase Support

80 Reply by Steven @ Showkase

(13 replies, posted in Showkase Support)

Last night I uploaded the SKTest folder and tried to run it and couldn't even see it at the url it should have been at.

Sounds like a domain name problem (not fully set up/propagated yet) or a PHP problem (PHP not yet installed and active on your web space). I'm glad to hear it's working now, though.

#1. For some reason all of my galleries now have a JUICEBOX link displayed in the bottom right corner on them. I know they were not in the previous version of my website so now I'd like to find where to turn that off? I've looked but can seem to find that feature.

The Juicebox link signifies that your galleries are using Juicebox-Lite (the free version of Juicebox). From this, I assume you have Showkase-Standard (and maybe, Juicebox-Pro as a separate purchase). If you do have Juicebox-Pro, then you can quickly and easily upgrade all your Juicebox gallery pages from Lite to Pro by following the Installing Juicebox-Pro instructions here.

#2. I guess since I upgraded to a new MacBook Pro M1 running macOS 12.5 Monterey my Juicebox. Pro is broken. When I try to open it I get a message to contact the developer.  That makes it kind of inconvenient when trying to create new galleries to add to my site. Is a new upgrade or fix available? As far as I can tell I already have the most recent version.

Please see this forum thread for details (and a workaround).

Also, make sure that you are using the latest version of AIR with WebKit support. (Please see this forum thread for details.)
This is currently AIR v33.1.1.743 which can be downloaded from the foot of the AIR download page here: https://airsdk.harman.com/runtime

be sure to uninstall any pre-existing version of AIR before installing AIR v33.1.1.743.

Remember that you can create Juicebox galleries from directly within the Showkase admin without the need to create them on your computer first and then import them but there's no problem if you'd rather create them with JuiceboxBuidler. Just two different ways to create the same end product.

Go to forum: Showkase Support

81 Reply by Steven @ Showkase

(13 replies, posted in Showkase Support)

Hi.

Unfortunately, I have no experience with IONOS but a (correctly configured) Linux server running PHP 8.1 should be absolutely fine for Showkase (with no need to add backward compatibility for PHP).

However, I cannot guarantee that Showkase will run fine on any particular server (although I see no reason why it should not run perfectly well under IONOS hosting, given the information I have) so, if possible, try running the Showkase Server Compatibility Test on the web space that they provide before committing.

I'm perhaps being a little over-cautious; the IONOS hosting looks fine (there doesn't seem to be anything to look out for). I just can't be 100% certain. Bear in mind that Showkase runs fine on my 3 different free web hosts without any tweaking at all so chances are you'll be fine.

Go to forum: Showkase Support

82 Reply by Steven @ Showkase

(3 replies, posted in Showkase Support)

That's great! I'm glad you were able to use the .htaccess/.htpasswd method. Thanks for letting me know.
Sorry there's not an easier way.

Go to forum: Showkase Support

83 Reply by Steven @ Showkase

(3 replies, posted in Showkase Support)

Hello. Thank you for purchasing Showkase!

As you have discovered, all Juicebox galleries within a Showkase site share a single 'jbcore' folder which means that all Juicebox galleries share the same 'pswd.php' file (i.e. all galleries have the same password or passwords). (The array in the 'pswd.php' file simply allows a variety of passwords to be used for a single gallery.)

Unfortunately, there's really no quick and easy solution to allow each gallery to have it's own unique password.
In order for each gallery to have its own 'jbcore' folder, the Showkase source would need to be modified significantly and, in order for Juicebox to support multiple passwordsand map them to different galleries, the Juicebox source code would need to be modified (and this is not something that a user can do, please see this FAQ for details).

However, there is something that you might be able to do.
As each Showkase page has its own folder (in the root Showkase directory), you could password-protect each gallery folder at server level, using .htaccess and .htpasswd files or from within your web hosting account's online control panel.

It maybe not quite as convenient as if Juicebox/Showkase allowed individual gallery passwords but as long as your web hosting account's online control panel allows you to password-protect individual directories, it should actually be quite quick and easy to set up. (Log into your control panel and what you're looking for might be labelled something like 'File -> Directory Privacy').

I hope this is a suitable workaround for you as the alternative (modifying Showkase and/or Juicebox) would really be much more difficult that it might seem at first glance.

Go to forum: Showkase Support

84 Reply by Steven @ Showkase

(93 replies, posted in Showkase Support)

No, sorry. No news of such functionality just now.

Go to forum: Showkase Support

85 Reply by Steven @ Showkase

(13 replies, posted in Showkase Support)

You're welcome!

Go to forum: Showkase Support

86 Reply by Steven @ Showkase

(13 replies, posted in Showkase Support)

I just use Namecheap personally as a domain registrar. No problems, though. It was very easy to migrate from GoDaddy (and they were cheaper than GoDaddy's renewal prices, too).
I use the aforementioned free web hosting accounts for personal use (just odds and ends, really, no sites up at present, I only signed up with them because they were free).
I use our own servers (Leaseweb) for testing/business use (probably not ideal for a regular individual user, though).

I wouldn't really recommend a free hosting account (I know you're not suggesting this, by the way) as you may have some or all of the following:
(1) fewer features than a paid account (e.g. the ability to change PHP versions and settings)
(2) limited support
(3) limited web space
(4) more downtime than a paid account
(5) monthly traffic limit

I really just used this to demonstrate that three free web hosting accounts were able to run Showkase without any tweaking at all (so finding a suitable host for a Showkase site really ought to be fairly easy).
The best way to figure out whether or not Showkase will run on a web server is to use the Showkase Server Compatibility Test. It's not foolproof (and you'll need access to the potential web space to run the test) but it might be useful (especially if you use it on a free account before upgrading to a paid account with a new host).

I've really not used any of the web hosts I mentioned extensively (although I've had the accounts for years) so I'd be hesitant to recommend any of them.
AwardSpace is really quick to update PHP (they usually make the latest version available within a day or two of release, even on their free accounts) so they have that in their favor. However, their free accounts have hotlink protection switched on with no ability to switch it off.
x10Hosting has been OK. I had a problem after they migrated my hosting account to a new server (sound familiar?) but they sorted it out fairly swiftly.
ByetHost seems to be the most restrictive of the three web hosts I mentioned, at least with regard to free accounts (e.g. PHP settings locked down, query strings being forced into URLs) but their free accounts still run Showkase (with just one non-critical warning on publishing regarding a PHP time limit which you'd probably never have a problem with unless you had a site with hundreds of galleries).
Having said all that, all these restrictions probably wouldn't come into play with a regular paid-for-account.

Whoever you go with, I'd recommend a Linux server over a Windows server (if you're given the choice). Linux servers seem to be much less problematic.

Go to forum: Showkase Support

87 Reply by Steven @ Showkase

(13 replies, posted in Showkase Support)

... they said if I wanted to keep my email address I'd have to start paying for it...

They used that bait and switch routine with me, too.
I used to use them as my domain registrar (I signed up with them for the 'free' email which they asked me to start paying for soon after) but I've since moved on to Namecheap.

I just installed ShowKase in a new folder and unfortunately that doesn't seem to have made any difference.

Unfortunately, this is pretty much what I expected. If the Server Compatibility Test cannot create a directory, then Showkase simply won't work (and I expect any PHP application which performs any file handling at all will fail, too).
You really need GoDaddy to take a look at their server configuration and allow PHP scripts to handle files and folders (it's probably just a permissions issue hidden somewhere in the server configuration). Without this basic functionality, Showkase is dead in the water.

I still think it might be worth approaching them to ask if they'll switch you over to a Linux server. They don't need to know anything about Showkase or how it works or even anything about what the current problem is to do this. It should be easy for them to do (no knowledge of anything outside of their own services is required) and I'm fairly confident (but can't guarantee) that it would solve your problem. Their Linux servers seem to have better default configuration settings (i.e. more stable with fewer pitfalls) than their Windows servers.

... selling their version of Wordpress...

Just for the record, WordPress is free (third-party plugins and themes can be purchased if necessary) and not too difficult to set up. (The most difficult part of a WordPress installation is setting up a database but even this takes only a couple of minutes in the hosting account's Control Panel.).

I wish you well whatever path you go down.
Just let me know if there's anything I can help with.

Go to forum: Showkase Support

88 Reply by Steven @ Showkase

(13 replies, posted in Showkase Support)

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

First of all, please let me try to reassure you that installing and using Showkase should be a quick, easy and error-free process.
I have free web hosting accounts with three different web hosts that I use for occasional personal use and Showkase runs fine out-of-the-box on all three (AwardSpace, ByetHost and x10Hosting).
I won't go out of my way to recommend any of the web hosts that I use as they are free accounts with limited features and no priority support. Having said that, Showakse runs on all of them without issue.
The System Requirements noted here are really all that should be necessary.

Your problem certainly seems to stem from GoDaddy's migration of your site.

Normally, after migrating a site, you'd need to run Setup ('System -> Setup' from the Showkase admin) to let Showkase know the new location of the site.
Also, if a site fails, then I'd also recommend trying 'System -> Repairs -> Repair' (to rebuild the page records).
Finally, if the above two suggestions fail, I'd suggest installing a fresh Showkase site (in a separate directory so that it does not interfere with your existing site) to see if this works (and if it does, then you could import the pages from your existing site via 'Site -> Import' to avoid having to recreate them all from scratch).
Incidentally, it is still worth making a complete backup of your dysfunctional site just now so that you can import pages from it into a new site at some point in the future.

However, the File Test failures that you posted (from the Server Compatibility Test) suggest that nothing I've mentioned above is likely to work and that the problem is an incorrectly configured server.

The first File Test is simply trying to create a new directory on the server.
If GoDaddy's support cannot figure out why a PHP script is unable to create a new directory, then I'm really not sure what to suggest. That's pretty much as basic as a file management task can be.
The fact that you mentioned "GoDaddy no longer supports html coding" is especially worrying!

I think the clue is in the word 'Plesk' (in the File Test paths).
As far as I am aware, GoDaddy uses Plesk for its Windows servers and I've seen issues with GoDaddy/Plesk/Windows in the past.
I wonder if GoDaddy would be willing to move you over to a Linux server (being that their migration has broken your site and they can't fix it)?
I have a hunch (it's a strong hunch, not just a long-shot) that running Showkase on a GoDaddy Linux server will work fine.
Showkase should work fine on a Windows server (I've seen it myself) but there definitely seems to be something amiss with yours and I'm pretty sure that, if you stay with GoDaddy, the way forward would be to migrate (again) to a Linux server.

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

Go to forum: Showkase Support

89 Reply by Steven @ Showkase

(1 replies, posted in Showkase Support)

Showkase requires PHP 5.2.0 or later (check out the System Requirements here) and the current version of Showkase (v1.7.6) is compatible with PHP 8.

In fact, work was done for Showkase v1.7.6 to specifically ensure PHP 8 compatibility (check out the Version History here).

As long as you are using the latest version of Showkase (v1.7.6), there should be no problems.

If you are using an older version of Showkase (prior to v1.7.6), then I'd strongly recommend upgrading Showkase before your website moves to a more recent version of PHP.
If necessary, full Upgrading Showkase instructions can be found here.

Having said that, I do not know what features of PHP will be enabled when your web host switches PHP versions so I cannot be 100% sure that you will not run into any problems at all.
Showkase v1.7.6 is compatible with the latest versions of PHP but if your web host changes any PHP settings during the switch (for example, introducing an open_basedir restriction, decreasing the PHP memory_limit or disabling the GD graphics library), then Showkase might not run as expected.
With this in mind, I'd recommend that you make a full backup of your Showkase site before the PHP switch, just in case anything unexpected happens and you need to reinstate your files at a later date. (This involves just copying the entire Showkase directory. Showkase does not use a database so that makes backing up a little easier.) This is extremely unlikely (I switch between PHP versions in a Showkase test site frequently with no problems) but it would be better to be safe than sorry.
Also, if you do run into any problems, then you can use the Showkase Server Compatibility Test (download from here) to check basic server and PHP requirements.

I hope this helps.

Go to forum: Showkase Support

90 Reply by Steven @ Showkase

(4 replies, posted in Showkase Support)

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.

Go to forum: Showkase Support

91 Reply by Steven @ Showkase

(4 replies, posted in Showkase Support)

By default, Showkase uses the first image in the gallery as the representing thumbnail on the gallery index page.
You can choose any gallery image you like for the gallery index page thumbnail as follows:
(1) Edit the gallery page (on the 'Pages' tab).
(2) Go to the 'Images' tab.
(3) Select the image you want as your representing image in the 'Index' column.
(4) Click 'Save' and then 'Publish'.

Please note that if you rearrange the order of images in the gallery, then it will be the original first image (before reordering) that will be used as the representing image (unless you change it as above).

Showkase has no caching functionality built-in at all. Changes are made instantly and you should see them immediately after publishing.

If you do not see changes immediately after making them, then try clearing your browser's cache before reloading your web page (or view your web page in a different browser that has not been used to view the web page before). This should let you know whether browser caching is at the root of your problem.

If this does not help, then it would appear that there is some server-side caching going on that you might need to investigate further.

I hope these notes help.

Go to forum: Showkase Support

92 Reply by Steven @ Showkase

(3 replies, posted in Showkase Support)

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!

Go to forum: Showkase Support

93 Reply by Steven @ Showkase

(3 replies, posted in Showkase Support)

Hello.

The problem is almost certainly a caching issue of some kind.

To make sure that your browser is not caching and displaying the older gallery page, try pressing Ctrl+F5 or, better still, completely clearing your browser's cache before reloading your gallery page.
I know you say that you've already tried this but it's worth trying again as there are no known bugs in Showkase which would result in the issue you describe.

Also, after changing some configuration options, try viewing the gallery page in a different browser, one that has not been used to view the original gallery page (before the changes). This should confirm whether the caching problem is client-side (browser-related) or server-side.

There is a chance that your web host uses server-side caching and even though the files on your web server are being modified by Showkase, older versions of those file could still be served to browsers for a certain amount of time.

I have an account with a web host that uses Varnish server caching. After I upload a new version of a file to my web server, the new version is not seen (and the old version is still served) for about 20 minutes afterwards. For this reason, I have Varnish disabled.

Please check in with your web host to see if they have server-side caching enabled on your hosting account and, if so, ask if they could disable it.

Caching can certainly be useful but it can also sometimes be a hindrance to development.

I hope my notes above help to resolve your problem.
Please let me know how you get on and if I can be of any further assistance.
Thank you.

Go to forum: Showkase Support

94 Reply by Steven @ Showkase

(1 replies, posted in Showkase Support)

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.

Go to forum: Showkase Support

95 Reply by Steven @ Showkase

(3 replies, posted in Showkase Support)

You're welcome!

Go to forum: Showkase Support

96 Reply by Steven @ Showkase

(3 replies, posted in Showkase Support)

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.

Go to forum: Showkase Support

97 Reply by Steven @ Showkase

(11 replies, posted in Showkase Support)

OK, no problem!
Thanks for letting me know.

Go to forum: Showkase Support

98 Reply by Steven @ Showkase

(11 replies, posted in Showkase Support)

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.

Go to forum: Showkase Support

99 Reply by Steven @ Showkase

(11 replies, posted in Showkase Support)

Showkase supports only the Web Property ID. If you need to add any extra parameters to the Google Analytics 4 code, then you'll need to add them manually to the Showkase source code.
Open your showkase/_themes/base/pagetypes/basetheme.tpl file in a plain text editor and you'll find the Google Analytics 4 code staring at line 10.
You can hard-code whatever extra parameters you like within this code and, after republishing your site (just click the 'Publish' button), the extra parameters will appear in the Google Analytics 4 code within all your pages.

Go to forum: Showkase Support

100 Reply by Steven @ Showkase

(11 replies, posted in Showkase Support)

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.]

Go to forum: Showkase Support