Search options (Page 28 of 39)

I've moved your query to a new forum thread to keep each case separate. You may have similar symptoms to another user but the solution may be different. (The original poster's solution was to remove an 'open_basedir' restriction and turn off Safe Mode.)

There are too many PHP directives to list individually but the Showkase Server Compatibility Test should flag any problems which should be addressed.

Showkase was designed with the idea that galleries would be created and edited within the Showkase interface. The import functionality was added as a convenience for users who already had existing Juicebox galleries and did not want to have to recreate them all from scratch.
If you want to add images to an existing gallery which has been imported into Showkase, just edit the gallery page in question, go to the 'Upload' tab and upload your additional images.

I do not see a Back Button in the gallery whose link you provided. (Perhaps you have changed the gallery since I have had a chance to look.)

I can't imagine that a Back Button would have been present in a Juicebox gallery without some Back Button configuration options being set. However, I would really need to see the problem for myself to be able to troubleshoot it further.

Just for the record, I've installed Showkase on several different web servers (each with a slightly different configuration, no doubt), but I've never had to change any permissions to get Showkase to work.
I do not know why you may need permissions of 777 on your own web server but if this is the only thing that works, then you might need to keep them. More information on file permissions within Showkase can be found here.

It sounds like the problem may be to do with caching. Try completely clearing your browser's cache before reloading your web site to see if this helps.

If you continue to experience difficulties, then we should perhaps try to tackle each issue individually.

First of all, with permissions set to 777 (which seems to work on your web server), make sure that all tests in the Showkase Server Compatibility Test pass OK. If any tests still fail, then they should be looked into further.

Also, if you still have a gallery which still displays a Back Button, please post the URL so that I can take a look at the configuration options from my end (using a browser that has never visited your web site) to see if any Back Button settings are being used.

[Query moved to new thread to keep each case separate.]

You might like to take a look at this forum thread, entitled "How to get an IFrame to be responsive in iOS Safari?". It might help with your problem. http://stackoverflow.com/questions/2308 … ios-safari
If you need to add any custom CSS to your Showkase web pages, you can add it to the '_themes/theme_name/css/custom.css' file as noted here.

That's great!
Thanks for letting me know.

With Facebook, it is not possible to pass individual thumbnail images via their share URL.
Facebook takes all the information to populate the pop-up share window from Open Graph tags in the web page: http://ogp.me/
It uses the og:image for the image and the og:title and og:description for the text.
(Showkase automatically includes Open Graph tags in pages.)

I've not personally tried ShareThis but perhaps other users have...

You need to click on 'Source' (to enter 'Source' mode) before entering your any HTML code (not afterwards).

Whatever software you use to create your virtual tour, please check with their support to see if they have any information on how to embed their virtual tours into web pages.

If you are trying to add the code <embed src="index.html"> to your Showkase page, then I expect the virtual tour is somehow embedded into the 'index.html' file. You could open the 'index.html' file in a plain text editor and examine the code. If you find the code which embeds the virtual tour into the web page, you could copy it into your Showkase page (being sure to click 'Source' first). If the virtual tour comprises many files, then you may need to ensure that they are uploaded to the correct location on your web server and that the paths in the code you use are correct.

Otherwise, you could certainly load the 'index.html' file into an iframe by using code such as:

<iframe src="index.html" width="800" height="600" frameborder="0" scrolling="no"></iframe>

I hope this helps.

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.