201

(5 replies, posted in Showkase Support)

I'm sorry to hear that my suggestion does not work.
Unfortunately, the code I posted above came straight from the PHPMailer Gmail example here so I'm not sure what else to suggest.

As I mentioned previously, the Contact Form within Showkase requires PHP mail support on the server and this is the only method that is officially supported.

The best thing to do might be to ask your web host if they could enable PHP mail support on your hosting account and you could then use Showkase's Contact Form without modification.

I realise that this is not a direct solution to your problem but it might be the best course of action.

202

(3 replies, posted in Showkase Support)

That's great! Thank you for letting me know.

203

(3 replies, posted in Showkase Support)

i want to up Juicebox Page footer

In a Juicebox gallery page, the body content includes both the body text and the gallery.
Also, in Maribo (the theme you are currently using), the body text appears above the gallery.
If you want to swap the positions of the body text and the gallery and insert the footer between the body text and the gallery, then this would probably involve modification to several Showkase source files.

I want to delete body content only in a specific gallery

This would me much easier to achieve than swapping the position of the blocks (and sections within blocks).
The easiest way to do this would be to edit the page in question and clear the 'Page title' and the editor's input text area.
If you really want to remove the 'page-body' container from a specific page, then please try the following:

(1) Find the number of the page in question. View the page's source in a browser, scroll down to the opening <body> tag and you'll find something like this:

<body class="light type-juicebox page-7 group-0  body-open-sans headings-open-sans ">

(The page number in this example is 7.)

(2) In your theme's 'custom.js' file (for example, in Maribo, use '_themes/maribo/js/custom.js'), add the following code:

$('.page-7 .page-title').remove(); // To delete the page title only

... or:

$('.page-7 .body-content').remove(); // To delete the body text only

... or:

$('.page-7 .page-body').remove(); // To delete the page title and the body text

... changing the page number as necessary.
(There is no need to republish your site after modifying a 'custom.js' file but you may need to clear your browser's cache before reloading your page.)

The top, gallery, and footer layouts on mobile are incorrect

Your site's Juicebox gallery page looks OK to me in Mobile Safari on my iPod Touch 6 (iOS 12.1).
Please let me know what you see and what you expect to see and maybe I can help further.

204

(3 replies, posted in Showkase Support)

You're welcome!

205

(3 replies, posted in Showkase Support)

I have enabled the three images sizes and Use full screen expand, but it always show the menus at the top and the bottom.

All Showkase pages (under the Boma, Kosel and Maribo themes) always show the navigation menu.
This is by design (so that visitors can easily navigate throughout the site).

The only way to have a full-page gallery within Showkase is to use the Gallery Manager theme.
However, the Gallery Manager theme supports only Juicebox and ListViewer Gallery pages (not About, Basic or Contact pages) and does not display the navigation menu on any pages.

If you really want to have a full-page gallery within your website, you could perhaps set up two separate Showkase sites (one using the Kosel theme and the other using the Gallery Manager theme). Next, create a Juicebox gallery page in the Gallery Manager site and then use a Navigation Link page type within the Kosel site to link directly to the Juicebox gallery page in the Gallery Manager site. You could include a Back Button in your Juicebox gallery to allow visitors to seamlessly return to a chosen page within your Kosel site.

Please note that the imageScaleMode configuration option (in the Main Image section) in the Multi-Size demo gallery is set to FILL so that the images always fill the gallery's image area no matter the size or shape of the user's browser window. (Cropping will occur if the aspect ratio of the image does not match that of the browser viewport.)

I also noticed that I cannot seem to cascade Gallery index pages.

Showkase supports only two levels in its menu system. Gallery Index pages are always top level pages and the Gallery pages listed on a Gallery Index page are always second level pages.
Unfortunately, it is not possible to nest Gallery Index pages under other Gallery Index pages.

206

(4 replies, posted in Showkase Support)

The bug noted above (regarding a PHP memory_limit value of -1) has now been fixed in Showkase v1.7.4 which has just been released.
Please see the Version History page for a full list of changes between versions. (The Version History page will be updated very soon in the next website refresh.)
Full instructions for downloading the latest version and upgrading a Showkase site can be found in the Upgrading Showkase support page.

Upgrades are free within the same major version number so if you purchased Showkase v1.0.0 (for example), then you can download all v1.x.x releases at no further cost.
Download links always point towards the most recent version that you are entitled to (rather than the version you purchased), so you can use your original download link from your purchase email to download the latest version.

Upgrading a Showkase site should be a quick and easy process (instructions in the link above) but please be sure to make a full backup of your site first, just in case anything goes wrong and you need to reinstate your original files at a later date.

207

(5 replies, posted in Showkase Support)

The bug noted above (regarding a PHP memory_limit value of -1) has now been fixed in Showkase v1.7.4 which has just been released.
Please see the Version History page for a full list of changes between versions. (The Version History page will be updated very soon in the next website refresh.)
Full instructions for downloading the latest version and upgrading a Showkase site can be found in the Upgrading Showkase support page.

Upgrades are free within the same major version number so if you purchased Showkase v1.0.0 (for example), then you can download all v1.x.x releases at no further cost.
Download links always point towards the most recent version that you are entitled to (rather than the version you purchased), so you can use your original download link from your purchase email to download the latest version.

Upgrading a Showkase site should be a quick and easy process (instructions in the link above) but please be sure to make a full backup of your site first, just in case anything goes wrong and you need to reinstate your original files at a later date.

208

(4 replies, posted in Showkase Support)

The bug noted above (the Juicebox version number not displaying in 'Site -> Customize Viewers') has now been fixed in Showkase v1.7.4 which has just been released.
Please see the Version History page for a full list of changes between versions. (The Version History page will be updated very soon in the next website refresh.)
Full instructions for downloading the latest version and upgrading a Showkase site can be found in the Upgrading Showkase support page.

Upgrades are free within the same major version number so if you purchased Showkase v1.0.0 (for example), then you can download all v1.x.x releases at no further cost.
Download links always point towards the most recent version that you are entitled to (rather than the version you purchased), so you can use your original download link from your purchase email to download the latest version.

Upgrading a Showkase site should be a quick and easy process (instructions in the link above) but please be sure to make a full backup of your site first, just in case anything goes wrong and you need to reinstate your original files at a later date.

209

(3 replies, posted in Showkase Support)

I'm sorry to hear that my suggestions did not help.

Showkase should work fine out-of-the box on most web servers but it sounds like there may be something unique to your own web server which is causing your problem.
It sounds like there may be a problem storing PHP session variables but the Showkase Server Compatibility Test should pick this up.

I'd be happy to help further but I'd really need access to your web server and Showkase site in order to investigate further.
If you are agreeable to this, then please email me your FTP login details (host, username and password) and Showkase login details (URL, username and password). (I have sent you an email. Please check your messages.)
I'll not change or delete any existing files on your web server but I'll need access to upload a test Showkase site (which I'll delete after I have completed my tests), check the functionality of your own Showkase site (so that I can see the problem for myself) and also check your web hosting account's PHP settings (in case they are somehow relevant to the problem).
Thank you.

210

(3 replies, posted in Showkase Support)

I've not encountered such a problem before so, unfortunately, I do not know what might be causing it.
However, here are a few things to check and try which might help.

(1) Change your password
Try changing your Showkase login password by following the procedure noted in the FAQ below.
I lost my password, how can I reset it?

(2) Upgrade (or reinstall) Showkase
If you are not already using the latest version of Showkase (v1.7.3), then try upgrading following the Upgrading Showkase instructions.
Even if you are already using the latest version, try reinstalling it to ensure that all core Showkase files are present and correct on your web server.

(3) Run the Showkase Server Compatibility Test
Try running the Showkase Server Compatibility Test.
Even if you ran the test before initially installing Showkase, please try again in case your web host has made any changes recently and any of the tests currently fail.
The results of the tests may point us in the right direction.
There are troubleshooting tips for any test fails that you may encounter on the test's support page.

(4) Run Showkase in debug mode
Try running Showkase in debug mode to see if any error messages or warnings are displayed in the application's status bar which might help to pinpoint the cause of the problem.
Open your 'showkase/admin/settings/constants.php' file in a plain text editor and change line 12 from:

define('DEBUG', false);

... to:

define('DEBUG', true);

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

(5) Check in with your web host
If the problem has only started to happen recently and you have not changed anything yourself, then this suggests that something might have changed on your web server.
Please ask your web host to see if they have made any changes recently which might be affecting your hosting account (and, subsequently, Showkase's functionality).

I hope these suggestions help.
Please let me know how you get on and if I can be of any further assistance.

couldn't access to it "Not Found The requested document was not found on this server."

(1) First of all, please check that the 'admin/index.php' file is present on your web server. It sounds like the file might not be there.

(2) Next, check the permissions of the 'admin/index.php' file (and the permissions of the 'admin' folder and all other parent folders). Default permissions of 644 for files and 755 for folders should be fine. You should be able to check and change file and folder permissions using an FTP program such as Filezilla or via your web hosting account's online control panel.

(3) Try visiting your admin section by going to 'admin/index.php' (stating the index page's filename) instead of just 'admin/' in case your web server is not set up to find and go to the 'index.php' file automatically.

but i didnt changed something .

(1) If things were working fine and you did not change anything yourself but things are no longer working as they should, then this suggests that something may have changed on your web server.
Please ask your web host if they have made any changes to your hosting account recently which might somehow be contributing to your problem. Maybe they have changed some PHP settings or the PHP version.

(2) Also, please try installing and running the Showkase Server Compatibility Test.
Even if you ran the test before initially installing Showkase, please try again in case your web host has made any changes recently and any of the tests currently fail.
The results of the tests may point us in the right direction.

(3) Try upgrading to the current version of Showkase (v1.7.3) to see if this helps.
I have sent you a new download link for your Showkase purchase.
For reference, instructions for Upgrading Showkase can be found here.

Hopefully my notes above will help to resolve your problem (or at least point us in the right direction).
Please let me know how you get on and if I can be of any further assistance.

212

(5 replies, posted in Showkase Support)

@Sake

The developers are working on a  new version at the moment but, unfortunately, I do not know when it will be released.
In the meantime, I would certainly recommend upgrading to v1.7.3 as this version features significantly faster publishing times (especially for sites with a large number of galleries).

For example, I created a test site in Showkase v1.7.3 with 128 galleries.
The initial publishing of the site took approximately 60 seconds. Subsequent publishing took approximately 5 seconds.
Please note that if you change the theme or the value for 'Customize Theme -> Gallery Index Page -> Thumb percent height', then thumbnails will need to be recreated and the publishing time will increase but, as long as thumbnails do not need to be recreated, publishing will be noticeably quicker.

This is not a strict benchmark (and actual publishing times will depend on many factors such as your web server) but my own findings should hopeful give you an idea of what to expect.

Incidentally, the bug noted above was fixed in a recent update to the Showkase v1.7.3 zip file so if you update to v1.7.3 just now, you will not need to manually implement the bugfix.
The bugfix was just a single line change in a single file so only the build number changed (to "2018.03.29.09.24.33" for Showkase-Standard and "2018.03.29.09.24.34" for Showkase-Pro).

213

(4 replies, posted in Showkase Support)

I'm glad you've got things working again until the official fix in the next version.
Thank you for letting me know.

214

(3 replies, posted in Showkase Support)

You're welcome!

215

(3 replies, posted in Showkase Support)

The code that sets the widths of the contact form input fields in the Kosel theme can be found on line 611 of the '_themes/kosel/css/styles.css' file:

@media only screen and (min-width: 768px) {
  input[type=text],
  input[type=email] {
    width: 200px;
  }
  textarea {
    width: 700px;
  }
}

You can either change the values there or override the values by adding the code below (with your own values) to your '_themes/kosel/css/custom.css' file, e.g.:

@media only screen and (min-width: 768px) {
  input[type=text] {
    width: 300px;
  }
  input[type=email] {
    width: 400px;
  }
  textarea {
    width: 700px;
  }
}

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

I hope this helps.

216

(4 replies, posted in Showkase Support)

It certainly sounds like the -1 memory_limit issue noted in this thread.

If the problem just happened suddenly without you changing anything yourself, then it is very likely that something changed on your web server.
Please check in with your web host and ask them if they have changed anything on your hosting account recently and, if so, what.

Also, please confirm what your PHP memory_limit is currently set to.
Better still, if you could post the link to a phpinfo() file so that I can take a look at your PHP settings, that your would great, thanks.

  • Create a new file in a plain text editor with the following code: <?php phpinfo(); ?>

  • Save the file with a .php file extension (for example, 'phpinfo.php').

  • Upload the file to your web server.

  • Copy the URL to the file in a post below..

When implementing the workaround I posted in the other thread (link above), please make sure that lines 25 to 27 inclusive of the 'admin/classes/thumbnail.php' file are exactly as follows:

$memoryLimit = (ini_get('memory_limit') == '')
    ? MEMORY_LIMIT_FALLBACK
    : '1024M';

Hopefully my notes above will point us in the right direction and be a step closer to solving your problem.
If the problem persists, I would be more than happy to investigate further but it would help if I had access to your web server. If this proves to be necessary and you are agreeable, then I'll send you an email address where you can forward to me your FTP login credentials. Thank you.

217

(5 replies, posted in Showkase Support)

@nuvisions

Thank you very much for allowing me access to your web server.
It was very helpful in confirming the bug.

------------------------------------------------------------------------------------------------

Just a quick follow up for anyone following this thread...

The problem was, indeed, caused by a PHP memory_limit of -1.

The memory_limit of 128M in the user's case above was for the root directory only (not inherited by subdirectories) and the memory_limit for the Showkase site's 'admin' directory (and all its subdirectories) was reported as -1.

This bug will be fixed in the next version of Showkase and the workaround I posted above (to modify the 'thumbnail.php' file) should work fine as a temporary measure for anyone experiencing similar symptoms.

218

(5 replies, posted in Showkase Support)

You're welcome!

I'm glad to hear that my suggestion worked, although I'm a little surprised as I expected to see "-1" instead of "128M" as your memory_limit.
As your memory_limit is already set to an actual value ("128M"), Showkase should read this value and continue as normal (unless your web server is not reporting the memory_limit correctly). It is only if Showkase encounters a memory_limit of "-1" that a problem can occur. (Incidentally, if your memory_limit was not high enough, you would see error messages in Showkase's status bar.)
I'm glad your Showkase site is back up and running but as the problem is not exactly as I expected, I cannot be sure that the new version of Showkase (when it is released) will actually solve your problem.

I would be happy to investigate further but it would help if I had access to both your Showkase site and your web server to check things out and run some tests. If you are agreeable to this, then please email me (you have my email address) with your Showkase site login details (login page URL, username, password) and FTP login details (host, username and password) and I'll hopefully find the exact cause of the problem. (I will not change or delete any existing files on you web server and I will leave everything as I find it.)

It would certainly help us to determine the exact nature of your problem and might help us to formulate a bugfix for the next version of Showkase. Thank you.

However, as everything seems to be working OK at the moment (with the workaround in place), if you would rather just leave things as they are and wait until the next version of Showkase (when it is released) to see if this fixes the problem, then I understand and that is perfectly fine.

219

(5 replies, posted in Showkase Support)

Thank you for running Showkase in debug mode and for trying the Showkase Server Compatibility Test.
They are usually the two most helpful things when trying to troubleshooting a problem.

The following is just a hunch but it may help.

Please check the PHP memory_limit value on your web server.
You should be able to check your PHP settings using phpinfo() as follows:

  • Create a new file in a plain text editor with the following code: <?php phpinfo(); ?>

  • Save the file with a .php file extension (for example, 'phpinfo.php').

  • Upload the file to your web server and open it in a browser.

If memory_limit is set to -1 (to assign no memory limit) rather than an actual value, then this is likely to be the cause of your problem.

Showkase is not currently set up to handle such a memory_limit value and this prevents thumbnails from being generated. (I have seen this only once before it could be the cause of your problem.)

The developers are aware of this issue and it will be fixed in the next version of Showkase.
In the meantime, a workaround is to hard-code a suitable $memoryLimit value into Showkase's source code.
Open the 'admin/classes/thumbnail.php' file in a plain text editor and change line 27 from:

: ini_get('memory_limit');

to:

: '1024M';

After making this change, please republish your Showkase site (just click the 'Publish' button).
Please note that the line number above refers to the current version of Showkase (v1.7.3).

Hopefully this will solve your problem.
Please let me know how you get on and if I can be of any further assistance.

220

(3 replies, posted in Showkase Support)

No problem!
I'm glad my suggestion worked for you. Thank for you letting me know!

221

(3 replies, posted in Showkase Support)

Try adding the following CSS to your site's '_themes/kosel/css/custom.css' file (changing the actual font-size value as necessary).

.type-galleryindex .thumbs figcaption a {
    font-size: 24px;
}

This should change the font-size for the Gallery Index Page thumbnail text.

If you have a lot of text to display and find that it is being truncated (and not all displayed), then you might like to try using the following CSS instead (which will leave more room between rows of thumbnails for text to wrap).

.type-galleryindex .thumbs figcaption {
    font-size: 24px;
}

There is no need to re-publish your site after making this change but you might need to clear your browser's cache before reloading your Gallery Index Page in order to see this change.

You're welcome! I'm glad it turned out to be an easy fix.

Thank you for providing the links.

I have downloaded your image and notice that the white area surrounding the picture is actually part of the image file itself (and is not originating from Showkase).
Open the image in an imaging program (such as Adobe Photoshop), crop the image to remove the white area surrounding the picture and then reupload the image file to Showkase.

This should solve your problem.

Unfortunately, I have been unable to reproduce the problem that you describe so I'm not sure what might be causing your problem.

  • I installed a fresh Showkase v1.7.3 site.

  • I changed the theme to Kosel.

  • I changed the 'Max site width (px)' to '1000'.

  • I changed the 'Overall color scheme' to 'custom'.

  • I changed the 'Background color' to '808080'.

  • I created a 'Basic' page.

The entire background of the page I created (the body content and the surrounding area) is #808080.

Here are a few things to check and try.

(1) If you are not already using the latest version of Showkase (v1.7.3), then please try upgrading your site to ensure that any bugs from previous versions which have since been fixed are not contributing to your problem.
Full instructions for downloading the latest version and upgrading an existing site can be found on the Upgrading Showkase support page.

(2) Try clearing your browser's cache before reloading your site to make sure that your browser is using the most recent versions of all your site's files from your web server (and not any cached versions).

(3) Check to see if you have any custom CSS (perhaps in your theme's 'custom.css' file) which might be conflicting with Showkase's own CSS and overriding the background color set in the interface.

I hope that these suggestions help.
If not, then please post back with the URL to one of your web pages which demonstrates this problem so that I can see the problem for myself and hopefully help further.
Thank you.

225

(1 replies, posted in Showkase Support)

Unfortunately, Juicebox-Pro's direct download functionality does not work on iOS devices so Juicebox-Pro automatically hides the Download Button when an iOS device has been detected. (The Direct Download button should display and function fine on Android devices, though.)
As you have discovered, the best alternative for iOS users would be to include the Open Image button so that they can open the image in a new windows and download the image from there (using Mobile Safari's native 'Save Image' functionality).