51

(7 replies, posted in Showkase Support)

No problem!

52

(7 replies, posted in Showkase Support)

The current version of Showkase (v1.7.6) is fully compatible with PHP 8.0 and 8.1

There is, however, a compatibility problem with PHP 8.2 (due to a deprecated feature) but I have notified the developers of this and it should be fixed in due course.
Until such time, just use PHP 8.0 or 8.1 (or, indeed, any version of PHP between 5.2 and 8.1 inclusive) and you'll be fine.

53

(7 replies, posted in Showkase Support)

Thanks for posting in the Feature Requests thread.
As always, I really don't know what might be picked up for future versions but this is still the best place to post ideas to ensure that they are seen by the developers.

54

(1 replies, posted in Showkase Support)

Unfortunately, I have no easy way of checking when a password was last changed but what we could do is this...

I could change your password (to a temporary password) and email you the password.
You would then log in with this temporary password and then change the password on your 'Profile' page via the 'Change your password' link (at the right hand side of the page below the second blue menu bar). This method does not require a confirmation email to be sent. (You'd have the temporary password as the existing password so you shouldn't encounter any unknown password errors.)

If you'd like to do this, then please email me to let me know (you can find my email address in the column to the left of this forum post).

55

(7 replies, posted in Showkase Support)

The logic that Juicebox uses to decide which image size to use is hardcoded into the 'juicebox.js' JavaScript file which is obfuscated and cannot be modified so you'll not be able to do anything there.

The best course of action would likely be to increase the resolution of your medium images and perhaps reduce the quality percentage a little ('Site -> Customize Viewers -> Juicebox-Pro (Edit) -> Pro Viewer Options -> Multi-size Images (Pro)') in order to keep the file size at a reasonable level.
If you don't want your images to be downloaded, then a slight decrease in quality might be acceptable. The likelihood is that a slight quality percentage reduction will result in a smaller file size but the visual quality may be hard to notice(at least to a casual viewer). A little bit of trial and error might be required to find a balance but I hope that you can find a suitable compromise between resolution and file size.

56

(7 replies, posted in Showkase Support)

I've just uploaded a fresh Showakse v1.7.6 site and checked the multi-image size functionality. It seems to be working OK for myself.

Here's what I did:
(1) Site -> Customize Viewers -> Juicebox-Pro (Edit)
(2) Selected 'Large images', 'Medium image resize' and 'Small images' checkboxes.
(3) Created a new Juicebox-Pro gallery page (on 'Pages' panel).
(4) Clicked 'Upload' tab.
(5) Uploaded a single image (dimensions 4416 x 3312) via upload module (via HTML 5 method).
(6) Published site (clicked 'Publish').
(All image sizes and all other checkbox were left at their default values.)

Now, when I check inside the Juicebox-Pro gallery's folder (in the root Showkase directory), there's a folder named 'images'.
Directly inside this folder is the medium image (dimensions 1024 x 768).
Also, inside the folder is a subfolder named 'large' which contains the large image (dimensions 1280 x 960).
Finally, inside the folder is a subfolder named 'small' which contains the small image (dimensions 800 x 600.).

It is worth noting that Juicebox-Pro uses the medium images for a gallery being displayed on a desktop monitor (no matter what the size of the monitor is). Large images are reserved for when an image is opened in a new tab (via the Open Image button) or downloaded (via the Download Button). Small images are used on mobile devices, though (unless a retina/high pixel density screen is detected, in which case, medium images will be used).

Give it another go and hopefully it'll work OK for you as it does for me.

57

(7 replies, posted in Showkase Support)

There are no real problems associated with having larger images in your galleries (other than the larger file sizes which result in the need for more server storage space and longer download times).

Assuming your galleries are Juicebox-Pro galleries:

(1) Images will always be dynamically scaled down to be displayed in their entirety, no matter what the size or shape of the user's viewport is (as long as imageScaleMode is set to SCALE_DOWN (the default value) or SCALE).

(2) Images are preloaded (according to the imagePreloading configuration option value) so while one image is being viewed, the next few images are being preloaded in the background so any delay associated with larger images will be minimal and may only be apparent on the first image. (The default value for imagePreloading is PAGE (whereby all images on the current thumbnail page are preloaded) but you can change it to NEXT (the next image only) or NONE, if you like.)

(3) You could have a Multi-Size Image gallery whereby your gallery can have up to 3 different image sizes and Juicebox-Pro will display the size most appropriate to the user's device and screen size.
GO to 'Site -> Customize Viewers -> Juicebox-Pro (Edit)', then scroll down to 'Pro Viewer Options' and expand the 'Multi-size Images (Pro)' section for the options.


Short descriptions of the configuration options in bold above can be found in the Main Image Options section of the Juicebox-Pro Config Options page.

I hope this helps.

58

(4 replies, posted in Showkase Support)

You can always post suggestions in the Feature Request thread.
I don't know what suggestions might be implemented in future versions but it's the best place for ideas to be seen by the developers.
Thanks!

59

(4 replies, posted in Showkase Support)

Sorry, there are no new themes in the pipeline.
If you're adventurous and proficient in HTML, CSS and JavaScript, you could perhaps create your own theme.
Check out the Creating Themes support section for details.

With regard to videos...

If you have a video uploaded to Vimeo or YouTube (or a similar service), then you can grab the video's embed code from the site and insert it into a Showkase page (e.g. a 'Basic' page).
You can insert whatever HTML code you like (e.g. a video's embed code) into the text editor on a Showkase page.
Just make sure that your text editor (on the Showkase page) is in 'Source' mode (click the 'Source' button in the text editor's toolbar).

Otherwise, if you want to host a video on your own web server and embed it into a Showkase page, then try the following:
(1) Upload the video file to your web server. In this example, we'll call it 'movie.mp4' and upload it to the root directory.
(2) Enter something like the following code into the Showkase page's text editor (in 'Source' mode), changing the width as necessary:

<video src="/movie.mp4" width="800" controls>Your browser does not support the video tag.</video>

The leading slash in the 'src' attribute denotes your root directory. If you upload your video file to a location other that your root directory, make sure that the path to the video file is correct. (If it is a relative path, then it should be relative to the Showkase page's location, i.e. one directory down from the Showkase directory.)

More information about the <video> tag and its attributes can be found here: https://developer.mozilla.org/en/docs/W … ment/video

Showkase's own video fitting routine ensures that the video fits within the theme's 'Max site width (px)' and the user's browser window.

Hi. Thanks for checking in with us.

Related FAQs:
How many websites can I use Showkase on?
Does a single domain license cover multiple subdomains?

A Single Site License allows you to install an unlimited number of Showkase sites on a single website domain and all associated subdomains.
For example, if your domain name is example.com, then all the following examples would be covered by a Single Site License (as they are all on example.com):

  • example.com/showkase_site_1

  • example.com/folder/showkase_site_2

  • subdomain1.example.com/showkase_site_3

  • subdomain2.example.com/folder/showkase_site_4

If you want to have a Showkase site on a difference domain (for example, example2.com), then you'd need to purchase a separate Single Site License.

Notes:

(1) Alias domains which simply mirror content are not counted for license purposes. For example, if you have a Showkase site at example.com/showkase and exactly the same content is mirrored at example2.com/showkase, then a Single Site License covers this scenario.

(2) Licenses are only required for publicly accessible domains, so staging and testing domains do not require an additional license.

I hope this helps to clarify things.

61

(5 replies, posted in Showkase Support)

Thank you for the update.

I can't say definitively that the script is not the cause of the issue but Showkase uses an unmodified version of PHPMailer. (The Showkase source code just passes parameters to the PHPMailer script which does all the hard work.)

PHPMailer has been around since 2001 and is still actively developed (with the latest version, v6.6.4 released 12 days ago). I can't guarantee that it's completely bug-free but Showkase v1.7.6 currently uses PHPMailer v6.3.0 and we've not had any reports (other than your own) of the contact form failing recently.

You were good enough to try the latest version of PHPMailer (v6.6.4) but without success. If this had worked, then it would point towards a bug in v6.3.0 (the version that Showkase currently uses) but this is not the case.

Also, the contact form worked in your previous Showkase site so we know the script is capable of sending mail. The script did not change when you moved your site but, for the script to fail, then logically something else must have changed (on your web server) to have caused the problem.

I'm sorry that you've not been able to get the contact form working but I'm glad that you've at least found a suitable workaround.
Thank you for letting me know.

62

(5 replies, posted in Showkase Support)

#1 That should be absolutely fine.

#2 Thanks for trying. I'm sorry it did not work.

#3 Do the times on the warnings correspond to times that the 'Send' button is clicked? (I know you won't know if visitors to your site try to use the contact form but you could try it yourself a couple of times and note the times down.)

From reading the PHP warnings, it looks to me like your PHP installation is looking for the Ctype extension but cannot find it. It's possible that your site previously used the Ctype extension without any problems but the extension may not have been carried forward after a PHP upgrade. (This is pure speculation on my part but possible, I guess.)

I don't know if this is the reason that your contact form no longer works (did your web host upgrade your PHP recently?) but it would be good to resolve these warnings. I'd contact your web host about them. They should be able to help. I expect they'll likely have seen warnings like this before so they'll probably know the cause and how to fix it.

According to a quick web search "The Ctype extension provides a set of functions that are used to verify whether the characters in a string are of the correct type.". If your PHP installation is triggering this extension after the 'Send' button is clicked but the extension cannot be found (thus returning a fail), then it's certainly plausible that this could be at the root of your problem.
I'd certainly look into getting it fixed (at least to eliminate it from the equation) before moving on to other potential causes.

I know you said that PHP Mail is enabled on your web server but it might be worth checking in with your web host to see if there are any restrictions on this service.

Here are two other things to try:

#1 You could try using SMTP to send the mail rather than PHP Mail. PHPMailer already has the code in place for this but you'll need to modify the Showkase source file which sets the values being sent to PHPMailer to include all the SMTP credentials. Instructions are in this forum post.

#2 If there is a restriction in place whereby mail is not being sent on your web server due to the email address you use not matching the domain of your website, then you could try forcing PHPMailer to not set the Sender address.

(1) Open the 'showkase/admin/plugins/contact/master/contactcore/contact.php' file in a plain text editor.

(2) Change line 88 from:

$mailer->setFrom('mailer'.strstr($siteEmail, '@'), $userName);

... to:

$mailer->setFrom('mailer'.strstr($siteEmail, '@'), $userName, false);

I don't know if this will make a difference but it is certainly a quick and easy thing to try.
Please note that the line number above refers to the current version of Showkase (v1.7.6).

63

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

64

(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!

65

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

66

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

67

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

68

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

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.

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.

71

(93 replies, posted in Showkase Support)

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

72

(13 replies, posted in Showkase Support)

You're welcome!

73

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

74

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

75

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