Aaron Brazell

Isn’t this was Custom Fields are for?

The details of the exploit were published by Ivan Fratric (the security guy who reported the situation) here.

https://ifsec.blogspot.com/2007/03/wordpress-code-compromised-to-enable.html

This is indeed quite dangerous.

Do the two have to be mutually exclusive? Is there integration that would make one or both sides have to rely on the codebase of the other?

Obviously, my preference is to run on a Linux box which precludes using ASP but beyond that, IIS supports PHP and ASP at the same time so why not just configure IIS to answer to .php with the PHP process and .asp with regualr built in IIS handling?

My feed runs through Feedburner (branded with b5media). HardinComp asked me the other day in an email and I failed to respond to him. Truth is, I’m not quite sure what he is referring to either. All I can think of is he saw the XSLT that is provided by Feedburner and assumed I had done some styling to it.

Also, Firefox 2 strips custom XSLT (i.e. Feedburner’s XSLT) so while some may see unstyled RSS, he may be seeing styled in Thunderbird (no experience, I use Mail.app for email).

If anyone is still having problems, I just released a new version of the plugin today that should fix any of the issues you’ve run into.

If your plugin files are editable, you can copy the contents of the export file over top of, say, hello.php. Not recommended though as if you mess up (i.e. add white space before or after the plugin), you will have blocked yourself from accessing your blog.

However, if you’re daring (and careful) there is a way…

TXP just changed to GPL.