Editing h1, h2, h3

Well, that hack is good to know. However, I do not use sidebars on this series of pages. In addition, the client I am working with is paying extra to gain access to the wiki.css file because he would like to customize things. Therefore, if you can think of any other way to get the changes made, that would be greatly appreciated.

Well my company uses the paid wiki css and I never use it. Here is what I would suggest. Create a template page and place all of your css code in a style tag on that template page. Make sure that you have the styles exactly how you want them for a while because although you only have to write one template page to begin with. If you change any styles you will need to update every page on the wiki because of course template pages do not update your pages like a css file. You can also try adding !important to the end of each css statement that isn't working like this.

h1 { font-size: 1em !important; }

Other than that I'm not sure. Its hard sorting through that wiki.css file but if you can do it your awesome.

I have the same problem. I have gone to settings and used the css editor in the package. I also asked support who suggested that I tried:
#displaycontent h1 { font-size: .6em !important; }

Which skin / theme do you use, we are using "que" or something like that.

I looked at the fully rendered page and #displaycontent h1 is declared in a style sheet that is before the wiki.css. I would have thought that styles were accumulative, So if you declare #displaycontent h1 and then redeclare is later in another css, it would change any params you changes in the second one. Is this correct.

I am not a CSS expert. Anyway, not entirely happy with the answer, so if anyone can shed light on a good solution.

#displaycontent h1 { font-size: 1em; } works for me?

I think it's the font-weight attribute (which is normal for h1 and bold for h2, h3) that makes you believe it's not working when trying to change font-size attributes ...

for h2, h3 etc. try using

#displaycontent h2, #displaycontent h3 { font-weight: normal; }

OK, well, if it works for you, then we are getting somewhere, now all we have to do is work out the difference between your set up and mine.

I am sure it is not working in mine. H1 is set to 2em in the skin and I am setting it to 1.3em. In the wiki.css editor page, you can clearly see h1 is smaller than h2 (as we want), BUT when you look at one of the wiki pages, H1 is still larger than H2.

I have also tried different skins without success, so I am stumped. Unless the "wiki.css" that is being supplied when you first go into the page is wrong. saved incorrectly etc.

OK, I am using firebug, looking at the css's in effect at the point h1 is rendered. It appears that https://vs1.pbwiki.com/common_both-v0...

is taking precedence
#displaycontent h1 {
font-size:24px !important;
}
Do you not get this inyou wiki pages?

That stylesheet does not appear in my wiki.
I can import it and see it takes precedence, yes.

However, I can overrule the precedence by declaring

#displaycontent h1 { font-size: 1.3em !important; }

See sample page.

Unfortunately does not work for me. The one in the https://vs1.pbwiki.com/common_both-v0... is still taking precedence. In terms of your webpage, which css is referenced first (in the one using the stylesheet). The common.. appears before the wiki.css.

It seems fairly draconian to use the "important" flag in a high level css if you are actively encourages to tinker with the CSS'.

Also, why do you think that https://vs1.pbwiki.com/common_both-v0... is not in your wiki, I didn't add it to mine?

TIA - JAC

First, I want to clarify that Forum Test Wiki is not mine, it's a wiki everyone can use to illustrate forum discussions.

A common-v07.. stylesheet appears indeed after a wiki.css but contains no declarations for h1, h2.
Yours is named common_both-v07.. , has a secure URL and h1 declaration, there's a difference but why?
Skin, wiki package (upgrade level), wiki security level? I don't know.

Since you have the custom wiki.css option I think you're entitled to get professional help from PBwiki: support@pbwiki.com. Let us know!

Cheers, didn't even know about "Forum Test Wiki". Yes, I started off logging a support question, but I think it is a "permutations" problem and pbwiki don't want to (and quiet rightly), get into writing sites for people. I have in parallel to this thread replied a couple of times to support. I will re-issue a support question and point them to this thread and let you all know the outcome. BTW - Firefox's Firebug is amazing - don't know how long it would have taken me to work out all the effects of all of the css' otherwise.

Thanks again - JAC.