lbessant

Hmmm. Works fine for me on 1.2.x, but (even using the beta version), the user interface bit doesn’t appear on 1.5. Plugin doesn’t seem to be completely dead as the function code appears in the template…

No errors displayed….

@ginjiamano:

See this post, which should help….

This post might help.

In brief, you’ll need to fix the value for siteurl in your database using PHPMyAdmin or your choice of database tool, and probably modify wp-login.php to stop WordPress trying to be helpful by changing it back.

Admin – is it possible to make a link to this solution “sticky” – variations of it seem to be biting a lot of people.

That looks suspiciously similar to the siteurl issue that’s quite popular at present:

See this post

Have you checked for whitespace in the plugin file? Specifically trailing spaces after the closing ?>

That does seem to be the most common cause of the “headers already sent” error. This FAQ article might be relevant.

I have the plugin working on my site and I haven’t had that issuse….

Saw mine in IE5.5/Win recently[1]. Looked a complete mess, but as I was updating the computer in question and getting as decent a version of IE as exists[2], I wasn’t really concerned.
Given that IE updates are more about system security than about rendering improvements, I have this vague idea that older versions of IE should not be catered for in layouts – if it looks broken, the answer is to update. If anyone has IE5, they likely have bigger problems than some pages looking messy.
[1] Previous version of the layout, but the current one isn’t much different
[2] Insert standard rant about IE here[3]
[3] It’s the indirect cause of much of the hassle in my job[4]
[4] I love removing spyware that less sophisitcated users manage to get all over their machines

I’m using WpBlacklist to deal with the Phentermine idiot, but to answer your question, copy everything from the opening <php to the closing tag and paste it into your preferred text editor. Save it as a new .php file, then upload to your plugins folder. It should then be available to activate….

There seems to be an epidemic…
I’ve been getting hundreds of spam attempts from 65.75.175.30.
WP-Blacklist is zapping them all quite nicely, so it’s merely an irritation, apart from the fact that some of the URLs are malformed, which caused Blacklist to make entries in the db that generated errors when posting legitimate comments (comment gets posted, but poster sees screen full of PHP errors). Cause turned out to be trailing backslashes at the end of the URLs. Quick edit in the db and all fixed…

Now that’s neat. I’ll be playing with that, too.
Thanks ??

For text editing, I like Textpad. Handles multiple files, and has loads of add-ons to extend its functionality.
Free trial, worth a look….

A link to the site might help someone give a more helpful response.
But what often happens is that a *single* error (often an unclosed tag) can make the rest of the page throw up more errors.
Nothing wrong with using Dreamweaver – just use the “Code” mode to check for broken XHTML rather than entirely relying on the “Design” mode.
The site might look as intended in IE, but the invalid code might cause problems in other browsers, so it’s probably worth making the effort.
Post a link, and I’m sure someone here will be able to point you in the right direction…

Take a look at Listamatic – lots of examples of how to style lists/menus.
You can either take one of the examples as is, or use it as a basis for your own design….

Well, having moved my old MT layout to WP, I decided it was time to change the look a bit. The new version is now live. I’ve moved most of the remaining static pages into the weblog to reduce the workoad next time I change the design (it’s only a matter of time…)
Now here’s an interesting thing – since I moved to WP, I seem to be making a lot more posts, and more longer posts especially. I think it’s the more pleasant interface encouraging me to do that……..

The class “post” is most definitely defined in the CSS. In mine, anyway, which is the only one relevant to this particular problem. There is a further class “post” defined in the context of the menu div:
#menu .post { whatever }

In the words of Microsoft, “that behaviour is by design”. The menu div contains a number of divs which do have the class post. Nothing odd about that at all, if you look at the CSS. And as the current design uses the same kind of structure without signs of borkage, I really can’t see that being the cause of the problem. Also, the fact that a standards-compliant browser has no trouble with the page suggests that the issue is with IE’s rendering, doesn’t it?