I am still unsure as to what the cause of the problem is but perhaps the following links will allow you to find a suitable workaround.

It also will work if I move everything to a subfolder but then my home page url would have to change.

Please see the Showkase Home Page section in the User Guide which deals with this scenario.

If I were to try removing the site and starting from scratch, would i be able to re-upoad my site without having to rebuild it?

Please see the Site Backup and Restore section in the User Guide which should hopefully help.

Try installing and running the Showkase Server Compatibility Test just to make sure that your server has all the features Showkase needs.
If it passes all the tests, then at least we can rule these factors out.

853

(4 replies, posted in Showkase Support)

My suggestion was not to change the name of the folder on the server.

  • Enter a 'Nav Name' within Showkase using non-cyrillic alpha-numeric characters such as 'Gallery'.

  • Allow Showkase to create a corresponding folder on your web server using this 'Nav Name'.

  • Edit the 'index.html' files for each Showkase page and change the link text (not the link 'href' attribute) to Галерея.

For example, in each page's 'index.html' file, change:

<a href="/showkase/gallery/">My Gallery</a>

... to:

<a href="/showkase/gallery/">Галерея</a>

854

(4 replies, posted in Showkase Support)

This error message is likely to be displayed as, not only is the 'Nav Name' displayed in the navigation area of your site but it is also used as the name of the folder on your web server to store the page's files in.
The only workaround I can think of would be to use non-cyrillic alpha-numeric characters for the 'Nav Name' and then edit the generated pages manually afterwards to change the link text to whatever you like.

It sounds like there may be a problem with the 'index.php' file in the root of your Showkase installation (in your case, your web site's root directory).
Try re-uploading a fresh copy of the file from the extracted Showkase zip file (in the root directory alongside the '_themes' and 'admin' folder) to see if this helps.

A fix will be included in the next version of Showkase but, until then, you can make the change manually by editing the '_themes/kosel/css/styles.css' file in a plain text editor and changing line 31 from:

[data-icon]:before {

... to:

#menu-anchor [data-icon]:before {

(The line number above refers to Showkase v1.0.3.)

Thank you very much for the additional information.
I have now been able to reproduce the issue myself and have logged a bug report with the developers.
It does, indeed, seem to be a conflict between Showkase v1.0.3 and Juicebox-Pro v1.3.0/Juicebox-Pro v1.3.1 though I do not know the exact cause of the problem, and unfortunately do not have a solution at the moment.
However, having notified the developers, this bug should hopefully be fixed in the next version.
Thank you for reporting the bug.

Do you use Juicebox 1.3.1 in your Showkase test installation, too?

Yes. I used Showkase-Pro v1.0.3 with both Juicebox-Pro v1.3.0 and Juicebox-Pro v1.3.1.

The problem occurs only on your pages which have Juicebox galleries so it does look like a Juicebox-related problem but I still cannot replicate the problem myself.

Try installing a fresh installation of Showkase (into a completely different folder to your existing Showkase installation so as not to interfere with it) and create a Juicebox gallery page with the new installation to see if the problem still occurs.
If you upload the Showkase zip file to your web server and unzip the file on the server (from within your web account's CPanel), the whole process should take only a few minutes and might give us some useful information.

Also, please try installing and running the Showkase Server Compatibility Test.
It sounds unlikely that any problems will be highlighted but if you run the test then we can rule this out.

I see the problem on your web site but have been unable to replicate it in a test Showkase-Pro v1.0.3 installation.
It looks like a missing font from certain pages (your home page and gallery pages).
I would first try re-uploading the '_themes/kosel/' folder to your web server to ensure that all files are present and correct. Be sure to make a backup of the existing '_themes/kosel/' folder first, just in case anything goes wrong or if you have modified any files (such as 'css/custom.css') that you might want to reinstate at a later date.
Then rebuild your home and gallery pages (there should be no need to rebuild the galleries themselves, just the pages they are in) and finally clear your browser's cache before reloading your site to see if this has helped.

860

(3 replies, posted in Showkase Support)

The current version of Showkase-Pro (v1.0.3) has not yet been updated to include the latest version of Juicebox-Pro (v1.3.0).
You can manually upgrade your Showkase installation to use the Juicebox-Pro v1.3.0 files by replacing the 'jbcore' folder in the 'showkase/admin/plugins/juicebox/master/' folder with the 'jbcore' folder from your Juicebox-Pro v1.3.0 download package.
However, the new Juicebox-Pro options will not yet be available in the Showkase interface and if you wish to use any of them, you will need to manually enter them into your gallery's XML file.
Showkase-Pro should hopefully be updated soon (although I do not know exactly when this will be).

861

(1 replies, posted in Showkase Support)

You could perhaps use a blogging tool which features an RSS feed, create a custom web page to display the blog's content using a utility such as RSS2HTML (modifying the template that comes with RSS2HTML to match your Showkase pages, e.g. same background color, etc.) and include the custom web page in a Showkase page using an iframe. You would not be able to include RSS2HTML directly into a Showkase page as RSS2HTML requires PHP and Showkase generates HTML pages. (You could change the file extension of your Showkase page from .html to .php but the next time you update the page in Showkase, the .php page would not be updated and a new .html page would be generated instead.)

862

(1 replies, posted in Showkase Support)

Yes. Both SimpleViewer-Pro and Juicebox-Pro support the flickrSetId configuration option to display all images in a specified Flickr Set.
SimpleViewer-Pro - http://simpleviewer.net/simpleviewer/pr … tml#flickr
Juicebox-Pro - http://www.juicebox.net/support/config_ … kr-options

When creating a SimpleViewer or Juicebox gallery page in Showkase, select Flickr as the source of images and enter the Flick Set Id into the 'Flickr set id' text field.

863

(93 replies, posted in Showkase Support)

The current version of Showkase (v1.0.3) has not yet been updated with the new features available in Juicebox v1.3.0.
Until is it updated, if you would like to incorporate the new features in your Juicebox galleries, you could create a gallery preset file (using JuiceboxBuilder-Pro v1.3.0) and follow the 'Customize Individual Viewers' instructions here.

864

(4 replies, posted in Showkase Support)

The modifications you have made to your SimpleViewer gallery pages will be overwritten only if you edit and update these pages within the Showkase interface.

865

(93 replies, posted in Showkase Support)

@photojoe01

Please see the 'Customize Individual Viewers' section on this page.

866

(4 replies, posted in Showkase Support)

Unfortunately, there is a known bug in SimpleViewer-Pro whereby the Download Button does not function correctly when a baseURL is used which starts with a leading slash (to denote the root directory) as used by Showkase.
Hopefully this bug will be fixed in the next release but in the meantime, you can edit your Showkase gallery pages in a plain text editor and modify the baseURL entries so that they use absolute paths, e.g. in your 'Engagements' page (http://joehendricksphotography.com/enga … index.html), change the line:

baseURL : "/engagements/"

... to:

baseURL : "http://joehendricksphotography.com/engagements/"

867

(3 replies, posted in Showkase Support)

Is it possible to import existing galeries made with Juicebox Pro / Simpleviewer Pro builder in Showkase ?

Yes. You can embed an existing Juicebox or SimpleViewer gallery in a Showkase page by using the baseURL method of embedding:
Juicebox - http://www.juicebox.net/support/embeddi … ery-folder
SimpleViewer - http://simpleviewer.net/simpleviewer/su … l#external

Essentially, create your gallery, upload the entire gallery folder (not just the contents) to your web server, create or edit a page in Showkase (such as a 'Basic' page) and paste the baseURL embedding code into the text editor section of the page (in 'Source' mode).
It does not matter where on your web server you upload your gallery folder to as long as you know where it is and that the paths within the embedding code (the path to the JavaScript file and the baseURL itself) are correct.

868

(3 replies, posted in Showkase Support)

Showkase v1.0.3 was recently released but this was mainly a bugfix release and no new features were added.
Please see the Version History for details.
Unfortunately, I have no news as to when 'sorting by file name' might be implemented.
Workarounds might be to use Flickr as a source of images for your Juicebox galleries and then use Flickr's 'Organize' options to reorder your images.
Otherwise, you could (as you suggest in your first post) create a gallery using JuiceboxBuilder (ordering your images as required on the 'Images' tab), upload it to your web server and embed it in a Showkase page following the embedding instructions here.

When adding a watermark, JuiceboxBuilder must process the image (to embed the watermark in the image).
The image will not be resized unless the 'Resize Images' checkbox is selected but the specified 'Quality' setting will be used when processing the image for resizing or watermarking.
On the 'Images' tab, click the 'Change...' button in the 'Image Size' control panel and increase the 'Quality' setting from its default value (maximum value is 99).

870

(1 replies, posted in Showkase Support)

Try adding the following code to your 'showkase/_themes/theme_name/css/custom.css' file:

section.content table, section.content table td {
    border: none;
}

871

(3 replies, posted in Showkase Support)

Please install and run the Showkase Server Compatibility Test to check that your client's server has all the features Showkase needs. The Showkase Server Compatibility Test can be downloaded from here.
It looks like the line that the error message refers to relies on the DOM XML parser extension being installed in your PHP installation. The 'Basic tests' (on the first tab of the Showkase Server Compatibility Test) should pick this up and let you know whether XML DOM functions are available or not.

872

(1 replies, posted in Showkase Support)

The embedding code you would need to use to embed a Vimeo video in a web page can be found here.
You can insert this code into a Showkase page (such as a 'Basic' page) by pasting the code into the text editor after clicking the 'Source' button on the toolbar (to tell the text editor that you are entering HTML code and not just plain text).

873

(5 replies, posted in Showkase Support)

The setting within Showkase is a global setting and applies to all pages within the theme.
You could, however, modify the generated pages individually. For example, if you had a Juicebox Gallery Page named 'Gallery', then you would edit the 'showkase/gallery/index.html' file.

874

(7 replies, posted in Showkase Support)

If using the Boma theme, try adding the following to the '_themes/boma/css/custom.css' file:

p,ul,ol,h1,h2,h3,h4,h5,h6 {
    max-width: 540px;
}

... changing the 'max-width' value as appropriate (although this will affect more than just the 'About' page).

If using the Kosel theme, try adding the following to the '_themes/kosel/css/custom.css' file:

div.profile {
    max-width: 560px;
}

... changing the 'max-width' value as appropriate.

875

(4 replies, posted in Showkase Support)

Rather than extract the 'showkase-pro.zip' file to your hard drive and upload the unzipped archive to your web server, try uploading the zip file directly to your web server. Then login to your hosting account's CPanel (through a browser interface) and try unzipping the file on your web server using the 'Extract' functionality of your CPanel's file manager.