726

(1 replies, posted in Showkase Support)

Please install and run the Showkase Server Compatibility Test to check that your web server has all the features that Showkase needs.

If all tests pass, then try reinstating all the core Showkase files as if you were upgrading to a new version.
Instructions on how to do this can be found in the 'How to Upgrade' section on the Upgrading Showkase support page.

If you continue to experience difficulties, it may help to know what type of web server you have installed Showkase on (Linux vs Windows) so please let me know.

Also, I know that you say you are using the latest version but you do not mention a version number so I cannot be sure which version you are using. The latest version is v1.3.1 so please ensure that this is the version you are using. Thank you.

727

(4 replies, posted in Showkase Support)

Seems to me that the Pro options should not show up in the config menus, until installed.

Perhaps, but leaving the Pro options exposed allows Standard users to see what is available to Pro users and to set up Pro galleries in preparation for upgrading the core image viewer files. Pro options will be applied to the gallery XML files immediately and will take effect as soon as the Pro image viewer is in place.

Sorry about the link. I have now corrected it in my post above.

I wish I could tell you exactly what the problem was and how you could perhaps try to avoid it in future.
It sounds like something may have happened on your web server to corrupt a file during a publish action but I really do not know.
However, I am glad that the import suggestion has helped you regain control of your site. Thank you for posting back to let me know.

729

(4 replies, posted in Showkase Support)

Are there issues in the Kosel theme re: sharing icons, or am I missing a step?

All Juicebox-Pro options are available under both Boma and Kosel themes (there are no Juicebox-Pro restrictions under any theme).

First of all, try clearing your browser's cache to ensure that your browser is fetching and using the most recent versions of your gallery files.

If this does not help, then check to see if your gallery has the Juicebox badge/link in the lower-right corner. If it does, then your gallery is a Juicebox-Lite gallery and will need to be upgraded to Juicebox-Pro before Pro configuration options (such as sharing options) become active.
Instructions for 'Installing a Pro Viewer' and upgrading existing galleries can be found here.

If you continue to experience difficulties, then please post the URL to your gallery so that I can take a look for myself and help further.

As far as I am aware, the Hierarchy Request Error is a PHP DOMDocument error which occurs when trying to move a node into itself, although I do not know why this error is generated when you try to publish your gallery.

We know that Showkase works OK on your web server (as you have a second working Showkase site) and we also know that all the core Showkase files are present and correct (as you have tried re-uploading them, overwriting the existing ones) so the problem may lie with one (or more) of your Showkase pages. With this in mind, you might like to try the following.

*** Please make a full backup of your entire Showkase site before proceeding. ***

Try trashing your Showkase pages on the 'Pages' tab, one by one (starting with the last one you created and working backwards), and try to Publish your site each time to see if the Hierarchy Request Error still occurs.
(When trashing a page, it will be moved into the '_trash' directory. You can reinstate a trashed page using the 'Site -> Import' functionality.)
If you find a page which is causing the problem, you could recreate it manually and reinstate all others using the 'Site -> Import' functionality.

Unfortunately, I do not know what may be causing your problem but a possible workaround would be to create a completely new Showkase site and use the 'Site -> Import' functionality to import all existing pages from the currently broken Showkase site. This might be a relatively quick option to get your site up and running again without having to create all your pages from scratch.

I have another ShowKase site running fine in the same directory tree.

Just to check, are both Showkase sites in completely separate directories? (I would not recommend nesting one Showkase directory within another Showkase directory.)

I am not sure what might have caused such a problem (especially knowing that everything has been working OK up to now).
Has your web host changed anything lately (such as PHP configuration settings) which might have caused the problem?

Unless something has happened with your web server, it is unlikely that you will have lost any of your pages. (The files should not have been deleted unless you or your web host have deleted them.) Check your Showkase file structure to see if the folders corresponding to the pages you have created are still there (in your root Showkase directory).
As long as they are still there, I would take this opportunity to make a backup of your entire Showkase directory just in case anything else goes wrong.

First of all, try installing and running the Showkase Server Compatibility test. If your web host has changed anything which would result in your web server no longer having all the functionality required to run Showkase, the Server Compatibility Test should hopefully pick it up.

If all tests pass, then try reinstating all the core Showkase files as if you were upgrading to a new version.
Instructions on how to do this can be found in the 'How to Upgrade' section on the Upgrading Showkase support page.

Hopefully this will resolve your problem.

732

(4 replies, posted in Showkase Support)

Your video is embedded on a 'Basic' page but you have grouped this page under the 'Videos' page which is a 'Gallery Index' page. Therefore, you need to click the 'Videos' link in the menu to see all pages grouped under the main 'Videos' page. You can then click the link to the 'Basic' page.

If you want the page your video is on (the 'Basic' page) to be a top level page (not grouped under any other pages), then edit the page and select 'none' for 'Group Under' in the 'Site Navigation section'. You can then delete the 'Videos' (Gallery Index) page and rename the 'Basic' page to 'Videos'.

Also, only gallery thumbnails (for Juicebox, ListViewer and SimpleViewer pages) are displayed on a 'Gallery Index' page and you have no galleries grouped under the 'Videos' page which is why nothing is displayed on the 'Videos' page itself. (It is not possible to automatically create a thumbnail page for videos like you can for image galleries.)

The background image you have set up for your 'Basic' page (Blank_Web.jpg) displays on you 'Basic' page as expected.
If you do not see this, then try clearing your browser's cache before reloading the page.

733

(4 replies, posted in Showkase Support)

The Vimeo videos embedded into the Patrick Surace demo are included on a 'Basic' page and the embedding code for each video looks something like this:

<iframe allowfullscreen="" frameborder="0" height="576" mozallowfullscreen="" src="http://player.vimeo.com/video/12345678?color=ffffff" webkitallowfullscreen="" width="1024"></iframe>

The embedding code would be entered into the text editor in 'Source' input mode.
Check that your embedding code looks like the above. (It sounds like you may be using some code other than an iframe.)
Further details on embedding Vimeo videos can be found here.
If you continue to experience difficulties, then please post the URL to your web page so that I can take a look and help further.

I'm glad that worked. Thank you for posting back to let me know.

On further investigation, in your DE and FR sites, the latest Showkase v1.3.0 files seem to be in place but the current HTML files have been generated with Showkase v1.0.1 templates (as can be seen in the comment in the <head> section).
Try republishing your DE and FR sites in case something went wrong during publishing (or perhaps the DE and FR sites have not yet been published after upgrading to Showkase v1.3.0).

I see the problem you describe in your DE and FR sites (but have not been able to replicate the problem in a test site of my own).
It certainly looks like a CSS problem which may be caused by a mixture of old and new files (perhaps one or more of the updated Showkase files did not overwrite existing files on your web server during the upgrade).
Try re-uploading all the '_themes' files from the Showkase v1.4.0 download zip package to your DE and FR Showkase installations on your web server to ensure that all files are present and correct. Hopefully this will help.
(If you have modified any '_themes' files or have edited any 'custom.css' files, please make a backup of them first before replacing them on your web server.)

737

(9 replies, posted in Showkase Support)

Another question, I am using my logo on the header, can I link it to something ?

Yes. Go to 'Site -> Site Settings' and enter the URL you wish to use in the 'Site Header -> Site header link' text field.

738

(9 replies, posted in Showkase Support)

@gustavocampos1

The 'Base font size (px)' in the interface goes up to only 16. All values set within the interface should result in a layout that looks OK.

Adding custom CSS can cause knock-on effects that might need to be resolved (as you have discovered).

If you find that your text is not being displayed in its entirety, then you may need to expand the container it is in with further CSS rules.

If the problem you are having is that you are using the Kosel theme and the top of the menu text is disappearing, try adding the following to your '_themes/kosel/css/custom.css' file:

nav ul {
    padding-top: 5px;
}

If this does not help, then please post the URL to your web site so that I can take a look and help further.

Incidentally, if you are not already using the current version of Showkase (v1.3.0), you can upgrade following the instructions here.

The Kosel theme still displays the navigation menu horizontally (in Showkase v1.3.0) except in narrow browser windows or on mobile devices where a menu icon is displayed (four horizontal lines) which can be clicked/tapped to toggle a vertical menu on and off.
When I view both your web pages in desktop browsers, the navigation menu is displayed horizontally as expected. The submenu page displays the top-level menu on a single horizontal line of text and the secondary menu, which changes depending on the top-level page currently being displayed, is also on a single horizontal line of text (below the top-level menu).
If you are not seeing this, then please try clearing your browser's cache before reloading your site to see if this makes a difference.

740

(2 replies, posted in Showkase Support)

Did you add your site header logo to your Showkase Library ('Library -> Upload') and select it (in the 'Site -> Customize Theme' section) using the 'Browse' button or did you enter a URL manually? If you entered a URL manually, please make sure that the URL is an absolute path (in the form http://www.example.com/images/image.png) so that it is a valid path from any web page.

I have been unable to replicate your problem using the Library method so if you have not already tried this, please do so.
If you continue to experience difficulties, then please post the URL to your Showkase site so that I can take a look and help further.

741

(5 replies, posted in Showkase Support)

How do I go about stripping out the EXIF information?

Just removed all the metadata and the viewing files are the correct orientation.

It looks like you have figured out how to strip the metadata from your images (a batch process in an imaging program would probably be the best solution, and certainly the quickest).

The thumbnails are still the wrong rotation.

Try rebuilding your Juicebox gallery (edit your Juicebox gallery page and go to 'Advanced -> Rebuild this Juicebox gallery').
If this does not help, then please post the URL to your gallery so that I can take a look.
Also, it might help if you were able to upload one of the images that you are using that results in a correctly-oriented main image but an incorrectly-oriented thumbnail somewhere (and provide a download link) so that I can try to replicate the problem myself. Thank you.

With regard to Showkase not currently being able to rotate images, please post suggestions for future versions of Showkase in the Feature Requests forum thread. It keeps them all together and ensures that they are not overlooked. Thank you.

It looks like your gallery might have been given fixed dimensions before it became part of a svManager or Showkase management system.

Here are a few things to try:

Make sure that you are using Showkase's 'Gallery Manager' theme ('Site -> Change Theme -> Gallery Manager') which displays galleries at 100% x 100% (filling the entire browser window, or in your case, your iframe).
If you are already using this theme, then try changing the theme to something different ('Boma' or 'Kosel') and then change it back to 'Gallery Manager'.

Now that your 'g2' gallery is part of Showkase, you could try rebuilding the gallery (edit the Juicebox Gallery page and go to 'Advanced -> Rebuild this Juicebox gallery').

Although the 'g2' gallery is already part of Showkase, it looks to have been originally part of svManager and became part of Showkase during the upgrade.
You could try importing the gallery into Showkase using the 'Site -> Import' functionality (to create a new Showkase page from the gallery) and then load this new page into your 'iframe'.

If none of the above automated suggestions work, then try opening your http://coromandelflavour.co.nz/showkase/g2/index.html page directly in a plain text editor and manually change the gallery width and height both to 100%.

A further solution (though not as clean as simply setting your gallery's dimensions to 100% x 100%) would be to add the following code to your 'showkase/_themes/manager/css/custom.css' file:

body.type-juicebox {
    margin: 0 !important;
}

... to ensure that the margin on your page (visible when viewing http://coromandelflavour.co.nz/showkase/g2/index.html) is not displayed within the iframe.

One of these suggestions should hopfully solve your problem.

743

(5 replies, posted in Showkase Support)

I do not know what program you usually use to view your images but it is possible that it reads the EXIF orientation flag embedded in your images and rotates the images as they are being viewed, depending on the value of the flag.
Showkase and SimpleViewer do not read the EXIF orientation flag and simply display the images as they are.

There is little consistency between programs (and browsers) as to whether or not your images will be displayed as you expect.
Try viewing one such image directly in a number of different browsers (Firefox, Chrome, Safari, Internet Explorer and Safari). You will likely see the image being displayed in different orientations across the browsers.

The only way to be sure that a program will display your images as intended would be to re-save your images stripping out the EXIF data and then rotate the images afterwards until they visibly look correct. (You can then feed them to Showkase and SimpleViewer.)

I hope this helps explain things.

744

(3 replies, posted in Showkase Support)

Each theme uses its own default settings.
To reset the Kosel theme's Juicebox settings (for example), delete the 'showkase/_data/themedata/kosel/juicebox.xml' file.

Thank you for providing the URL to your web page.
I see what you are doing now (loading a Juicebox gallery created by Showkase into an iframe in a non-Showkase page).
I thought that you were loading a Juicebox gallery created outside of Showkase into an iframe on a 'Basic' Showkase page.
In this case, importing the gallery would not be possible (or a solution).

The problem seems to be that your iframe has dimensions of 750 x 490 but that your gallery has dimensions of 730 x 490 (resulting in the space that you report). Try setting your gallery's dimensions to be the same as your iframe's dimensions or set your gallery's dimensions to 100% x 100% so that the gallery fills the iframe no matter what size it is.

Rather than load the gallery into an iframe within a Showkase page, you could import the gallery into Showkase (and give the gallery its own Showkase page) by using the 'Site -> Import' functionality. This would allow you to manage the gallery within the Showkase interface and should also hopefully solve your problem with the space on your web page.

If this does not help (or you do not want to import the gallery), then please post the URL to your web page so that I can take a look and help further.

747

(1 replies, posted in Showkase Support)

First of all, I would recommend keeping your Showkase and WordPress installations completely separate from each other (in different directories, ie. not storing one within the other).
Having your WordPress installation within your Showkase directory may cause problems if you ever want to move or upgrade either of the programs.
Separating the two from each other would also solve the problem that you are currently experiencing.

In order to have Showkase create a Navigation Link, you would need to ensure that the name of the page does not match any existing page. You could initially call it something other than 'blogg' (just so that Showkase can create the necessary page) and then edit your Showkase pages manually to change the text displayed in the menu. However, please note that such manual modifications will be lost any time your Showkase site is republished.

Alternatively, you could also change the source code of Showkase to add a custom link to the end of your menu (bypassing Showkase's own Navigation Link functionality) by following the example in this forum post.

However, the easiest (and cleanest) solution would be to keep your Showkase and WordPress installations in separate directories.

748

(3 replies, posted in Showkase Support)

Unfortunately, there is no quick and easy way to reset all Juicebox gallery settings to their default values within Showkase.
If you change gallery configuration options at theme level (under 'Site -> Customize Viewers'), then these values will be applied to all galleries. However, if any settings have been changed at page level (on individual gallery pages), then these values will override theme level settings and you will need to change the page level settings back to change the corresponding galleries.

749

(6 replies, posted in Showkase Support)

If you want to use an image link (instead of a text link), try something like the following. Make sure the path to your Facebook logo image is correct.

$customLi = $navDom->createElement('li');
$customA = $navDom->createElement('a');
$customA->setAttribute('href', 'http://www.example.com/index.html');
$customImg = $navDom->createElement('img');
$customImg->setAttribute('src', '/facebook.png');
$customImg->setAttribute('width', '50');
$customImg->setAttribute('height', '50');
$customImg->setAttribute('alt', 'logo');
$customA->appendChild($customImg);
$customLi->appendChild($customA);
$navRoot->appendChild($customLi);

750

(6 replies, posted in Showkase Support)

If you want Showkase to add a custom link at the end of your menu on every page each time the 'Publish' button is clicked, you would need to to open the 'showkase/admin/classes/nav.php' file in a plain text editor, scroll down to line 177 and just before the return $navDom; line, construct the HTML you require within a <li> tag using PHP DOM techniques and append your custom DOM element(s) to the $navRoot variable.
For example, if you wanted to insert a link which displays the text 'Click Here' and directs the user's browser to the URL http://www.example.com/index.html, then you could use the following code:

$customLi = $navDom->createElement('li');
$customA = $navDom->createElement('a');
$customA->setAttribute('href', 'http://www.example.com/index.html');
$customText = $navDom->createTextNode('Click Here');
$customA->appendChild($customText);            
$customLi->appendChild($customA);
$navRoot->appendChild($customLi);

Please note that the source code of Showkase was not intended to be modified by users in such a manner and I do not know what (if any) knock-on effects this may have.
More information on using the PHP DomDocument class can be found here.
I hope this helps.