• Registered: 2019-07-14
  • Posts: 7

Topic: Showkase favicon issue

The website is lesmithart.com


I previously had implemented this website using Showkase, but since have built it from scratch using HTML and CSS. I believe all of the old files for the site have been removed.

However, on all of the pages of this site, the Showkase favicon shows up and that does not seem to be a great idea. I have tried to remove it using all of the techniques I could glean from searches on the web, but it still persists. It also shows up on other computers unassociated with me, so it is not my computer, probably not the browser, but how to get rid of it?

This site does have some pages using image galleries produced using  Juicebox builder pro. And on another site, I have used Showkase so the folder is in the file system in the host at cabrackett.com.

Your thoughts please.
Thanks

  • Registered: 2019-07-14
  • Posts: 7

Re: Showkase favicon issue

I think I have found the solution, but just maybe:

I found a Showkase folder in the lesmith.com directory on the host, and within it was the favicon.ico file. I changed its name but left it there. Subsequently, the Chrome browser no longer seems to have the favicon showing.

On the other hand, it still shows on a Firefox browser.

  • Registered: 2012-12-16
  • Posts: 984

Re: Showkase favicon issue

I've viewed both your sites (https://cabrackett.com/ and https://lesmithart.com/) in Chrome, Edge and Firefox and neither site has any favicon at all in any browser (at least for myself just now).

It's possible there was some server-side caching going on (which was still serving the Showkase favicon even after the file was renamed) which has since expired.

For reference, the Showkase favicon is, by default, named 'favicon.ico' and is located directly in the Showkase root directory. There is another 'favicon.ico' file in this location: showkase/admin/img/favicon.ico.

With regard to your own Firefox browser, even though the server-side caching may have expired (if it was ever present), it might be worth clearing your browser's cache in case there is some client-side caching going on, too.