Thanks that worked :)

Note: At first I didn't understand what the heck you meant by "Try republishing your DE and FR sites" but finally figured out that you meant "open a page in the admin area and click the Publish button again." I thought I needed to alter the code using a code editor like Coda on every single page and then re-send them via FTP. This was much easier. Clicking just one page was enough to fix it.

Hmmm, I'm having the same issue on the French and German versions of this site: and

I have cleared the cache and checked several machines. The update was done a couple of days ago.

Huh. Now it's fine. :)

Cache issue, methinks.

I just upgraded ShowKase and everything looks fine except for the navigation menu. It used to display along a horizontal line. It now displays vertically, and pushes everything else down the page. Help!

Same thing with the submenu:


(9 replies, posted in Showkase Support)

I added a separate splash page index.php  (this is the only page of my site that is not the Kosel template, just my own custom HTML and CSS) and added the GoogleAnalytics code on that page:

The Analytics report shows that Google has tracked the inside pages as well. Maybe use this as a workaround?

Note that my Showkase installation and Showkase pages are all one level deeper on the server than the splash page.

I changed the path to /EN/ but got the error message: Site must be in installation folder or a sub-folder

Yes, that's my setup.

IN Admin > System > Setup, I have /~petraluz/EN/

...and that would be where I delete the /~petraluz?

I built my 3-in-1 Showkase site at and now the DNS transfer is complete, so the site can be seen at Great. It's the same server and host, just a difference in the look of the URL.

Except that the nav link URLs look really convoluted (e.g. How do I get rid of the extra "~petraluz" in the URL? This does not appear in the home page for each site ( just the subsequent linked pages.


(11 replies, posted in Showkase Support)

Just learned that German only has an umlaut accent on O, A and U.  The word "Noël" is French.  Go figure.

And of course, we would have this word on one of the main German pages:

This does not negate the need for a full set of diacritics, but it does lower the possibility of it being an issue that crops up in other places on the site in the future.


(11 replies, posted in Showkase Support)

No, it seems to have a problem with the Ë in the body as well:  (see the name of the first gallery).

At first I had the wrong fontkit loaded (French instead of German) and everything was fine except the Ä. Then I loaded the correct German fontkit and the problem switched to the Ë. This makes me suspect that they have carved up the diacritics according to each language for each language kit, rather than include all diacritics. Possibly to increase the speed of the page load. But this backfires when you have an English site that mentions, for example, both French and German authors/books/places/adopted phrases and you need both sets. I wish it was a full font, like the alternative font options in the theme, so that all letters would render properly. That, or replace Bebas Neue with another condensed-bold font that comes with a full set of diacritics.(If I didn't love the contrast of a bold-condensed font with plain ol' sans serif Arial, I'd have just chosen an alternative font from the theme options ages ago and spared myself this hassle. But the theme designer made a strong design choice when setting this as the default look for Kosel, and it really is the best pairing IMHO.)

I read the forum entry above and yes, I have already done that and just re-checked my code and it appears correct. I appreciate your forwarding the issue to the developers. The site is due to go live this week, so fingers crossed they address it asap.


(11 replies, posted in Showkase Support)

New wrinkle.

The font appears to render correctly in the body of the page ( but not in the nav area. See the last button on the nav.
My custom.css file contains:

/* Generated by Font Squirrel ( on January 23, 2013 10:16:30 PM America/New_York */

@font-face {
    font-family: 'BebasNeueRegular';
    src: url('../../../fonts/BebasNeue-webfont.eot');
    src: url('../../../fonts/BebasNeue-webfont.eot?#iefix') format('embedded-opentype'),
         url('../../../fonts/BebasNeue-webfont.woff') format('woff'),
         url('../../../fonts/BebasNeue-webfont.ttf') format('truetype'),
         url('../../../fonts/BebasNeue-webfont.svg#BebasNeueRegular') format('svg');
    font-weight: normal;
    font-style: normal;


header hgroup h1 {
  font-family: 'BebasNeueRegular', Arial, sans-serif;
  font-size: 18px;
  line-height: 1.5;

header hgroup {
  font-family: 'BebasNeueRegular', Arial, sans-serif;


Also, on Windows machines in IE 7 and 8, even after installing the Intnl French version of the font, the French accents are not rendering properly:

Of course it all looks fine on my Mac (Safari 6.0.2, Chrome 24, Firefox 18.0.2). But try explaining that to a client using IE 7 or 8, who are convinced their demographic uses similar.

I think you should replace Bebas Neue. Seriously. It's a default font in Kosel, and the only condensed font option, so it's gonna cause umpteen headaches for anyone else even referencing a foreign text or name within an English site.

As I mentioned above, Google webfonts ( have a couple that are almost identical to Bebas Neue but have full diacritics:

Roboto Condensed Bold (700 weight)

BenchNine Bold (700 weight)


(11 replies, posted in Showkase Support)

Took me awhile to figure out the CSS and directory paths, but I got it sorted in the end.

Success :)

And yes, having a backup was critical.


(9 replies, posted in Showkase Support)

:) Thanks.

Great, thanks. I am going to try the "3 separate sites on one domain server" option.

I'm assuming I need to follow these instructions to move the contents of the first site (English) from the root folder to a sub-directory.


(87 replies, posted in Showkase Support)

Hoping you will add an "insert Google Analytics code here" field to the admin in the future?
For now we have the workaround:


(9 replies, posted in Showkase Support)

Where/how do I add Google Analytics  tracking code in Showkase? Google says to add it just before the closing </head> tag. Is there somewhere in the Showkase admin to do this? If not, do I add it via ftp somehow?  _themes > kosel > js ?

I've read and am wondering if these instructions apply if I'm trying to set up duplicate versions of the same site in 3 languages. Basically, I need an English, French and German version of the same site, with separate galleries and captions in their respective languages. (Client prefers this to the confusion and clutter  of 3 different languages on each page or caption. Even if it means updating 3 versions of the same image caption when updating the site.)

My plan was to keep it simple by creating an index.html ("Choose your language" with links to each of the sites) at the root level. Then a separate folder at the root level for each language (EN, FR, DE), and each of these sub-directories would contain their own copy of the Showcase contents, and their own home page. Is this possible?

Or do I absolutely have to set up one site (e.g. the English version) at the root level, and make the other 2 sub-directories, (as in the live site/dev site examples in your support doc)? If yes, do I have to fill in the Site > Site Settings > title (e.g. French) or is that optional (i.e. just to help avoid confusion while you build and can be removed later by deleting the site title?) I just don't want the word "French" showing up on every page of that section once we launch...
If indeed this is the best way to set up the directories, is there any way to create links in the Site Subhead field (under the logo)? Then I could just make the Site Subhead 2 text links ("Français   |   Deutsch") that point to the subdirectories, and "English  |  French" on the German version, etc, yes? Or would it have to be "English  |  French  | German" on every page of all 3 subdirectories?

Please advise asap.


(11 replies, posted in Showkase Support)

Thanks, will give it a shot.


(11 replies, posted in Showkase Support)

Google webfonts ( have a couple that might be a good substitute for Bebas Neue:

Roboto Condensed Bold (700 weight)

BenchNine Bold (700 weight)


(11 replies, posted in Showkase Support)

Love the Bebas Neue font for Headings.

Unfortunately it does not appear to render letters with diacritics (foreign accents) well. Specifically, French and German text. The font seems to revert to a wider type on letters that have an accent, which looks.... very odd.

I tried using the "insert special character" button in the text style editor. Same result.

I then tried using a different font, and the issue disappeared. Great. But... none of the other options have a bold-condensed-all-caps look, so the titles seem to merge with the body text, rather than stand out, and the impact is diluted down to blah. :(

Is there any way to check to see if that font (or an equivalent) comes with official diacritics? Or add a font color option to the Customize > Theme > Fonts > Headings Font ?


(87 replies, posted in Showkase Support)

Would love the ability to add a selection of languages in smaller-than-the-nav-size text (e.g. english  |  français   |  deutsch) to the header or footer of every page. Or maybe to the subheading area of the logo? (I tried this and small text looks great under the logo, but the Showkase admin interface does not allow links in that field). Then they could even be the standard tiny flag icons with minimal aesthetic impact to the layout. I prize the minimalist look of Kosel and hate to add *anything* but when your clientele is global... you kinda have no choice.

Ideally, clicking these links would point to the same page in a separate folder. i.e. if I'm on the Contact Us page in English ( and I click on the "français" text link, I am taken to the Contactez Nous page (

My current workaround is to use the index page as a "choose your language" intro, and then link from there to the separate language folders. e.g. one directory folder of the entire site in English, one in French, etc. This is okay, but not ideal.