Body font not showing up correctly « Support Forum | Kriesi.at

Support Forum » Shoutbox

Body font not showing up correctly

4 posts from 3 voices

Started 7 months ago by ces-design
Latest reply from ces-design
This topic is closed
This topic is resolved

Tags:

ces-design
Member

Hello,

I'm building a site with the Shoutbox theme locally. I don't know if the local part has anything to do with the font, but the body text is all showing up in a serif font. It looks like your default styles.css has it set to Helvetica Neue... Just in case, I added this snippet to the Quick CSS in Theme Options:

body {
font-family: "Helvetica Neue", Arial, sans-serif;
color: #000000;
font-size: 13px;
position:relative;
overflow-x: hidden;
}

Which is basically just a differently-worded version of the same thing in styles.css. Still the body text is showing up as a serif. All of the headings and the nav are correct, though. My browser is the most updated Google Chrome, by the way.

Any advice on fixing this? I can send screenshots if needed.

Very best,

Amy

Posted 7 months ago #
rumblefish
Member

Hi Amy,

What do you mean by body text exactly? If you mean the text inside the posts you need to set the .post-entry parameter. The body parameter does the text for the menus and titles and things like that.

If you use a source code inspector something like Firebug (add on for Firefox) in your browser it can help you identify which bits of css code do what. It makes life a lot easier for making changes.

rich

Posted 7 months ago #
Ismael
Moderator
Hi,

Since most of the text is stack inside the paragraph tag maybe adding the p element on your custom.css will help.
```
body p  {
font-family: "Helvetica Neue", Arial, sans-serif;
color: #000000;
font-size: 13px;
position:relative;
overflow-x: hidden;
}
```
Regards,
Ismael
Posted 7 months ago #
ces-design
Member

Hey guys,

You gotta believe me...I tried adding the p element before I had written this query and it didn't change anything! But now it works. I'm thinking I must have simply phrased some of the code wrongly when I was fiddling with other edits ;)

Thanks for the help in resolving this issue!

Best,

Amy

Posted 7 months ago #