Search options (Page 16 of 38)

I'm glad my suggested workaround works for you.
Thank you for letting me know.

No problem at all.
I appreciate you posting the link, though. I would never have found the source of the problem without seeing your gallery's configuration options. Thank you.

Please post the URL to your gallery's web page so that I can take a look and hopefully help further.

Please also let me know the following.
What version of iOS do you use?
What browser(s) do you see the problem in (Mobile Chrome, Mobile Firefox, Mobile Safari)?
What Showkase theme do you use (Boma, Kosel, Maribo)?
Are you referring to the Splash Page on the Juicebox Gallery Page or the expanded gallery (after clicking the Splash Page)?
Thank you.

I have been unable to replicate the problem myself so hopefully with some additional information and being able to see your own gallery for myself, I should hopefully be able to help further.

In the meantime, if you are currently viewing your Juicebox gallery over a 3G or 4G connection, please try using a wfi connection instead. This may or may not be relevant but it cannot do any harm. Perhaps this Juicebox FAQ will help:
Why can't I view my gallery on a 3G mobile connection?

Checking your website with Google's own PageSpeed Insights tool reveals the render-blocking JavaScript and CSS being referred to.
They are gallery and theme related external JavaScript and CSS files which are necessary for the functionality and styling of the content above-the-fold. (In a typical Showkase page, pretty much everything is above-the-fold.)

Suggestions to defer or asynchronously load them might not help much as your above-the-fold content would not look the way it should until the files are fully loaded anyway and there is not a great deal of code on a typical Showkase page that the render-blocking elements would be holding up.

If you like, you could certainly try deferring the loading of the theme related JavaScript files.
Open the showkase/_themes/base/pagetypes/basetheme.tpl file in a plain text editor and add the defer attribute to all <script> tags between lines 33 and 44 (the 'scriptlinks' section). Please note that the line numbers refer to the current version of Showkase (v1.6.1).
However, please be aware that this is not officially supported or tested and might even break your Showkase pages. (For example, if you defer the loading of the 'juicebox.js' gallery file in a Juicebox gallery page, the gallery will simply not display. The 'juicebox.js' gallery file cannot be deferred or loaded asynchronously. The file needs to have been loaded synchronously before the JavaScript embedding code is executed.)
It is certainly something that you could try, though. It is easy to revert if it does not help.
(Be sure to re-publish your site after making any modifications to source files.)

The other suggestion to inline the code would probably also not help much in real terms and would require the structure of Showkase to be changed significantly.
The render-blocking JavaScript and CSS is mostly theme related and I expect that restructuring Showkase to inline the theme code (rather than have it modular in discrete external files) would make maintaining themes and creating new ones a much more difficult process.

Just for the record, I picked a couple of websites at random (youtube.com and wordpress.org), analyzed them with the test website you quoted and got exactly the same message that you reported. It does not seem to be an not uncommon occurrence.

Incidentally, the test website's own pop-up results page (after clicking 'See what to fix') does not fit within my laptop's screen and I have to press F11 to go fullscreen to see the close button. Even though their own web page passes all their own tests, usability is perhaps more important than ultimate speed (although it would be nice to have both in an ideal world).

I'm glad you've found what you were looking for. Thank you for letting me know.
For reference (and other users reading this thread), the Juicebox-Pro Password Protection support section can be found here.

Setting showDownloadButton="FALSE" will ensure that Juicebox-Pro's Download Button is not displayed on the gallery's own Button Bar.
However, it does not disable core browser functionality (such as Chrome's 'Save page as...' feature).

If a user is determined to download an image and is familiar with the structure of a Juicebox gallery, it is possible to view the source of the web page in a browser, find the URL of the XML file and view this file to find the image URL. There is nothing that can be done to prevent a user from doing this (as the 'View Source' functionality is built into each browser).
Anything you do to try to prevent a user from directly viewing an image will also prevent Juicebox from doing the same.

It is also not possible to prevent users from taking a screenshot of the web page displaying the image.
To deter users from doing so, you might like to watermark your images. You could use JuiceboxBuilder-Pro (the desktop application which comes with Juicebox-Pro) to watermark your images. Please see the Adding Watermarks support section for details.
You could then import the gallery (with watermarked images) into your Showkase site using Showkase's 'Site -> Import' functionality.

It might also be wise to ensure that your images are of a file size suitable for web gallery use but not large enough for other purposes (such as printing).

Setting showDownloadButton="FALSE" and showOpenButton="FALSE", disabling the right-click context menu (by using Juicebox v.1.5.0), watermarking your images and making sure that your images are not too large are probably the best preventative steps you can take and should hopefully deter the casual user from downloading your images.

I'm not exactly sure what you are looking to do.
It sounds like what you are looking to do might not be possible with Showkase but using a Gallery Index Page might be a suitable compromise.

You can group multiple different Gallery Pages under either a Gallery Index Page or another Gallery Page.

If multiple different Gallery Pages are grouped under a Gallery Index Page, then on the Gallery Index Page, each gallery will be represented by a thumbnail image which, when clicked, will open the corresponding gallery.

If multiple different Gallery Pages are grouped under a Gallery Page, then when the top-level Gallery Page is selected, the top-level gallery will be displayed and there will be links to all the other galleries in the navigation menu.

If you are using a Juicebox gallery, please make sure that you are using the latest version (v1.5.0) as right-click protection was introduced in v1.5.0. (Please see the Version History for a full list of changes between versions.)
Please also see this FAQ: How do I allow or prevent users from saving gallery images?
(Also, set showDownloadButton="FALSE" in the 'Button Bar (Pro)' settings section.)

If you purchased Showkase-Pro, you can upgrade to the latest version (v1.6.1) which comes bundled with Juicebox-Pro v1.5.0.
Instructions can be found here.
If you purchased Showkase-Standard and Juicebox-Pro separately, then you can download Juicebox-Pro using your original download link and integrate it into Showkase-Standard following the instructions here.

If you are using a ListViewer gallery, go to 'Override Site Options' in the page settings and make sure that the 'Protect images' checkbox is selected.

If you are using a SimpleViewer gallery, then please see this FAQ: How do I prevent users from saving gallery images?

Be sure to re-publish your site after making any changes.

I hope these suggestions help.

Your SimpleViewer-Pro galleries set floatButtonBar="TRUE". The heights of floating elements are not used when calculating the height for the gallery. (Please see the Resizable Layout section of the SimpleViewer-Pro Layout Guide for a short note on floating elements.)
If you set floatButtonBar="FALSE" (in the 'Button Bar (Pro)' section), then height will be reserved in the gallery for the Button Bar and the Title (to the Button Bar's left) should be fully visible (like in your other galleries).
Alternatively, you could set floatTitle="FALSE" and set a titleHeight if necessary (in the 'Title (Pro)' section). (The default value for floatTitle is TRUE.)

Please see 'Editing Individual Captions' in the Pages section of the Showkase User Guide for details on how to extract IPTC data for use in image captions.
If entering IPTC data via Adobe Lightroom, {iptctitle} corresponds to the Metadata 'Title' field and {iptcdescription} corresponds to the Metadata 'Caption' field. (In Photoshop, {iptctitle} corresponds to the IPTC 'Document Title' field and {iptcdescription} corresponds to the IPTC 'Description' field.)

Are you referring to the 'Email to' field in the admin section?

I'm not exactly sure why the contact form (PHPMailer) would fail to send emails to your own email address.
I used a couple of different (valid) email addresses when I was testing the functionality out on your server (a Gmail address and a Hotmail address) and emails from the contact form were sent to both addresses successfully.

At least we're making some progress and now know that your email address seems to be the cause of the problem.

I don't know if it will help but this forum thread seems to describe your problem:
http://stackoverflow.com/questions/2901 … l-function

Also, the PHPMailer troubleshooting section for the "Could not instantiate mail function." error message might help.
https://github.com/PHPMailer/PHPMailer/ … l-function

You could maybe try the 3rd suggestion in the link above and try using sendmail by opening the 'showkase/admin/plugins/contact/master/contactcore/contact.php' file in a plain text editor and changing line 21 from:

$mailer->isMail();

... to:

$mailer->isSendmail();

The path to the sendmail binary in your 'php.ini' file looks to be OK (the regular default sendmail path) so you should not need to explicitly set it.
Be sure to republish your site after making this modification.
I'm not sure if it will work but it might be worth a try.

Please note that the line number above refers to the current version of Showkase (v1.6.1).

Gallery settings for individual themes are stored in files such as:

showkase/_data/themedata/kosel/juicebox.xml

The _data folder is not part of the Showkase package. It is created when the gallery is setup. As such, it will not be overwritten if/when you upgrade Showkase.

You're welcome.

There are a number of different ways that you can target the 'Message' text area using CSS.
My own suggestion above will target only the 'Message' text area as it uses the element's id (#message) and every id on a web page should be unique.
You can certainly use classes (or input types) to target multiple elements at once (to avoid having to specify individual ids).

Add textarea#message to your CSS selectors:

@media only screen and (min-width: 768px) {
    input[type=text],
    input[type=email],
    textarea#message {
        width: 300px;
        border: 1px solid blue;  
    }
}

I usually use my browser's developer tools (accessible via F12) to determine which classes and ids the custom rules should be applied to.

Just a quick reminder...
As you are using a lot of custom CSS in your theme's 'custom.css' file (which is absolutely fine), be sure to make a backup of this file.
If/when you next upgrade Showkase, your 'custom.css' file will be overwritten with the blank version that comes bundled within Showkase and you'll need to reinstate your custom version after upgrading (or you could remove the blank version from the Showkase core files before upgrading).