Blog clients and WordPress

Mostly likely something is injecting additional characters that is messing up the XML formatting.

Plugins would be my first suspect, if you disable all of your plugins, does WLW work normally? If so, enable each plugin one and at time until WLW breaks again, then you’ll know which plugin is causing the problem.

Do you mean WINDOWS Live Writer? If so, you just tell WLW WordPress, point to your blog’s URL and that’s that. This works on 2.0.11 and 2.5.1 WP sites. And I am a notorious plugin hog; the WP blog that I mostly post using WLW has over 28 active plugins…

What I am trying to say here is that I’ve never had to touch the xlmrpc.php file.

@josephscott
Disabling all the plugins has not helped. And the xml response my computer gets from the site seems OK:

<?xml version="1.0"?>
<methodResponse>
  <params>
    <param>
      <value>
        <array><data>
  <value><struct>
  <member><name>isAdmin</name><value><boolean>0</boolean></value></member>
  <member><name>url</name><value><string>https://skxpl.eu.org/</string></value></member>
  <member><name>blogid</name><value><string>1</string></value></member>
  <member><name>blogName</name><value><string>skx: Numer zastrze?ony</string></value></member>
</struct></value>
</data></array>
      </value>
    </param>
  </params>
</methodResponse>

@jonimueller
Well, I didn’t put it in “What I have already done” list, but I tried just pointing it to my blog. But you’re right, I should have stated that it’s Windows Live Writer.

I have this problem with blog clients on a free hosted blog(they use php to insert a banner ad that shows in ALL pages served, including login and RPC ;o/ )

I can write to all other(non-bannered) blogs fine.

First — thank you for your help ??

My hosting company is not inserting any banners. Wouldn’t it show in the logs if they were interfering?

I’ll try setting up a new WordPress installation to see if my problem has anything to do with the server, but until then: is there any way I can debug it — find out which element is screwing things up? Again, possibly without blindly turning things on and off.

That response looks ok. Are you sure there was nothing else in the HTTP response? A byte order marker (BOM) or anything else?

At this point I’d try the WLW forums and see if they can provide any clues. I’ve worked with some of the WLW team members, so if they have any questions on the WordPress side of things they know how to reach me.

I’m not sure about the reponse, running Fiddler is already the pinnacle of my technical skills when it comes to http, but…

I found out that my theme is responsibile — never thought of that — when I swich to its original version, everything works fine, which means I must have lost sth in translation. Which theme files, and how, can get in the way?

Sure, it’s entirely possible for a theme to get in there and mess things up, although that isn’t usually the most likely culprit.

If there is a functions.php file in your theme, that is most likely where the problem would be. Could also be in a language translation file I suppose.

Thank you very much.
3 bytes in functions.php were the cause of all my problems. Unless while restoring the old version I broke something else, it is OK now ??

I would like to know what exactly was wrong with your functions.php file.
I have the same problem and cannot resolve it.

thanks

I would like to know what exactly was wrong with your functions.php file.

Unfortunately, I don’t know and don’t even have the version (of functions.php) that was causing errors. Restoring the original file from my theme resolved the issue.

Sorry.