DannyQuah

Thanks for finishing this up. Glad everything works now (and I understood both the problem and its fix). I thought I’d posted the solution here too but obviously must have forgotten. Thanks again.

The amazing Rarst solved this. She suggested I run my site through validator.w3.org. Amidst the other W3C errors, the site finds invalid hexadecimal characters. Chrome won’t show them (but Rarst says Opera does). I copied the sections over to my GNUemacs window, and sure enough they all appeared. Going through these cleared up all my problems and now WLW, ScribeFire, Qumana, and likely all other weblog clients work for me.

Many, many thanks, Rarst!

I have reproduced this problem using Qumana (on both W7 and Ubuntu Linux 14.04) now as well:

“Error decoding XML-RPC response: An invalid XML character (Unicode: 0x7) was found in the element content of the document.”

My question: Is there a way to isolate where the invalid hexadecimal character appears?

A previous related post, https://www.ads-software.com/support/topic/windows-live-writer-unable-to-retrieve-posts although marked resolved, never found where the error was, and I can’t tell if the error appears in the post content or in the db. I’m opening this thread as I think the error is in the WP content (db, post content, etc.), not in the WLW or other clients. I can’t find a single file or directory to run a grep on for this.

Any ideas or suggestions greatly appreciated.

—

Thanks for the suggestion, kmessinger. I deactivated all plug-ins, and switched to the default theme (I tried both 2015 and 2012). Unfortunately, WLW still fails to retrieve posts, and still shows the DisplayableException error.

Bruce / Eksplorr – your solution worked, obviously, but is it known whether the illegal hexadecimal character was, in fact, in one of your blog posts or in the db (and your procedure simply ended up clearing that)? Pioneer Valley’s post suggested the error might have been in the db.

I have the same problem now on my wordpress site with retrieving posts using both Windows Live Writer and ScribeFire, except that the Ubuntu client Blogilo will correctly retrieve all my previous posts. Does anyone know where ScribeFire’s error logs go? I don’t want to just rely on Blogilo if the error might, in future, end up confounding Blogilo too.

If the illegal character is in the db, is this quite a common problem that the WordPress community itself might provide tools to fix? I am uneasy about an ad hoc phpmyadmin manipulation as I don’t know if this will end up being something I have to do repeatedly.

—
Danny