Oh come one lads, surely someone knows whats wrong?
I’ve seen a few other members have had similar problems with no satisfactory answer or solution.
for future reference, and just a friendly headsup, your 2 hour later bump just removed you from the queue of unanswered posts. That queue tends to be the first place ppl look when answering.
Patience goes a long way here, and typically its nice to wait 24 hours before bumping. Impatience, on the other hand, while tolerated, doesn’t enamor anyone to your cause.
We all volunteer, and if no-one has answered yet then there a good chance that no-one knows the answer.
Has anyone figured this out? I’m having the same problem with FireScribe…
There are several threads on this same subject that have existed for months and so far as I can tell, none have been answered.
Also, please note that neither post2blog nor blogdesk nor livewriter will work with WordPress due to this same xmlrpc.php error.
There are several threads on this same subject that have existed for months and so far as I can tell, none have been answered.
Yes, and it’s quite likely that none of them will be answered. Nobody ever gives enough information to make any sort of informed guess at what is going on.
We cannot solve problems in a vacuum.
The problem is not a WordPress related one, it’s a server or site-specific issue. WordPress does indeed work fine with several XML-RPC capable clients, including all of the ones mentioned in this thread. Many of the main WordPress developers use XML-RPC on their own sites. Any bug in this respect would be noticed fairly quickly.