Search options (Page 5 of 39)

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!

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.

#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).

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

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.

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.

You're welcome!

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.

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.

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.

You're welcome!

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.

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.

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.

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.

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.

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.