Yes, this is one of the hazards of "rolling our own!" One of the changes in this version consists of somewhat more selective generation of CSS. For example, why have entries in the CSS file for credits if the user has indicated that he wants to exclude the credits line? The skin, of course, has no idea that you've hijacked the
sa-credits class for your own nefarious purposes.
You're correct that generating all of the CSS yourself is messy, especially when you include things like WOFF fonts or Google fonts.
In looking at the way that's being handled right now, I'll probably make some changes in a future release - what I'm doing is too clever by half.
For now, the quick fix is to open the skin directory and edit the
common.css file. You'll find this buried deep in it:
<ja:if not test="${excludeBacklinks}">.sa-credits {
<ja:if test="<%=isWoff && creditsUseFont.equals("WOFF")%>">font-family: "${woffName}", ${fontStack};</ja:if>
<ja:if test="<%=isGoogleFont && creditsUseFont.equals("Google font")%>">font-family: "${ctGoogleFont}", ${fontStack};</ja:if>
<ja:if test="<%=isGoogleFont2 && creditsUseFont.equals("Google font 2")%>">font-family: "${ctGoogleFont2}", ${fontStack};</ja:if>
font-size: ${creditsFontSize}px;
font-weight: ${creditsFontWeight};
font-style: ${creditsFontStyle};
font-variant: ${creditsFontVariant};
margin: 0px auto 10px;
text-shadow: ${creditsFontShadowString};
}
.sa-credits a {
text-decoration: ${creditsLinkDecoration};
}</ja:if>
Just delete the opening and closing "if" statements, so that the skin will always generate the CSS you need. Careful - syntax errors here will cause a crash:
On the first line, delete:
<ja:if not test="${excludeBacklinks}">
And delete the closer on the last line:
</ja:if>
