CSS question

Your excerpt’ed posts are placing the content text into the postmetadata div element, where as full content articles are placing the text into the entry class div..

Your small font size is inherited by the postmetadata class, which is set to 1.1em in your style.css

Right, why would the plugin author do that? Chaning the postmetadata font size does not have the result that I want btw… The first (unexcerpted because of the plugin) post gets larger and smaller, not the excerpted posts. Anoter problem with this method is that the line heights (? white between two lines) is smaller which is natural since it’s postmetadata…. I think I better leave the issue alone. Thanks for the pointer though.

No idea, there’s no reason you can’t put some new elements in and re-style them how you want though.

If the plugin only deals with excerpts it shouldn’t really touch the HTML side of things, unless it’s optional, check the options, there may be an option for the excerpt element’s class or ID.. or the element itself.

Thanks, but that’s way over my head. I can’t find anything in the plugin code to make another CSS reference either. I guess I’ll leave it with this.

Well it’s simple enough, depending on how you want to look at it.

Did you have to edit your template file to use the plugin, if so what did they have you add?

I just installed and activated the plugin, that’s it. I don’t understand why the makeup isn’t just the same as the normal index without the plugin. Do I have to make another CSS argument in the stylesheet for the plugin or another CSS reference in the plugin files?

Open up excerpt-editor.php in the plugin’s folder, around line 37 there are some inline styles with font sizes, see if altering or removing those helps.

Thanks again. I didn’t think font sizes to be anywhere but in CSS files.

<style type="text/css">
.pgee-exc-before {
	font-size: 1.3em;
	margin: 20px 0 10px;
}
.pgee-exc-title {
	font-size: 1.1em;
	margin: 15px 0 5px;
}
.pgee-exc-text {
	font-size: 0.9em;
}
.pgee-read-more {
	font-size: 0.9em;
}
</style>

No matter what I edit, nothing changes. Perhaps a persistent browser cache on my work’s IE7, I’ll have another look when I’m back home.

Ok, forget that, try this..

Find this in style.css.

.post p, .post ol li, .post ul li{
	margin-top:0;
	font-size:1.2em;
	line-height:1.5em;
	text-align:justify;
}

Update to..

.post p, .post ol li, .post ul li, .post .pgee-read-more {
	margin-top:0;
	font-size:1.2em;
	line-height:1.5em;
	text-align:justify;
}

However this bit from the plugin…

.pgee-read-more {
	font-size: 0.9em;
}

Should be controlling the font size, which is what i’ve basically asked you to add into your style definition.

Forget what i said about the postmeta div before it’s not actually that important..

If the suggested change doesn’t work, try it again, but also change this.

font-size:1.2em;

to..

font-size:1.2em!important;

I see what you’re trying to do. I applied all changes you suggested (the stylesheet including the important argument and I changed the font size in the plugin file, but to no avail. I switched themes and back, something that I always had to do in the old days to get changes in the stylesheet to work, but no again. I even installed WP Super Cache so I can be 100% sure that it is not some WP cache thing…

There is only one real problem:
Your excerpt’ed posts are placing the content text into the postmetadata div element, where as full content articles are placing the text into the entry class div..

I noticed that the plugin is only fit up to WP 2.7
What version are you running?

It’s not the plugin adding in the postmetadata div, that’s somewhere in the theme files.. (i was wrong before)

You must have a template file with a conditional statement that switches between excerpt and content.

I’d imagine (although this isn’t a solution) that removing the font size declaration for postmetadata would resolve the font size issue, but alas you’ll have large text for all the meta info.

I think there’s some inheritance from another element, and the best way i can see to resolve this is to correct the problem template file (again it’s not the plugin – or at least i don’t think it is).

Thanks for baring with me. Shamefully I have to say that it was something different alltogether: an unclosed </div> after the postmetadata call. No I didn’t find that myself and I’m still working on it, but I pointed us all in the wrong direction.