276

(7 replies, posted in Showkase Support)

The code should be in your weddingringslondon.co.uk/_themes/boma/js/custom.js file but it does not seem to be there (it seems to be an empty file).
Please double-check that the code is in the correct file and clear your browser's cache before reloading your website.

I checked my suggestion in a test site under the Boma theme (in Mobile Safari on an iPod Touch 6 running iOS 11.2) before posting it and it seemed to work well for myself so, once the code is in the correct file, it should hopefully work for yourself, too.

277

(7 replies, posted in Showkase Support)

Do the mobile versions and desktop / tablet versions have different start index files.

No. Desktop and mobile devices all display the same HTML files but the styling of the pages differs depending on the screen size. The CSS controlling the layout of the pages for the Boma theme can be found in the '_themes/boma/css/styles.css' file.

Rather than delve into Showkase's own CSS and JavaScript code which handles the hiding/showing of the navigation menu, perhaps the easiest way to have the menu appear in its expanded state on mobile devices would be to manually trigger a click on the menu icon once the page has loaded.
Try adding the following code to your site's '_themes/boma/js/custom.js' file.

$(document).ready(function() {
    $('.icon-menu').trigger('click');
});

Hopefully this will be a suitable solution for you.

278

(11 replies, posted in Showkase Support)

Seeing all the PHP code on the web page suggests that you do not have PHP installed (or configured correctly) on your web server.

Accessed the ftp folder at home on a few different web browsers...

Are you accessing the Showkase Server Compatibility Test's 'index.php' web page using ftp:// protocol?
You should be viewing the 'index.php' file using the http:// protocol (or https:// if you use SSL) like a regular web page.

Make sure that you have PHP (5.2.0 or later) installed and open the 'index.php' using a regular http:// or https:// URL, for example:

http://www.example.com/sktest/index.php

I hope this points you in the right direction.

279

(6 replies, posted in Showkase Support)

On further investigation, the "Notice:  A non well formed numeric value encountered" message may have been displayed as a result of running Showkase under PHP 7.1.

We have just uploaded a new version of Showkase (v1.7.2) to address this issue and I would advise anyone using PHP 7.1 or above who encounters the "Notice:  A non well formed numeric value encountered" message to upgrade their site to Showkase v1.7.2. Showkase v1.7.2 is now compatible with both PHP 7.1 and PHP 7.2.

We have not yet updated the Version History page (this will be done in the next website refresh) but the new version can now be downloaded using existing download links. (Upgrades are free within the same major version number and download links always point towards the latest version rather than the version purchased.)

Full instructions for downloading the latest version and upgrading sites can be found on the Upgrading Showkase support page.

280

(11 replies, posted in Showkase Support)

I think it might be very difficult (if at all possible) to get Showkase working in a Google Cloud environment.
There are instructions for Serving Websites and PHP on Google Cloud Platform but the talk of PHP apps within Google Cloud suggests that Google Cloud does not provide a regular PHP environment which would support Showkase (and which Showkase was designed to work in).

It would be much easier to get Showkase up and running on web space provided by a regular web host (following the installation instructions here).

There are many web hosts that offer free web space which should be suitable for hosting a Showkase site. Showkase does not really need any special server requirements. Most web hosts providing web space and PHP 5.2.0 or later should be fine. Please see the System Requirements for more details.
Try a web search with terms such as 'free web hosting' but please bear in mind that with a free hosting account, you may get little or no support, less reliability (more server down-time) and fewer features.

Whatever web space you sign up for (whether it is a free or paid for account), be sure to run the Showkase Server Compatibility Test to check that your server has all the features Showkase needs.)

281

(6 replies, posted in Showkase Support)

That's great! I'm glad that you've been able to resolve your problem with the help of your web host.
Thank you very much for posting back to let me know.

282

(1 replies, posted in Showkase Support)

Your galleries are SimpleViewer (Flash) galleries and, unfortunately, many browsers have started blocking Flash content by default. What you are seeing in Chrome is the Mobile Player (HTML fallback) version of SimpleViewer.
You can re-enable Flash in your own Chrome browser but, unfortunately, there is nothing you can do to ensure that visitors to your web site see the Flash Version of your galleries (as their own browsers may also be blocking Flash).

Please see this forum post where I've written much more about the subject (and how to re-enable Flash in Chrome).

With the demise of Flash imminent, I would recommend changing your galleries over to Juicebox. Again, there is more information (and further links) about Juicebox in the forum post.

If you'd like to swap a gallery over from SimpleViewer to Juicebox in Showkase, just edit the gallery page in question, go to the 'Advanced' tab and click the 'Change' button next to 'Juicebox Page'.

Please note that as Juicebox was written from the ground up for a different platform than SimpleViewer (HTML5 vs Flash), Juicebox and SimpleViewer share similar but not identical feature sets. As such, it may not be possible to exactly match a SimpleViewer-Pro gallery using Juicebox-Pro, although you should certainly be able to get close (and Juicebox galleries, being HTML 5, will be immune from all the problems that are currently affecting Flash).

I hope this helps to clarify things.

283

(6 replies, posted in Showkase Support)

Thank you for trying my suggestions and for providing the debug information.

The getBytes() function in the 'helpers.php' file which throws the error does a simple numeric operation on a variable which, depending on where the function is being called from, could be the PHP memory_limit, the PHP post_max_size or the PHP upload_max_filesize.
The problem could be due to how your server is reporting one (or more) of these values.
If these values are not in an expected format, then the variable being used in the getBytes() function may not be numeric, causing the error.

Please check the memory_limit, post_max_size and upload_max_filesize values on your server.
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 can then search the page for the terms memory_limit, post_max_size and upload_max_filesize to find their values.
Please post back with the values you find for each of these PHP directives.
It might also help if you could post the link to the 'phpinfo.php' file so that I can take a look at your PHP settings for myself.
This should hopefully shed some more light on the problem.

Also, please let me know what version of PHP your server has installed.

It might also be wise to install and run the Showkase Server Compatibility Test to see if any errors are reported there.
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 further clue as to the nature of the problem.

284

(6 replies, posted in Showkase Support)

I'm really not sure exactly what has happened during your migration process but hopefully my notes and suggestions below will help.

It certainly looks like your Showkase installation is in its own subdirectory (marinakrasnovid.com/showkase/) rather than in your root directory so the first thing to do would be to run 'System -> Setup' to ensure that Showkase knows exactly where it is located.
On the 'Setup' page, you should be able to enter a path in the 'Path to your web site folder' input field before clicking the 'Setup' button. It looks like the correct path should be "/showkase/".

The "non well formed numeric value" error message you quoted is not an error I've ever encountered before using Showkase.
It is a PHP error (rather than an error generated specifically by Showkase itself) but just the message itself without any context is, unfortunately, rather unhelpful. It might help to run Showkase in debug mode to see if a more detailed error message is displayed in the application's status bar on publishing which might help to pinpoint the cause of the problem (for example, letting us know the page and line number causing the problem).
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);

If this provides more detailed information about the publishing problem, please let me know.

Also, I notice that you currently use Showkase-Pro v1.4.2.
It might be worthwhile upgrading your site to the current version (v1.7.1) to see if this helps. There have been many changes since v1.4.2 (please see the Version History page for a full list of changes between versions) and upgrading might help.
If your web server runs PHP 7, then you'll need at least Showkase v1.4.3 (this was the first version of Showkase to be compatible with PHP 7).
Full instructions for downloading the latest version of Showkase and upgrading a site can be found on the Upgrading Showkase page.

Once your Showkase site is fully functional again, then if you want your site to be accessible from your root directory (without having to move all your Showkase files), then you should be able to follow the 5 steps in the Showkase Home Page support section.
Otherwise, instructions for moving a Showkase site can be found in the Changing Your Installation Directory support section.

If the suggestions above do not help, then I might be inclined to just install a fresh installation of Showkase on your server (perhaps in your root directory if that's where you'd like it to be) and then just import all the pages from your existing Showkase site (via 'Site -> Import').
Installing a new Showkase site should take only a few minutes and you can import multiple pages at once so getting a new site up and running with your existing content should not take too long (and might be a quicker and easier option than trying to troubleshoot and fix your existing migrated site).

Hopefully my notes above will point you in the right direction and give you a few things to try.

285

(1 replies, posted in Showkase Support)

Please see this FAQ:
How do I allow or prevent users from saving gallery images?

Essentially, set:
showOpenButton="TRUE" (in the 'Lite' section)
... and/or:
showDownloadButton="TRUE" (in the 'Button Bar' section)

Both the 'open' and 'download' buttons appear in the gallery's Button Bar so make sure you set buttonBarPosition to a value other than NONE (otherwise the entire Button Bar will not be displayed, regardless of individual button settings).

286

(3 replies, posted in Showkase Support)

You're welcome.

287

(3 replies, posted in Showkase Support)

It's not possible to include .pdf files within any Showkase gallery type (ListViewer, Juicebox or SimpleViewer) as the Showkase upload module supports only images.
You'd need to upload your .pdf files to your web server via FTP (outside Showkase) and then either link to them from within your Showkase pages or embed them into your Showkase pages using techniques such as those discussed in this forum thread:
https://stackoverflow.com/questions/291 … df-in-html

Any code you want to include in a Showkase page (for example a link using an <a> tag or an <embed> or <object> tag) can be entered into the Showkase page's editor in 'Source' mode: click the 'Source' button on the editor's toolbar.

I hope this points you in the right direction.

288

(6 replies, posted in Showkase Support)

This issue has now been fixed in Juicebox v1.5.1 which has just been released (25 August 2017).
Please see the Version History for a full list of changes.
Full instructions for upgrading can be found on the Upgrading Juicebox support page.

Please note that Juicebox v1.5.1 has not yet been integrated into Showkase but, until the next version of Showkase is released, you can download Juicebox-Pro v1.5.1 separately and integrate it into your Showkase site by following the Installing a Pro Viewer instructions.

289

(1 replies, posted in Showkase Support)

It can often be quite difficult to pinch-zoom a Juicebox gallery as the gesture can often be misinterpreted as the start of a swipe (for navigation).
However, I see the problem you are referring to (on both the Splash Page and in a Large Screen Mode gallery) on an iOS device and I think it may be related to the way that Showkase resizes the gallery and/or web page itself.
Unfortunately, I do not know of an easy fix for this but I have notified the developers who will certainly investigate further.
Thank you for reporting the problem. Hopefully there will be a fix in a future version.

290

(3 replies, posted in Showkase Support)

Thank you for posting your suggestion in the Showkase Feature Requests thread.
You could post it in the Juicebox Feature Requests thread, too, if you like (as it is perhaps more relevant to Juicebox than it is to Showkase itself).

291

(3 replies, posted in Showkase Support)

If you set imageClickMode="OPEN_URL" ('Main Image' options), then, when a main image in the gallery is clicked, the corresponding linkURL (entered on the gallery page's 'Images' tab) is opened in the specified linkTarget window.
This would almost certainly be the easiest way to set something like this up.
However, it would be the main image that would need to be clicked (not the thumbnail) and the linkURL web page would be opened in a new tab (rather than in a pop-up window).

If you've not got many sample videos to display, then perhaps you could set up a separate 'Basic' page and embed the videos into this page (instead of trying to incorporate them into your Juicebox gallery).
Here's a sample 'Basic' page in a demo Showkase site which embeds a couple of videos.

If you really want to have a video play in a pop-up window when a thumbnail is clicked, then try the following:
(1) Create a separate web page manually (not in Showkase) and embed your video into it by whatever method you like (HTML 5 <video> tag, YouTube embed, etc.).
(2) Upload your video's web page to your web server.
(3) Enter the URL to this web page as the corresponding image's linkURL (on the gallery page's 'Images' tab).
(4) Edit the gallery page in Showkase, click 'Source' on the editor's toolbar to enter source mode and add the following code to your web page.

<script>
  function openWindow() {
    window.setTimeout(function() {
      var index = jb.getImageIndex();
      var info = jb.getImageInfo(index);
      var url = info.linkURL;
      window.open(url, '_blank', "height=400,width=600");
    }, 500);
  }
  jb.onShowThumbs = function(showing) {
    if (showing) {
      window.setTimeout(function() {
        $('#jb-glry-id-0_thumb_0, #jb-glry-id-0_thumb_1').not('.bound').addClass('bound').click(function() {
          openWindow();
        });
      }, 500);
    }
  };
  jb.onThumbPageChange = function() {
    window.setTimeout(function() {
      $('#jb-glry-id-0_thumb_0, #jb-glry-id-0_thumb_1').not('.bound').addClass('bound').click(function() {
        openWindow();
      });
    }, 500);
  };
</script>

This example displays a pop-up window for the 1st and 2nd thumbnails in the gallery.
The id #jb-glry-id-0_thumb_0 represents the 1st image in the gallery (the internal numbering starts at 0 for the 1st image). You can change the thumbnails as required and extend this example to work for more thumbnails (each loading their own individual linkURL when clicked) if you like.

The code above uses the Juicebox-Pro API to check when a new thumbnail page is displayed (onThumbPageChange()) as the thumbnail you want to add the custom click handler to might not be visible when the gallery is initially displayed (it might be on a subsequent thumbnail page and might not initially be included in the Document Object Model). The click handler also needs to be added when the thumbnails are shown after being hidden (onShowThumbs(showing)). (The code also uses the API to fetch the image's linkURL.)

If you just had a single video per gallery, then you could hardcode the URL to the video's web page into a window.open command (and do away with the openWindow() function) but the code above will allow for multiple thumbnails to be selected (each with their own linkURL).

This is not a perfect solution by any means (a couple of short delays are required to ensure that things are in place) but it might at least point you in the right direction.

292

(3 replies, posted in Showkase Support)

You're welcome!

293

(3 replies, posted in Showkase Support)

Using enableDirectLinks should have no negative impact on page loading times.

Using enableDirectLinks allows each image in a Juicebox gallery to have a unique URL (the page's URL with a # identifier corresponding to the image number within the gallery).

When a new image is selected in the gallery (via the thumbnails or navigation buttons), Juicebox amends the URL in the browser's address bar (using the # and the appropriate image number) but because the page URL remains the same and Juicebox uses a # to identify the image (rather than having a completely separate web page for each image), the page is not actually reloaded (and neither is the gallery itself). The gallery just displays the selected image (as normal) and the # identifier is added to the URL. The full URL (with the # identifier) can then be copied from the browser's address bar and sent to someone to let them see a particular image in the gallery.

I hope this helps to clarify things.

294

(6 replies, posted in Showkase Support)

Id love to have you look under the hood.

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

In the meantime, I think I might have found the root of the problem.
Each Showkase page has its own folder in the Showkase root directory. Inside each page's folder is a file named 'page.xml'. (This file contains information about the page such as the page type.)
You should be able to view the 'page.xml' files directly in a browser. For example, here is the 'page.xml' file for one of the page's in our Live Demo: https://www.showkase.net/livedemo/about-page/page.xml
However, trying to view the 'page.xml' file for any of your own Showkase site's pages fails (with the browser showing just the folder's 'index.html' page instead), for example: http://renaldi.com/projects/page.xml

It looks like the 'page.xml' files are missing from your Showkase site (they may not have been transferred successfully to their new locations when you moved your site) and this may be the reason for the incorrect page types.
If the 'page.xml' files are present in the page folders, then please check that their permissions are not too restrictive. Default file permissions of 644 should be fine.

Try creating a new page (in your moved site) and see if a 'page.xml' file is created in the page's folder on your web server.
If a 'page.xml' file is created for the new page, then it looks like the problem might be that your site's existing 'page.xml' files were not transferred successfully when you moved your site.

Otherwise, if a 'page.xml' file is not created for the new page, then there may may some underlying issue on your server whereby Showkase is unable to create the 'page.xml' files in the page folders.
If this is the case, then try running Showkase in debug mode to see if any warning or error messages are displayed in the application's status bar which might help to pinpoint the cause of the problem.
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);

The line number above refers to the current version of Showkase (v1.7.0).

I hope this points you in the right direction.

Edit:
It might also be wise to install and run 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 further clue as to the nature of the problem. (Also, there are troubleshooting tips in the link above.)

295

(6 replies, posted in Showkase Support)

I have not encountered this problem before so, unfortunately, I do not know what might be causing it. (My best guess was corrupt page records but rebuilding them had not fixed the problem).

I don't know if it will help but try upgrading your site from Showkase v1.6.1 to the latest version (v1.7.0) to see if this makes a difference. (It is certainly something that I would try myself.) Please see the Upgrading Showkase support page for details.
This will replace all core Showkase files (with the latest versions) whilst leaving all your custom pages and settings in place.

Also, you could try editing one of the troublesome page, going to the 'Advanced' tab and changing the page type from 'Gallery Index Page' to whatever page type it should be ('About Page', 'Basic Page' or 'Contact Page').

If this still does not help, then it might 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 site login details.

296

(6 replies, posted in Showkase Support)

That certainly seems strange.
It looks like all the pages have become clones of your gallery index page.

The first thing Id try is to re-publish your site (if you have not already done so) by just clicking the 'Publish' button.

The next thing I'd try is to go to 'System -> Repairs -> Repair' to rebuild the page records.

Hopefully one of these suggestions will help.

Otherwise, as long as you made a backup of your site before moving it, if the intention of the move was to allow your site to be accessible from your root directory, then you could maybe reinstate your backup (to the way things were before moving your site) and then just follow the 5 step instructions in the Showkase Home Page support section.

297

(3 replies, posted in Showkase Support)

You're welcome!

298

(3 replies, posted in Showkase Support)

The Showkase root directory's 'index.php' file is used (to display the Showkase home page) only when the Showkase site is accessed via the root directory (without specifying an actual page name).
Every Showkase page has its own folder in the Showkase root directory (and an 'index.html' page inside the folder).
For example, a Showkase page named 'my_page' will be located here: http://www.example.com/showkase/my_page/index.html
However if the designated Showkase home page is 'my_page' and a visitor to your site goes to: http://www.example.com/showkase/
... then the 'index.php' page will be used to show the '/my_page/index.html' page.

That's really just an aside about the function of the root 'index.php' file. (Your tags should not go in this file).

If you want to have all your own <link> tags included on all your Showkase pages, then the best place to put them would be alongside the existing <link> tags in the /showkase/_themes/base/pagetypes/basetheme.tpl file.
Open the basetheme.tpl file in a plain text editor, scroll down to the {block "stylelinks"} section and add your own <link> tags alongside the other ones there.
All you now need to do is republish your site for all your own <link> tags to be added to all your Showkase pages.

299

(1 replies, posted in Showkase Support)

The 'Site -> Customize Viewers' tab allows you to customize the image viewers (gallery types) that Showkase supports: Juicebox, ListViewer and SimpleViewer. Any values changed in this section will be applied as default values when you next create one of these galleries.

Kosel is a theme (rather than a 'viewer'). The theme determines the layout and style of the pages (rather than the galleries that might be embedded in the pages).
If you want to customize a theme beyond what is available in the interface ('Site -> Customize Theme'), then please see the Creating Themes support section.
There's more information there than I could possibly include in a forum post (including a section on 'Inside the _theme Folder' inside the Advanced Theming section which it sounds like you might be interested in).

The _themes/base/ folder contains information common to all themes. The _themes/kosel/ folder contains information specific to the Kosel theme (that builds on the 'base' information). If you can't find what you're looking for in the _themes/base/ folder, try looking in the _themes/kosel/ folder. If whatever you are looking for is directly related to the Kosel theme, then it will likely be in one of these two folders.

300

(3 replies, posted in Showkase Support)

I'm glad to hear that reverting to v1.6.1 has resolved your problem. Thank you for letting me know.
Unfortunately, I have been unable to reproduce the problem you are describing myself (which makes me think that some of your custom modifications might be contributing to the problem).

If anyone else is experiencing difficulties with 'External fit px' when upgrading from v1.6.1 to v1.7.0, please let me know so that I can try to reproduce the problem myself and notify the developers if necessary. Thank you.