Looks like you have the teaser inside a div, and then inside a p. I don’t see any CSS for the p tag, so don’t know what the defaulting might be. Looking from Firebird, seems like your p tag might have a top-bottom padding or something like that.
=d
Thanks for your help. That worked, for a while, but has now stopped working, and I can’t understand why.
Please help. I’m usually very capable of controlling errant html and css but the beast will not be calmed this time.
TV,
I’ll have a look at the site after work and see if I can spot anything.
Craig.
Having read some other messages, and tried a few of their suggestions, it now appears that the blank line preceding the teaser message is mandatory. I cannot determine whether this is a bug or a feature.
It dissapears if you comment a few of the lines in b2vars.php – the ones which deal with line breaks and paragraph breaks – but in my case that led to the dissapearance of all paragraph and line breaks. As I have well over 100 lengthy pages on my site I cannot go through them all through b2-edit and put the line-breaks and paragraph breaks in manually, and I suspect it would be too complex a task to automate, if automation was at all possible.
For me this is a big problem because I am not running a personal blog but a content-based public website – I’m using WordPress as a CMS. I know it’s not designed for that, but then neither was b2, and b2 coped perfectly well. I had hoped that WordPress would to.
Any CMS or blogging tool should give the page designer complete control over everything on the page. Unless there is something that I’ve missed, I do not have complete control.
Worst of all, the upgrade has coincided with one of my site’s traffic peaks. These happen when we post something that lots of people are interested in, and they usually result in a heightened average level of traffic and therefore more advertising revenue and continued growth.
I am almost certain that, due to the depleted navigability of my website – caused by the failure of the next_post and previous_post tags, and the unprofessional appearance (the front-page looks a mess with all those spaces), I have lost current and future revenue.
“More simply, WordPress is what you use when you want to work with your software, not fight it.”
I’m fighting WordPress and losing. It’s a shame because everything else about the software is brilliant, and I looked forward for a long time to putting ‘Powered by WordPress’ on my pages and supporting this otherwise excellent exponent of the open-source software movement.
If the CSS rule stopped working, you likely added another rule that accidentally took precendance over the working rule. You have created a custom layout, so you can’t really blame WordPress when it doesn’t look like you want it to.
The next_post and previous_post functions were fixed within days of the 1.0 release. I too wish they had been tested before the actual release, but bugs happen.
We have gone to great lengths to make the bug fixes available, even setting up nightly releases (link is on the download page) so you can grab the latest bug fixes without having to log into CVS.
I hope you resolve your problems soon and are able to get on to the business of your site.
