1 Reply by dave

(11 replies, posted in Showkase Support)

Steven,

It may not be said enough that your taking on the job of maintaining the Showkase code to keep it functional is much appreciated.  I have purchased code where support and updates end after a few years.  I've been using Showkase for 9 years and feel that I've already more than gotten my money's worth, especially when compared to some other software providers, not least of which includes a company named Microsoft that regularly stops support for the older versions of the Windows operating system and now even demands that you, not only update to a new version, but also replace all of your existing computers with newer hardware.  I understand the need to update as software standards change, but I don't much care for a company, like Microsoft that exploits the need to update to load your computer with more spyware and shovel an ever increasing pile of reviled advertising in front of your face.

Okay, I feel better now.  Thanks for listening.  :-)

Go to forum: Showkase Support

2 Reply by dave

(11 replies, posted in Showkase Support)

That's great!  It's impressive that you have taken it upon yourself to produce a patch to fix newly discovered issues and keep the code compatible with PHP updates.  On top of that, anyone who uses Showkase can get access to the patch without having to pay for additional support.  That I can still get an update 9 years after I bought the software is phenomenal.

Thanks for all the effort and quick response!

-Dave

Go to forum: Showkase Support

3 Reply by dave

(11 replies, posted in Showkase Support)

It's good to hear you found a way to fix the og coding without having to edit files.  I plan to continue to research whether Google and Bing are really ignoring noscript image data or if I'm doing something else wrong.  In any case, Showkase has worked very well for me for 9 years, so I can't complain even if I can't solve the issue.  It's also hard to argue with Google's reasons for adjusting their crawling algorithms to accommodate new coding standards and malicious threats (if that's what they've done).

Thanks again for your help.

-Dave

Go to forum: Showkase Support

4 Reply by dave

(11 replies, posted in Showkase Support)

Thanks!  That fixed the http issue in the og tags. 

It looks like there's more going on here than I can figure out.  Bing and Google let you view the page source after you do a "Live Test" and in both cases the image info from the SEO block is not there, but it is clearly there when I look at the source in my browser.  I have a Wordpress blog under that same domain and search engines pickup every image and tag from the blog with no problem.   I also have a Piwigo site with images that get picked up by search engines.  I think it's possible search engines have changed their policy to no longer collect image info from inside a noscript block and there might not be a solution if that's the case.

In any case, I do appreciate all the time you put into helping me resolve the http and www issue.  Your support for Showkase has always been topnotch and I appreciate that.

-Dave

Go to forum: Showkase Support

5 Reply by dave

(11 replies, posted in Showkase Support)

Steven, thanks for your detailed response.

You solved part of the issue.  You're absolutely right that the way I sign in determines whether the site includes the www prefix in website address on both the Setup page and in the og:image code.  My keepass entry had the www as well as the http.  I changed it to https and eliminated the www and, while the www issue is solved, the http issue remains on both the Setup page and in the og:image code.  My concern is that, if Google is seeing http instead of https on image links, it may ignore the images.

This is all stems from my inability to get google to pick up any of my new gallery images even after submitting a sitemap and submitting the page URLs directly to the Google search console.  I've been looking for anything that might cause that.  My new galleries were added after changing to the Kosel theme, but I don't know if that has anything to do with the problem.  I have problems getting Google to pick up images in other galleries as well.  Sorry for getting longwinded but I've been struggling with this for a while.  I'm afraid Google has stopped using image info inside a noscript block due to some potential "cloaking" issue.

Article here: https://www.orbitmedia.com/blog/noscript-tag-seo/

Go to forum: Showkase Support

6 Topic by dave

(11 replies, posted in Showkase Support)

Hello.

My website URL is listed as http://www.kruegerphoto.com/KPMain2/ and I'd like to change it to https://kruegerphoto.com/KPMain2/.  I assume this gets set up during the installation (back in 2016) and to change it, I'd have to edit some configuration file. 

The problem is that the "http://www." is used on all the image URLs in the SEO section of the page code sent out to visitors (including search engine crawlers).

Can someone please help me with this?

Thanks,

-Dave

[edit]  Sorry.  This problem apparently only affects the og:image code line.  The image info in the SEO section is relative and doesn't include the website address.  But, I'd still like to fix it because Bing Webmaster flags it as an error.

Go to forum: Showkase Support

7 Reply by dave

(93 replies, posted in Showkase Support)

Please consider adding comments and photo ratings (1-5 stars).

I use Showkase for my higher end work, but I am planning a new site for the lower end work that I had on Flickr.  Now that Flickr has been bought from Yahoo by SmugMug, I will be closing my account there.

I want comments and ratings, so Showkase is out of the question, although it is my preferred choice for photo  hosting software.  Piwigo, Zenphoto, and Coppermine all have comments and ratings. 

Showkase is great as is and I assume this would be a major undertaking, but I just thought I'd share my thoughts on this since it was a factor in my deciding to use a different CMS.

Go to forum: Showkase Support

8 Reply by dave

(3 replies, posted in Showkase Support)

I think I just now figured it out.

I noticed the date of the showkaseconfig.ini was old, so I must have pulled the wrong one when I copied it into the web root directory or maybe I copied it over before I ran the setup again.  Anyway, I copied over the showkaseconfig.ini file again, this one with today's timestamp, and that fixed it.  I just knew it would be because of some dumb mistake I made. 

Anyway, sorry to put you through this.  Obviously, when I was running setup, I wasn't updating the showkase config file in the web root directory, so I wasn't solving the problem.  Also, the original server DOES have the showcaseconfig file in the web root directory, so I was wrong about that as well.

Bottom line is that I am now up and running and apologize again for wasting your time on a rather dumb mistake.

I will update to the latest version after I verify that everything is good.  I do love this software.  It's been very good to me.

My main site will continue to use Showkase, but I am about to create a new gallery site to host the more amateur-ish pictures that I currently have on Flickr (which was just sold to Smug Mug).  I had even run the sktest on it to prep it for Showkase, but then decided I wanted comments and possibly ratings.  From what I gather, that is not a capability that Showkase has.  If I'm wrong on that, please let me know.  Otherwise, thanks again and best wishes going forward.

Go to forum: Showkase Support

9 Topic by dave

(3 replies, posted in Showkase Support)

I just had my webhost move a fucntioning showkase site to a new server and all I get when I browse to the domain is the Showkase login as if it's a new showkase installation (Welcome to your New Showkase Web Site).

Everything works if I browse to the subdirectory (KPMain2) where the showkase software is located: 
(Well, I guess I can't post the link here after all)

The showkase index.php is located in the web root directory, but there was no copy of the showkaseconfig.ini file there so I copied one over per the instructions on the Showkase quick tour under "Showkase Home Page".  That didn't help.  By the way, I don't see a copy the ini file in the original website web root directory either and it worked fine.  There are no other index.xxx files in the web root directory.

The showkaseconfig.ini shows the absolute path correctly for the new server (domain address + /KPMain2).  I checked the site System/Setup menu under showkase and it has the correct path.

I also did a "Repair" under the System/Repairs menu, but that didn't fix the issue, either.

The only issue I see is that, when I did the "Publish", I got a number of errors that say: "Notice: A non well formed numeric value encountered".  I went ahead and published anyway.  The green Publish button is now gray and the pages show up when I browse to them directly.

I have Showkase-Pro 1.6.1 | Build: 2016.06.07.09.32.46, 

The IP address of the website has changed and the name servers have been updated.  When you browse to kruegerphoto.com you will get the new site, not the old one.

Any suggestions would be appreciated.

Go to forum: Showkase Support

10 Reply by dave

(11 replies, posted in Showkase Support)

Thanks for taking the time to help me with this.  I think I figured it out and now I'm embarrassed for not thinking of this.

I have KeePass Helper installed on my browser which modifies the page title to make sure my KeePass password safe recognizes what website I'm visiting so it knows what password to use.  It apparently interferes with the way the favicon displays on the tab.  After I disabled it, the icon displayed correctly.   I installed that app so long ago I forgot about it.

My apologies for dragging you down this rabbit hole.  I was afraid it might turn out to be something stupid like this.

By the way, so far I have been extremely impressed with ShowKase.  It works perfectly for me and I love all the config options.  I also like that it doesn't break whenever there's a Wordpress update like my last web gallery experiment.

Thanks again for your help.

Go to forum: Showkase Support

11 Reply by dave

(11 replies, posted in Showkase Support)

Still not working. 

I can see the icon on the screen (not the tab) when I go to  kruegerphoto.com/favicon.ico
so I know it's there in the root directory. 

I'm not entirely sure this isn't a Firefox issue, but it displays other favicons correctly, including the one from my other site: cityshadows.org

Go to forum: Showkase Support

12 Reply by dave

(11 replies, posted in Showkase Support)

Thank you for the reply Steven.

I found the file and code.  It was just as you described.  I have v1.6.1.
I pasted in the line of code using Notepad++ and dropped the ico file into the web root directory, but it doesn't seem to work.  I also tried dropping the ICO file into the main showcase directory), but that didn't help either.

I'll keep working at it to try and figure out what I'm doing wrong.

{block "stylelinks"}
    <link rel="stylesheet" href="{$ss_themeUrl}/css/styles.css">
    <link rel="stylesheet" href="{$ss_themeUrl}/css/custom.css">
    <link rel="shortcut icon" href="/favicon.ico" type="image/x-icon">
{/block}

Go to forum: Showkase Support

13 Topic by dave

(11 replies, posted in Showkase Support)

I have Showkase installed in a subdirectory from the root directory.  Everything works fine, but I'd like to use my old favicon.  I placed it in both the root directory and in the Showkase directory, but it still isn't being picked up.

A forum search gave me one result, but its from 2014 (this forum won't let me post the link) and the file and code don't match my Showkase Pro 1.6.1, so I was hesitant to proceed with any experimentation. 

Can someone please tell me where to put my favicon and what code insertions/changes are necessary to make it work?

Go to forum: Showkase Support