Search options (Page 26 of 38)

If you hardcode the 'www' subdomain in the path, then your gallery might work only when visitors go to www.boxofbirds.kiwi.nz and not boxofbirds.kiwi.nz. The code I posted (with the leading slash to denote your root directory) should work for both addresses.

I have just viewed your gallery and the icons seem to display fine.
I'm not sure if you have solved your problem or if you are still experiencing difficulties but if you still cannot see the icons, then try clearing your browser's cache before reloading your web page to see if this helps.

Also, please bear in mind that the icons are characters in a custom font so make sure that you do not have any global CSS rules which might set a font-family for everything on your page and which might override the gallery's own font. It is not possible to isolate a Juicebox gallery (or any other element on a web page) from global CSS rules and Juicebox will have no option but to inherit such rules. If you do find such a global font-family CSS rule, then try applying it to only those elements on your web page which require them through use of ids and classes.
(This is perhaps one good thing about using an iframe: it isolates the gallery from all other code on the web page that it is loaded into.)

Thank you for providing the URL to your web page. I now see the problem.
Your gallery does have a transparent background but the background color of the page that the gallery is embedded into (the Showkase page that you load into your iframe) has a background color of #222222.
You will need to make the background of the Showkase gallery page transparent, too.

Open the '_themes/manager/css/custom.css' file in a plain text editor and add the following code:

body, html {
    background-color: transparent !important;
}

Alternatively, instead of using an iframe, you could embed the gallery directly into your web page using the baseUrl method as documented here (and set the gallery's background to be transparent in the embedding code).

Just replace your iframe code with the following:

<!--START JUICEBOX EMBED-->
<script src="/showkase/gallery/jbcore/juicebox.js"></script>
<script>
  new juicebox({
    baseUrl : '/showkase/gallery/',
    containerId : 'juicebox-container',
    galleryWidth : '100%',
    galleryHeight : '800',
    backgroundColor: 'rgba(0,0,0,0)'
  });
  </script>
<div id="juicebox-container"></div>
<!--END JUICEBOX EMBED-->

This has none of the drawbacks that using an iframe has (please see here for details) and avoids the need to add any custom CSS to your Showkase pages.

First of all, you will need to set the gallery's 'Gallery background color opacity' to 0 (to set the background to be fully transparent) in the Juicebox page's 'Gallery Lite Options' section.

Then, for Internet Explorer, you may also need to use the allowtransparency="true" attribute in your iframe as follows:

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

Try increasing the captionHeight (in the 'Caption' section) from its current value to 40 to something large enough to accommodate your three lines of text. (The default value for captionHeight is 120.)
This should hopefully solve your problem.

You could push your SimpleViewer galleries down SimpleViewer Gallery Pages by editing the '_themes/base/pagetypes/simpleviewer.tpl' file in a plain text editor and adding a few HTML line breaks <br /> at the start of the {block "content"} section. Alternatively, you could add custom content instead of using <br /> tags.
Please note that this will apply to all SimpleViewer Gallery Pages within your Showkase site.
Also, after pushing the galleries down your pages, you might want to decrease the height of the galleries (so that users do not need to scroll down the pages to see the bottom of the galleries). You can do this in the Showkase interface by editing a SimpleViewer Gallery Page, scrolling down to the 'Override Theme Settings' section and entering a negative number (such as -200) for 'External fit px'. (Then click 'Update' and 'Publish').

Have you tried just using a 100% x 100% iframe such as the following?

<iframe src="index.html" style="width: 100%; height: 100%;" frameborder="0" scrolling="no"></iframe>

It might be worth trying.

Another thing you might like to try is to use JavaScript to listen for a change in the user's browser window size and then assign new dimensions to your iframe accordingly.
There are examples of this technique in the Using a Resizable Gallery with a Header support section. In the online examples, JavaScript is used to dynamically set the gallery's dimensions. You could copy and modify the code as required to set your iframe's dimensions instead.

As noted in the short description for enableKeyboardControls in the Config Options page:

Having said that, you might like to try the following suggestion.
Open the '_themes/kosel/js/custom.js' file in a plain text editor and add the following code:

jb.onInitComplete = function() {
    $('#juicebox-container').find(':first-child').focus();
};

The code uses jQuery but Showkase already loads jQuery into web pages so there is no need to manually add jQuery to your site.
The code also relies on the juicebox object having been assigned the variable name 'jb'. This is already the case for all Juicebox galleries created within or inported into Showkase. However, if you embed your gallery manually, you will need to ensure that you use var jb = new juicebox({ instead of just new juicebox({.

The key to your other problem is to always leave the gallery's height at 100% in the embedding code. (Under normal circumstances, there should be no need to manually edit an HTML page created by Showkase.)
Showkase has its own gallery fitting routine to best display the gallery on the page (and always sets a gallery's height to be 100% when you create or import a gallery within the Showkase interface).
Showkase pages are responsive and change depending on the size of the user's browser window.
Manually setting a fixed height for a gallery by editing an HTML page directly is going to cause problems. (Showkase has no knowledge of any manual editing you may do and expects the height to be 100%.)

With default settings, the bottom of a gallery will rest on the bottom of the browser window (no matter what the height of the browser window is) and the user can vertically scroll down to see the page's footer below the gallery.
If you want to increase the height of your gallery, edit your Juicebox gallery page in Showkase, scroll down to the 'Override Theme Settings' section and entering a positive number for 'External fit px'. (Be sure to click 'Update' and 'Publish' afterwards.)

First of all, it looks like you might need to increase the maxCaptionHeight (from its current value of 20) to allow the whole caption to be displayed. When captionPosition="BELOW_IMAGE" (as in your gallery), the maxCaptionHeight is used as the actual caption height (rather than a maximum). This is noted in the description of maxCaptionHeight in the Caption Options section of the Config Options page.
If you see too much space above and below the main images in your gallery, then please see this FAQ:
My Juicebox gallery shows too much space above or below the main image, how do I fix this?
Hopefully this will help.

That's great! It sounds like you have found the control you were looking for.

By far the easiest thing to do would be to trash the existing page and import the new version of the gallery making sure that the Nav Order for the new Gallery Page is the same as the old Gallery Page (so that it displays in the same menu order).

I would not recommend this at all. You would have to upload the gallery folder to somewhere on your web server anyway and the importing process does not take long so I would certainly just upload the gallery folder to your 'temp' directory and allow Showkase to import the gallery correctly.

Changing a page name should not have any effect on the images or configuration options listed in a gallery's XML file. It sounds like there may be some server-side caching going on which is causing your problems. (When you revert to an older page name which previously existed, the corresponding older version of your gallery's XML file seems to be used. If you have since modified the gallery, then it sounds like the data must be coming from a cached version somewhere.)
If your web server is caching files, try switching it off to see if this helps.

I cannot replicate this behavior. I created a new Juicebox gallery page, named 'landscape', with a couple of images and a couple of custom settings. The gallery displayed as expected. I then trashed the page and the 'landscape' folder was moved to the '_trash' folder. (The 'landscape' folder no longer existed in the Showkase root directory.)
Next, I created another new Juicebox gallery page, again named 'landscape' with two different images and all default settings. Again, the gallery displayed as expected. Only the two new images were displayed and none of the original gallery's custom settings were used. A new 'landscape' folder was created in the root Showkase directory using none of the original 'landscape' folder's data.
I suspect that what you are seeing is due to some kind of caching (whether server-side or in your browser) so please check into this to see if it might be the cause of your problems.

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.