Derik

I don’t think it is. It previously worked in 1.5.x.

Further, this errant behavior is present when using two completely separate blog clients (MarsEdit and w.bloggar, on Mac and Windows respectively).

The new XML-RPC library is the root of the problem.

Oddly enough, it seems to work for WordPress. Unfortunately, that doesn’t help me.

Ok, backticks don’t help showing the entity result.

“>” becomes “& gt ;”.

I had to rewrite the function to return my actual home path (hard wired as a string).

Apparently, this is some kind of transient error that can be corrected by restarting Apache. Just for reference.

Just to let anyone reading this know, this problem is indicative of a problem on your server. My host corrected the problem but still hasn’t let me know what caused it.

Hey clay, I’m the same guy you’ve been emailing with. I think that’ll have to be my next step if I can’t get iPowerWeb to recognize that this is a problem with their server.

I’ve found a problem with the weather plugin that seems to crash PHP or Apache when calling fsockopen(). Is anyone familiar with anything like this?

Are any of the developers skimming these boards? I really just want to resolve this problem and I will donate if I can get this working again. I’m not the most experienced person as far as PHP goes (though I have a large amount of programming experience). I just can’t isolate this problem on my own.

As far as I’m aware, my ISP doesn’t use a proxy. I’m just really bugged by the fact that the die statement prints out twice, which seems to suggest that two independent PHP threads are being spawned. The only thing that I can figure might be causing it is the use of globals in the apply_filters procedure.
Please, someone help. I’m at the end of my rope.

I’ve narrowed the problem to the use of “do_action” at line 183 (give or take a few lines, I’ve been editing the file heavily) in post.php. If I put a die statement (with a static string) in do_action after getting the results of apply_filters, I get that string twice over. I don’t understand how it could be doing that.

Another update:
My host once again has told me that the problem is on my end. There’s a problem with that assertion: Last night, I made a new database and a fresh installation of WordPress, and I still have the problem with posting.
Has anyone run into this before?

Oh, and I’m using iPowerWeb, so if anyone reading this uses them, please chime as to whether you are having problems as well.

I did in my original request for support from them. They seemed to ignore my question, but I reiterated it. Hopefully they’ll answer. At first I thought maybe they upgraded to PHP 5.0, but according to phpinfo() it’s 4.3.4.