751

(7 replies, posted in Showkase Support)

Showkase v1.3.2 (including the new versions of both Juicebox v1.4.2 and SimpleViewer v2.3.2) has just been released.
Please see the Version History for a list of changes and the Upgrading Showkase page for details on how to download and install the latest version.

752

(7 replies, posted in Showkase Support)

Juicebox and SimpleViewer have both been updated to address the new SSL Flickr API requirements.
Showkase should hopefully be updated (with the new versions of Juicebox and SimpleViewer) sometime within the next day or two.

In the meantime, you can manually upgrade your existing Showkase installation with the new versions of Juicebox and SimpleViewer by downloading Juicebox and SimpleViewer individually and following the 'Installing a Pro Viewer' instructions here.

753

(7 replies, posted in Showkase Support)

You can download the latest versions of Showkase-Pro and Juicebox-Pro using the links provided in your original purchase email. If you cannot find your original purchase email or your links have expired, then please fill in this Download Link Request Form.

Please note that Showkase has not yet been updated with the new versions of Juicebox and SimpleViewer so your best bet at the moment would be to download Juicebox-Pro and follow the 'Installing a Pro Viewer' instructions here.

If you want to find out what the latest version numbers are for Showkase and Juicebox, you can check their respective Version History pages:
Showkase: http://showkase.net/support/history/
Juicebox: http://www.juicebox.net/support/history/

754

(7 replies, posted in Showkase Support)

Flickr have recently made a change to the way that API calls (which both Juicebox and SimpleViewer) must be made. Please see here for further details.

This issue has been already been addressed in the latest releases of both Juicebox and SimpleViewer and a new version of Showkase (with the new versions of the image viewers) will be released very soon.

In the meantime, you can upgrade your Showkase installation by downloading the latest versions of Juicebox and SimpleViewer and following the 'Installing a Pro Viewer' instructions here.
Even if you a not a Pro user, just download Juicebox-Lite and SimpleViewer-Standard and follow the instructions using the 'jbcore' and 'svcore' folders from these packages.

755

(9 replies, posted in Showkase Support)

I'm glad that you have been able to resolve your problem.
Thank you for posting back to let me know.

756

(9 replies, posted in Showkase Support)

The problem seems to be that when you go to vita-taylor.com it displays the s97231701.onlinehome.us/frankase/index.php page.
This will not work due to the paths used within Showkase.

vita-taylor.com should redirect/forward to just s97231701.onlinehome.us and then the Showkase site should display correctly at vita-taylor.com/frankase/.

It is not possible to display the Showkase site at the root of vita-taylor.com because the Showkase site is not at the root of s97231701.onlinehome.us.

You say that you have "set the destination of vita-taylor.com to blank" but have you tried setting it to s97231701.onlinehome.us?

If you would like to be able to view the Showkase site at s97231701.onlinehome.us instead of s97231701.onlinehome.us/frankase then please see the Showkase Home Page support section here.
Maybe this will help.

757

(9 replies, posted in Showkase Support)

Here's a bit more information about how Showkase works which might help explain what's going on.

Every page within a Showkase site, including the home page, is given its own folder (with the web page inside it).
Therefore, it is possible to get to view the home page by using two different addresses.
(1) Go directly to the Showkase root directory: s97231701.onlinehome.us/frankase/
The index.php page in that directory will display the home page (whatever the home page happens to be).
... or:
(2) Go to the actual directory of the page being used as the home page: s97231701.onlinehome.us/frankase/home/

All paths (to CSS files) within Showkase pages use the following notation:

<link rel="stylesheet" href="/frankase/_themes/kosel/css/styles.css">

The leading slash denotes the root directory so on s97231701.onlinehome.us, the path /frankase/_themes/kosel/css/styles.css resolves to s97231701.onlinehome.us/frankase/_themes/kosel/css/styles.css

The same files are used when using both your domains so the paths remain constant.
Therefore, when you try to visit your Showkase site on vita-taylor.com, Showkase is looking for the CSS file at vita-taylor.com/frankase/_themes/kosel/css/styles.css but it is not there. It can be found, instead, at vita-taylor.com/_themes/kosel/css/styles.css (notice the absence of the frankase directory in the path that works).

This is what made me think that vita-taylor.com is currently pointing towards s97231701.onlinehome.us/frankase and should just be pointing towards s97231701.onlinehome.us instead.
If it did, then all the paths within the Showkase pages would resolve to the correct locations.

If this does not fix the problem, then it might at least explain what is going on and help point you in the right direction.

758

(9 replies, posted in Showkase Support)

It looks like vita-taylor.com is currently pointing towards s97231701.onlinehome.us/frankase.
It should be pointing towards just s97231701.onlinehome.us instead.

You should then be able to access the gallery by going to vita-taylor.com/frankase.

Try clearing Facebook's own cache of your web page (by entering your web page's URL into Facebook's Debugger) to see if this makes a difference.

Unfortunately, it is not possible to have the shared image's thumbnail displayed in the pop-up share window due to limitations imposed by Facebook on what data can be passed via their share URL. Only one thumbnail can be used per web page. (The shared link will still point towards the correct image within your gallery, though.)

The image used in the pop-up share window can be set using an Open Graph og:image <meta> tag in the <head> section of your web page, such as the following:

<meta property="og:image" content="http://www.example.com/images/thumbnail.jpg" />

In order to choose an image for use in your gallery page's pop-up share window, 'Edit' the gallery page and upload the image you wish to use on the 'Upload' tab and then 'Update' and 'Publish' your site.
An og:image tag will be automatically generated on the gallery page.

761

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

762

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

764

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

767

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

768

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

772

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

773

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

775

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