Jun
25

Transport error - HTTP status code was not 200

Uncategorized

Now every time I tried to blog through Digg, I encounter this error message. It is probably something to do with my WordPress XMLPRC file but I overwritten it again and it still didn’t work.

Error From Your Blog
transport error - HTTP status code was not 200

I am kinda stuck already. It’s so easy to blog through Digg and it’s unfortunate that I can’t do so anymore. I am using WordPress 2.2.1, it’s the latest version of WordPress. Blogging via Digg used to work before I upgraded from WordPress 2.2 to WordPress 2.2.1. It just stop working after that upgrade.

Tags: , ,

3 comments for “Transport error - HTTP status code was not 200”

  1. Same thing here but mine worked until yesterday…
    I’ve also noticed occasional garbage on the screen and the editor gets messed up. It only happens in wordpress. I have two other packages running, TNG (Genealogy) and Gallery2
    Any ideas, yet?

    by Tom (Jul 9, 2007 at 7 PM)
  2. I don’t get the garbage but I still get the transport code errors.

    It’s driving me nuts last week. But I just give up. I don’t really know who to seek. I don’t even know how to describe the problem properly. And I tried to look for other people facing the same problem. I guess I kinda given up. Hopefully 2.3 version would be fine. :D

    by Mr. Dew (Jul 13, 2007 at 12 AM)
  3. I haven’t had any problems yet! :)

    by Bubba (Feb 27, 2008 at 1 AM)
 

Leave a Reply

 

Comments may be moderated due to spam. No advertisements are allowed in comments.

You'll require some math knowledge to comment, this is done to stop evil bots from spamming my blog.

Read my comments policy

Want a display picture?