351

(11 replies, posted in Showkase Support)

@alfavite

As far as I am aware, favicons should display correctly when using a VPN or proxy (at least they do when I try the free VPN built into Opera of the KProxy Extension for Firefox).

When using your VPN or proxy, check to see if favicons for other sites are displayed correctly.
Also, check your own site's favicon to see if it displays correctly without using a VPN or proxy.

If your favicon is not being displayed as expected, then try adding a <link> tag in your 'basetheme.tpl' file (as I suggested in this post above).

Failing that, I would recommend that you contact your VPN service provider to see if they can help further. (It does not sound like an issue directly related to Showkase but rather a VPN/proxy/favicon issue.)

352

(4 replies, posted in Showkase Support)

Prior to this when it was on "Auto" the picture was cropped square when the phone was held vertically.

By default, the Splash Page uses the first image in the gallery and the image is scaled to fill (rather than fit within) the Splash Page and, as such, cropping may occur.
You can select a different image to use for your gallery's Splash Page (it does not even need to be a gallery image) via the splashImageUrl configuration option. You could perhaps use an image that is representative of your gallery as a whole and is more tolerant towards cropping when it is displayed in different viewport shapes.
(You could upload an image for your Splash Page to your Showkase 'Library' and then use its URL for the splashImageUrl.)

When the phone was held horizontally, the picture changed sizes as the page was scrolled up and down.

This sounds like it might be due to Showkase dynamically resizing the Splash Page image when the viewport size changes. (As you scroll up and down (in Mobile Safari on iOS at least), the browser toolbars can appear and disappear, resulting in a different viewport height. Showkase will adjust the gallery height when the viewport height changes (just like when a desktop browser window is resized).

I'm not understanding what other setting you may be suggesting for this scenario with the Splash Page for mobile devices?

I was really just suggesting that you might set showSplashPage="AUTO". You could then configure your Splash Page using the available Splash Page options.
The Splash Page itself will still be sized the same as the gallery (when no Splash Page is used) so you'll still have the same problem as before (space above and below in certain viewport shapes) but only with a single Splash Page image. (The gallery itself will be displayed on a page of its own when expanded from the Splash Page.) Maybe with a smaller 'External fit px' value (such as '-100', for example), the spacing on desktop monitors would be acceptable and you could find a suitable image for your Splash Page which would look OK on mobile devices until the gallery is expanded.

Currently I have the "External Fit px" set to -240. Also, would decreasing the logo height be helpful at all?

I'm not sure that this would help. The height of your logo does not change the height of the gallery. A logo with a large height will just push a gallery down the page (and this can be compensated for via the 'External fit px' option).

I think that using an 'External fit px' of around '-100', setting showSplashPage="AUTO" and choosing a suitable image for your Splash Page (one that will not suffer too much when dynamically cropped to fit various different viewport shapes) might be your best course of action.
With an an 'External fit px' of '-100', the space surrounding your gallery in desktop monitors should not be excessive and it should hopefully be a low enough value for a usable Splash Page on mobile devices.

353

(4 replies, posted in Showkase Support)

It's always going to be difficult to display a gallery of landscape-style images in both landscape and portrait-style viewports without any space surrounding the gallery in either, especially when Showkase has been designed to have the gallery fill the remainder of the page below the header.
Ordinarily, on small screen devices, Juicebox would display the Splash Page and, when the gallery is expanded to fill the viewport, the images are displayed as large as possible given the space available.
However, you've set showSplashPage="NEVER" so your gallery is displayed in your embedding page (rather than on its own expanded page).
In such a scenario, a compromise might be the easiest solution. Try to find an 'External fit px' value that works for mobile devices and does not result in too much space surrounding your images on desktop monitors (although perhaps a little more than you currently have).

The ideal solution would be to have your gallery's height be determined by the viewport width and the aspect ratio of your images.
However, this is not a regular scenario and it would not be easy to implement, especially within Showkase which has its own gallery sizing routine and any manual intervention might cause problems.
If you tried to modify the Showkase source, then the modification would apply to all galleries within your site (which, I guess, would not be what you want) and it would be very difficult to do.
If you edited just a single gallery's 'index.html' page, then the modification would be overwritten each time you republish your Showkase site.

You might like to take a look at these two Juicebox forum posts which deal with having a gallery height change depending on the image size and aspect ratio. They might point you in the right direction.
https://juicebox.net/forum/viewtopic.php?pid=7014#p7014
https://juicebox.net/forum/viewtopic.php?pid=9392#p9392

However, it would really not be easy to implement such a solution into Showkase and I'd recommend trying to find a compromise via the Showkase interface if at all possible, either by using a different value for 'External fix px' (one that is 'good' for both desktop and mobile devices rather than one that is 'great' for desktop but 'poor' for mobile devices) or perhaps by allowing the Splash Page to be used for mobile devices (by setting showSplashPage="AUTO").

Please check your email. I have sent you a message. Thank you.

[Query moved from Feature Requests forum to new thread.]

@saidn

Any custom code added to the 'showkase/_themes/base/pagetypes/layout.tpl' file will appear in all pages created by Showkase (whether they are password protected of not). Showkase uses this file as a base template for all pages.

Make sure that your custom code is in the 'layout.tpl' file and re-publish your site (just click the 'Publish' button) to re-generate your pages with your custom code.

If you then check the source of any of your web pages in your browser, you should see your custom code there.

If you continue to experience difficulties, please let me know and I will contact you via email (where you can send me details of how to access your password-protected web pages so that I can investigate further). Thank you.

356

(3 replies, posted in Showkase Support)

Thank you for the additional information.
Unfortunately, an error 500 is a rather generic error message generated by the web server (rather than an error message specifically displayed by Showkase) that can cover a multitude of problems.
Also, a lot has changed between v1.3.4 and the current version (v1.6.1) so I'm not sure what might be causing your problem. (Please see the Version History for a list of changes between version.)
However, here are a few things to check and try.

(1) Please try installing and running the Showkase Server Compatibility Test to check that your server has all the features Showkase needs.
Even if you ran the test before installing Showkase, please try again in case your web host has made any changes recently.
If any of the tests fail, then it might give us a clue as to the nature of the problem. (Also, there are troubleshooting tips in the link above.)

(2) Try contacting your web host to ask if they have made any changes recently or are currently experiencing any issues which might be contributing to your problem.

(3) Try running Showkase in debug mode to see if a more informative error message is displayed in the Showkase status bar when (or before) the problem occurs.
Open your 'showkase/admin/settings/constants.php' file in a plain text editor and change line 12 from:

define('DEBUG', false);

... to:

define('DEBUG', true);

Please note that the line number above refers to the current version of Showkase (v1.6.1).

(4) Try reinstalling Showkase following the upgrade instructions here using v1.6.1. Something may have happened during your initial upgrade attempt which resulted in corrupt files on your web server. Following the upgrade process should (as long as it is successful) replace all Showkase core files (whilst retaining all your existing pages and settings) so if you currently have any corrupt files, then this should fix them.

(5) Try installing a fresh Showkase v1.6.1 site (in a new subdirectory of its own so that it is completely self-contained and does not interfere with your existing site) to see if the problem happens with this new site. This should let us know whether or not the problem is unique to your original Showkase site.

Hopefully the suggestions above will help or at least point you in the right direction.
Please let me know how you get on and if you need any further assistance.

357

(4 replies, posted in Showkase Support)

Update for others experiencing similar symptoms:

The 'Pages' layout problem was caused by old or corrupt versions of the '/showkase/admin/css/all.css' and '/showkase/admin/css/bootstrap.min.css' files.
Replacing them with the stock versions from Showkase v1.6.1 resolved the problem.

358

(3 replies, posted in Showkase Support)

I've moved your post to a new thread to keep it separate from Vasily Iakovlev's problems in this thread.

Vasily's 'Pages' layout problem was caused by old or corrupt versions of the '/showkase/admin/css/all.css' and '/showkase/admin/css/bootstrap.min.css' files.
Replacing them with the stock versions from Showkase v1.6.1 resolved the problem.

i am getting the same error as the OP trying to upgrade from v1.3.4 to v1.6.1 (unable to publish the site).

Vasily was not actually unable to publish the site. There was just a warning regarding the PHP function set_time_limit() being disabled. Clicking through this message (it was just a warning, not an error) published the site successfully.

If you are seeing the same warning "Warning: set_time_limit() has been disabled for security reasons", then this is due to the set_time_limit() function being disabled in your PHP configuration settings.

As I mentioned in Vasily's thread, this is just a warning (not an error).
Showkase (since v1.3.4), makes use of set_time_limit() and if this PHP function has been disabled on your server, then there is nothing that can be done within Showkase to enable it.
However, unless your site is very large (and Showkase needs more than the default time limit to process everything), it may never actually become a problem. Just clicking through the warning message should publish your site fine.

If you do have a large site and you are unable to publish it successfully because of set_time_limit() being disabled, then I am surprised that reverting to v1.3.4 helps. (Versions prior to v1.3.4 do not use set_time_limit() so the default time limit will be used, just like in v1.6.1 with set_time_limit() disabled.)

In any case, if you would like remove the set_time_limit() warning, you'll need to enable this function in your PHP configuration settings. If you do not have access to change your PHP settings yourself, your web host should hopefully be able to help you out.

If you are getting any different messages when you try to publish your site (whether they are notices, warnings or errors), please let me know and I'll try to help further.
Thank you.

359

(4 replies, posted in Showkase Support)

But both of this problems have arisen after i tryed to update Showkase to lastest version.

I'm not sure what version of Showkase you upgraded from but Showkase has only been making use of it set_time_limit() since v1.3.4 so, if you have upgraded from a version prior to v1.3.4, then it is possible that set_time_limit() has always been disabled on your server but that you've not known about it until now. Please note that the message is just a warning (it is not an error) and it will not cause a problem unless Showkase has to process a very large site (which might take longer than the default time limit). You would know if this was a problem as there would be errors (not just a warning regarding the set_time_limit() function) when publishing your site.
There is nothing that can be done from within Showkase to enable set_time_limit() in your PHP settings. This has to be done at server level so if you do not have access to change your PHP settings yourself, your web host should hopefully be able to help you out.

I've sent you an email where you can forward me your FTP and Showkase login details.
Once I'm able to see the 'Pages' layout problem for myself, I should hopefully be able to help further.

360

(4 replies, posted in Showkase Support)

It looks like there are two issues here:
(1) The set_time_limit() warning
(2) The layout of the admin 'Pages' page

(1) It looks like your web host has disabled set_time_limit(). This is unlikely to cause any problems (unless you have a very large site with lots of images and your web server's default time limit is too short for Showkase to process everything when you re-publish, in which case you will not be able to increase the time limit). However, this may never actually cause you any real problems. (You could, however, ask your web host to enable set_time_limit() on your hosting account and see what they say.)

(2) Your 'Pages' page layout is set by CSS code in the 'showkase/admin/css/all.css' file. Please double-check that the 'all.css' file is present in its correct location on your web server and that it is not corrupt or incomplete.
Also, try clearing your browser's cache before reloading your 'Pages' page to see if this helps.
You could also try viewing your 'Pages' page in a different browser to see if this makes a difference.

If you continue to experience difficulties, I would be happy to help further but I'd really need access to your web server and Showkase site to check things out.
If you are agreeable to this, then please let me know and I'll send you an email address where you can forward me your FTP and Showkase login details.
Once I'm able to see the problem for myself, I should hopefully be able to determine the cause and propose a solution.
Thank you.

361

(11 replies, posted in Showkase Support)

You're welcome.
I'm glad that you've been able to resolve your problem.
Thank you for taking the time to let me know and for detailing the reason for the problem.
Hopefully it will help out any other users experiencing similar symptoms.

By the way, so far I have been extremely impressed with ShowKase.  It works perfectly for me and I love all the config options.  I also like that it doesn't break whenever there's a Wordpress update like my last web gallery experiment.

That's really great to hear! We're glad you're getting on well with Showkase!

362

(11 replies, posted in Showkase Support)

Thank you for the link to your Showkase site.
Your favicon displays OK in the browser tab when I view your Showkase site in Firefox 51.0.1 on my PC (and everything looks OK: your <link> tag is in place, your 'favicon.ico' file is in place and your <link> tag's 'href' attribute is correct).
Try completely clearing your browser's cache before reloading your web site. Hopefully this will resolve your problem.

363

(11 replies, posted in Showkase Support)

It looks like the line of code is in the correct place.
Here are a few things to check.

(1) After making the change to the 'basetheme.tpl' file and re-publishing your site, check the source of one of your Showkase pages in your browser to make sure that the code is present in the page.

(2) Check that the favicon file has been uploaded to your web server and ensure that the path to the favicon file (the 'href' attribute in the <link> tag) is correct.

(3) If your favicon is not an 'ico' file (and is perhaps a 'png' or a 'gif' file instead), then make sure that its file extension is correct and change the 'type' attribute in the <link> tag as appropriate:

<link rel="icon" href="http://example.com/favicon.ico" type="image/x-icon">
<link rel="icon" href="http://example.com/favicon.png" type="image/png">
<link rel="icon" href="http://example.com/favicon.gif" type="image/gif">

(4) Try using an absolute path (like in the examples in #3 above) instead of a relative path for the 'href' attribute in the <link> tag.

Hopefully these suggestions will help.
However, if you continue to experience difficulties, please post a link to your Showkase site so that I can take a look at things for myself and hopefully help further.
Thank you.

364

(11 replies, posted in Showkase Support)

I expect you've seen this forum post.
The instructions were accurate at the time (2 years ago) but things have changed slightly since then. (There are now certain files that are shared between all themes.)

If you've already put your 'favicon.ico' file in your root directory (not necessarily the same as your Showkase root directory) and it's not being picked up by your browser, then add the following code to your 'showkase/_themes/base/pagetypes/basetheme.tpl' file in the {block "stylelinks"} ... {/block} section between lines 27 and 30 (alongside the other <link> tags.

<link rel="shortcut icon" href="/favicon.ico" type="image/x-icon">

You can change the location of your 'favicon.ico' file if you like (it does not need to be in your root directory) but just make sure that the path to the file is correct in the 'href' attribute of the <link> tag.

Be sure to publish your site afterwards (just click the 'Publish' button) to have this <link> tag inserted into all your pre-existing Showkase pages.

Please note that the file and line numbers above refer to the current version of Showkase (v1.6.1).
If you are not already using the current version, then you might like to upgrade your site following the instructions here.
For a list of changes between versions, please see the Version History.

Incidentally, once you've posted a couple of posts, you should hopefully be able to include links. (Otherwise, you can disguise the links by inserting spaces between slashes or leaving out the http:// part.)

365

(7 replies, posted in Showkase Support)

I'd be happy to investigate further but it would help if I had access to your web server and Showkase site.
If you are agreeable to this, then please let me know and I will send you an email address where you can forward me your FTP and Showkase login details.

In the meantime, how are you setting your PHP directives? It might be worth checking (with phpinfo() to see if the new values are actually being used.

Also, try running the Showkase Server Compatibility Test. Even if you ran the test before installing Showkase, please try again in case your web host has made any changes recently. The results might give us a clue as to the nature of the problem.

366

(93 replies, posted in Showkase Support)

@toygate

Is there a keyboard shortcut for Save and for +New Page?

There are currently no keyboard shortcuts for Showkase interface buttons but thank you for posting your suggestion here where it will be seen by the developers.

367

(7 replies, posted in Showkase Support)

Thanks for the additional information.

The line you noted above sets several attributes for each image so it certainly looks like my initial suggestion regarding max_input_vars might be in the right ballpark.
Try increasing max_input_vars further (to something much larger such as 2000) to see it this solves the problem.
If I was out by just one and max_input_vars needs to be 7 x the number of images, then 1200 would not be enough for a 180 image gallery.
I was pretty sure that 6 x the number for images is all that should be required when I posted earlier but there is no harm in trying a larger amount in case I was wrong. What you say in your latest post certainly points towards a low max_input_vars being the cause of the problem.

I have just done some testing of my own and in a gallery of 33 images, a max_input_vars of 200 results in an undefined offset (when clicking 'Save' on the 'Images' page tab) but a max_input_vars of 201 works fine. Neither 200 nor 201 divide exactly by 33 but they are both just over 6 so trying a larger value (such as 7 x the number of images) might yet work.

Also, if you have not yet tried increasing your PHP memory_limit, this might also be worth a shot.

368

(7 replies, posted in Showkase Support)

It looks like you might be reaching your PHP max_input_vars limit.
Each image in a Showkase gallery page has 6 different variables associated with it so in order to process a large gallery, you will need to ensure that max_input_vars is at least 6 x the number of images in the gallery.
For example, if you have a gallery with 200 images, then the max_input_vars will need to be at least 1200.
I notice in your screenshot that the undefined offsets begin at 166 which equates to a max_input_vars value of 996 (166 x 6 = 996) so it sounds like your max_input_vars might currently be set to 1000 (and it needs to be higher for your site).

You should be able to check your PHP settings using phpinfo() as follows:

  • Create a new file in a plain text editor with the following code: <?php phpinfo(); ?>

  • Save the file with a .php file extension (for example, 'phpinfo.php').

  • Upload the file to your web server and open it in a browser.

You should be able to change PHP values using a php.ini file, via an .htaccess file or via your web hosting online Control Panel.
If you have trouble changing any PHP values, your web host should be able to help you out.

Hopefully increasing max_input_vars will solve your problem.

If this does not help, then here are other things that you can try.

(1) Please try installing and running the Showkase Server Compatibility Test to check that your server has all the features Showkase needs.
If any of the tests fail, there are troubleshooting tips on the test's support page (link above).
Even if you ran the test before installing Showkase, please try again in case your web host has made any changes recently.

(2) If you are not already using the latest version of Showkase (v1.6.1), please try upgrading to see if this helps.
For a list of changes between versions, please see the Version History.
Full instructions for upgrading Showkase can be found here.

(3) Try going to 'System -> Repairs' and clicking the 'Repair' button to rebuild the page records.

(4) If the error message happens only when deleting images from certain gallery pages, try editing the pages in question, going to the 'Advanced' tab and clicking the 'Rebuild' button to rebuild the gallery.

(5) Check and increase your PHP memory_limit directive (in a similar way to max_input_vars above).

(4) If none of the above helps, then try running Showkase in debug mode to see if a more informative error message is displayed when the problem occurs.
Open your 'showkase/admin/settings/constants.php' file in a plain text editor and change line 12 from:

define('DEBUG', false);

... to:

define('DEBUG', true);

This should help to track down the exact cause of the problem.
Please note that the line number above refers to the current version of Showkase (v1.6.1).

I would also recommend that you make a complete backup of your site before you change anything, just in case anything goes wrong and you need to reinstate the original files at a later date.

I hope one of my suggestions above helps to solve your problem.

369

(1 replies, posted in Showkase Support)

Unfortunately, there are no dedicated keyboard shortcuts for Showkase interface buttons.
However, you might like to post your suggestion in the Feature Requests forum thread.
This keeps all the ideas together and ensures that they are not overlooked by the developers.
I do not know the likelihood of any suggestions being implemented but this is certainly the best place for all ideas.
Thank you.

Edit:
Many thanks for posting your suggestion in the Feature Requests forum thread.

370

(5 replies, posted in Showkase Support)

You're welcome.
I'm glad you've found a suitable compromise.
Thank you for letting me know.

371

(5 replies, posted in Showkase Support)

The thumb count was the problem. Thanks!

You're welcome!

To fix the gap on the left side that is set aside for the nav icon, I added to the custom.css file the following to get it to align left with the image block:

I'm glad you've been able to left-align the thumbnails to your liking. Thank you for sharing your solution.

Any ideas on how to get the thumbs to stay immediately below the image no matter what the height of the page is?

If you are looking to always have the top of the thumbnails flush against the bottom of the main image, then the only way to do this using the available configuration options would be to set imagePadding="0" and thumbPadding="0" and then either set imageScaleMode="FILL" (probably not appropriate for your gallery) or ensure that your images are large enough that they will always need to be dynamically scaled down slightly by Juicebox to fit within the gallery's image area when the gallery is displayed.

Otherwise, you could perhaps use some custom CSS such as the following to move the thumbnail container (and its navigation buttons) up slightly. (However, I would always recommend using the available configuration options where possible as Juicebox will not know of any custom CSS modifications that you make. Juicebox may expect certain elements to be in certain places and shifting them around via CSS may lead to unforeseen problems and unwanted knock-on effects.)

.jb-idx-thumbnail-container, .jbn-nav-button  {
    margin-top: -20px !important;
}

Again, this will work only if all your images are larger than the gallery's image area. If any of your images are smaller than the image area and are not dynamically scaled up (check your gallery's imageScaleMode value), then there may be a gap below your main images. (There is no easy way to always just attach the top of the thumbnails to the bottom of the main image.)

372

(5 replies, posted in Showkase Support)

I can't get the thumbnails to align left and immediately below the main image.

The default value for maxThumbColumns is 10 but your gallery has only 8 images so Juicebox will be reserving enough space for 10 thumbnails, leaving room for extra thumbnails which your gallery does not have. Try setting maxThumbColumbs="8" (in the 'Thumbnails' section).
It might be difficult to exactly align the thumbnails with the left-hand edge of the main image (Juicebox will reserve space for the thumbnail navigation buttons which will be required in a narrow browser window and thumbnail padding will also need to be taken into consideration) but you could perhaps use imagePadding to line them up and also set thumbNavPosition="BOTTOM" to position the thumbnail navigation buttons below the thumbnails, clearing some space to their left.

Also, can't get the Gallery title position to move from the default - bottom left.

The 'ARTSY' text below your gallery is actually the Showkase page title ('Page Content -> Page title') rather than the Juicebox Gallery Title.
If you want to move the page content (including the page title) from below the gallery to above the gallery, then it is not possible with the available interface options and you'll need to edit one of the Showkase source files.
Open the 'showkase/_themes/base/pagetypes/juicebox.tpl' in a plain text editor.
Cut lines 18-23 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 2:

{block "content"}

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

Be sure to re-publish your site after making this change.

373

(2 replies, posted in Showkase Support)

Thanks for sharing!

It's often enough to just press Ctrl + F5 to reload the current page from the server (but, if all else fails, clearing the browser's cache is certain to solve any browser caching issues).

374

(3 replies, posted in Showkase Support)

You're welcome!

375

(3 replies, posted in Showkase Support)

You're welcome!