Search options (Page 28 of 39)

It can certainly take a long while to delete an entire folder structure via FTP (especially if the folder contains many subfolders and files). If you log into your web hosting account's CPanel and open their online File Manager, you might find that you are able to instantly delete a complete (non-empty) folder without having to wait for each and every file to be deleted individually (as would be done via FTP).

It doers not really matter where you store your galleries for importing (although I would recommend a location outside your Showkase folder). However, setting up a 'temp' folder (where you know the contents can safely be deleted after importing) sounds like a good idea.

For others reading this post and wondering how to update Showkase, please see the Upgrading Showkase support page for details.

When Showkase imports a gallery, it creates its own copy of the gallery folder within the Showkase directory.
As you have discovered, it does not delete the original gallery. Showkase leaves it up to the user to delete the original gallery folder if necessary. (The gallery may be embedded in another web page elsewhere and the user may not want it to be deleted.)

You could certainly embed a Juicebox gallery manually in a 'Basic' Showkase page (using the baseUrl method of embedding documented here) but the gallery would not become a true Showkase Gallery Page and you would not be able to edit the gallery within the Showkase interface. (It would also not be possible to list the gallery in a 'Gallery Index Page'.)

A new folder will be created in the root Showkase directory for each page in a Showkase site.
The names of the folders correspond to the 'Nav Name' entries.
If you create a page with a 'Nav Name' of 'gallery', then a folder with the name 'gallery' will be created.
If you then create another page with the same 'Nav Name' ('gallery'), then a folder with the name 'gallery-2' will be created (to avoid a name clash with the original folder).
If you change the 'Nav Name' of a page, then the name of the original folder corresponding to the page will be changed. A new folder should not be created. This seems to be working OK for myself in a test site (with Showkase-Pro v1.3.5).

If you want to delete a page, I would recommend using Showkase's 'Trash' functionality on the 'Pages' tab rather than manually deleting the page's folder from the root Showkase directory. This will ensure that Showkase knows the page has been deleted (and should not be listed on the 'Pages' tab).
If you like, you should then be able to safely delete the contents of the '_trash' folder.

Essentially, Showkase does not delete imported galleries or trashed pages from a web server. If it much safer to leave original galleries as they are (or to move Showkase pages into the '_trash' folder) than to automatically delete them. Some users may not expect files to be deleted with no method of recovery.

I hope this helps to clarify things.

If you are loading your pages into iframes which have fixed pixel dimensions, then the iframes will not dynamically resize. They will always remain at their fixed dimensions.

You could embed a Juicebox gallery created and managed by Showkase in a non-Showkase page using the baseUrl method of embedding as documented here.
The gallery folder (whose name you will need for the baseUrl) is the name of the gallery page (in your root Showkase directory).

It is not possible to 'embed' a Gallery Index Page into a non-Showkase page. The best you could do is load it into an iframe.
You could perhaps give your iframe percentage dimensions rather then fixed pixel dimensions (via CSS) but its actual size will be dependent on its parent containers. If there is a fixed pixel value anywhere up the chain, then the iframe's size will become fixed (e.g. 100% x 800px = 800px). If you wanted to ensure that your iframe is responsive, you would need to ensure that all containers that the iframe is nested within also have percentage dimensions.
Otherwise, you could use JavaScript to listen for a change in the browser window's size and then assign new dimensions to the iframe on your page. This technique is used to resize the gallery container in the resizable examples here.
You could perhaps view the source of the sample web page in your browser and copy/modify the code to suit your own needs.

It's quite a clever idea to close what would normally be the 'href' attribute with a double-quote at the beginning of the 'Back link URL' and then add an 'onclick' attribute (knowing that Showkase will add a double-quote at the end).
This creates valid HTML code and there is nothing wrong with such a solution.
If using this technique, then I would probably use something like the following:

" onclick="javascript: window.parent.location.href='http://www.example.com/'; return false;

It just tidies up a few things (for example adding a space after the opening double-quote, using lower-case characters for the attribute name and adding return false; at the end so that the 'href' value, which is empty anyway, is ignored).

An alternative solution would be to add a value for the 'href' attribute and then add a 'target' attribute in the same way you add the 'onclick' attribute.
The following should also work:

http://www.example.com/" target="_parent

This might be a little simpler as it does not use any JavaScript.

OK. Thanks for letting me know.
In your web host's online control panel, there is likely to be a 'File Manager' which you can use to change permissions.
Hopefully your web host will be able to help you out further with this. (The control panel interface may differ from web host to web host.)

It looks like your web server may not be set up to automatically open 'index.html' files if they exist in a directory.
It is usual for a user to be able to go to a directory and have the 'index.html' file inside it opened in the browser without explicitly having to add 'index.html' to the URL.
For example, a user should be able to view the http://www.example.com/index.html file by going to just http://www.example.com/.
This does not seem to be happening on your web server. (Only 'index.php' files seem to be accounted for on your web server.)
Try contacting your web host to check that 'index.html' files are included in your DirectoryIndex.
Hopefully this will solve your problem.

First of all, please ensure that you are using the latest version of Showkase (v1.3.4) to ensure that any bugs that were present in previous versions but which have since been fixed are not contributing to your problem.
If necessary, please see the Upgrading Showkase support page for details.

I have just checked that changing the 'Gallery text color' and updating a caption takes effect after clicking 'Update' and 'Publish' and everything seems to be working as expected in my own test Showkase v1.3.4 installation.

After making changes to your Showkase site, try completely clearing your browser's cache before reloading your gallery page to see if this makes a difference.
Your web server may also be caching pages which might introduce a delay before you see the updates that you make to your Showkase site.
If your web server uses Apache, try adding the following line of code to the .htaccess file in your root directory to disable server-side caching.

Header set Cache-Control "max-age=0, private, no-cache, no-store, must-revalidate"

Hopefully ensuring that you are using Showkase v1.3.4, clearing your browser's cache and disabling server-side caching will solve your problem.

The problem with grouping pages under a Navigation Link in the Kosel theme is that, when the link is clicked in the menu, the link's URL is opened (rather than the menu expanding to show the second tier pages).
If your 'paintings', 'sculpture', 'water' and 'ferries' pages are gallery pages, then I would recommend using Gallery Index Pages (rather than Navigation Links) for your 'Art' and 'Photography' top tier pages.

Alternatively, if you like, you could change your theme to Boma ('Site -> Change Theme') and select the 'Show all subnav' checkbox ('Site -> Customize Theme -> Navigation').
This will always display all links to all pages so links to your second tier pages (grouped under Navigation Link pages) will always be visible. (The ability to display all links at all times is available only in the Boma theme where the side menu is better suited to displaying a larger number of menu items at once.)

I'm glad you've been able to resolve your problems.
Thank you for posting back to let me know.

If you are unable to run the Showkase Server Compatibility Test, then the problem might be something as basic as not having PHP installed (or correctly configured) on your web server.

Try contacting your web host to see if they can confirm if you have PHP installed on your hosting account and, if so, which version.

The problem may also be a pathing problem whereby the URL you are entering into your browser's address bar may be incorrect and you are not actually viewing the Showkase Server Compatibility Test or Showkase admin section files at all.
Please double-check that the URLs you are using are correct.

Also, please check to see if you have any rewrite or redirect rules in an .htaccess file on your web server which might be causing your problem.

It might also help if I were able to see the problem for myself so please post the URLs to your Showkase Server Compatibility Test and Showkase site itself and I will take a look and investigate further. Thank you.

If you want to add code to the <head> section of only 'Basic' pages (for example), then you can add a {block "head"} ... {/block} section to the '_themes/base/pagetypes/basic.tpl' file.
For example:

{block "head"}
    <link rel="stylesheet" href="http://mark-friedman.com/assets/css/simplex.css" media="screen" />
    <link rel="stylesheet" href="http://mark-friedman.com/assets/css/form.simple.css" media="screen" />
{/block}