Point your software at http://jzalter4u.wordpress.com/xmlrpc.php .

If it is why can't I get it to work? If it's not available can someone let me know so I can stop wasting time looking for a way to do it.

Thanks,

John

I am now having the same problem with my site http://ofdustandkings.wordpress.com

Any help would be greatly appreciated. Thanks!

~Thomas

Thanks so much will do!

What was the solution to this? I still can't post via xmlrpc since the 20th?

I have replied to you privately via email in order to further troubleshoot this issue. Please look for an email from support@wordpress.com in your inbox.

We are looking for some assurance that this problem is being looked into.

Thanks.

You cannot retire or cripple the XML-RPC API because stand-alone WordPress.org sites must provide that API. OAuth for standalone installations will never work because no web service is going to register its application with each individually installed WordPress.org blog.

Hi Kathryn,

Could you provide an update in regards to where we are at with this issue please.

This is affecting multiple users and has been ongoing for coming up to a couple of weeks.

We would really appreciate an update so we can assure our mutual users that something is being done to resolve this.

Thanks,

Dyson

Thank you,

Dyson

The user posting was success with the OAuth method using the api token.

Ref.
http://developer.wordpress.com/docs/oauth2/
http://developer.wordpress.com/docs/api/1/post/sites/%24site/posts/new/

Please advise.

Thanks for your reply.

When using the email address and try the "wp.getCategories" method got the following error message:

"403:Incorrect username or password.",

And when using the username instead of email address and try the "metaWeblog.newPost" method got the following error message:

"500:You are not allowed to do that."

Please do the necessary, we can not post from 20 November, before is is working fine.

Thanks.

Accessing via a simple php script.

--Excerpt (edited to remove usernames etc--

$username = #####";
$password = "#####";

$date_image = date('y-m-d-His');

$category = "General";
$keywords = "";
$encoding='UTF-8';

$keywords = htmlentities($keywords,ENT_NOQUOTES,$encoding);

$content = array(
'title'=>$title,
'description'=>$body,
'mt_allow_comments'=>0, // 1 to allow comments
'mt_allow_pings'=>0, // 1 to allow trackbacks
'post_type'=>'post',
'mt_keywords'=>$keywords,
'categories'=>array($category)
);
$params = array(0,$username,$password,$content,true);
$request = xmlrpc_encode_request('metaWeblog.newPost',$params);
$ch = curl_init();
curl_setopt($ch, CURLOPT_POSTFIELDS, $request);
curl_setopt($ch, CURLOPT_URL, $wplocation);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);
curl_setopt($ch, CURLOPT_TIMEOUT, 1);
$results = curl_exec($ch);
curl_close($ch);

--End Excerpt--

If you would like to see how this normally operates when interacting with wordpress site please take a look @:

http://myviennamedia.com.au/~myvm/vaw_base/test/vaw/main/main.php?api=BMC225563

Generally the write option is best for testing.

This then writes to a Test wordpress site that we have setup on a multihost http://174.120.2.163/~myvm/test/ - I am just providing this to you so you can see how it works. I understand that this is not your site (trying to provide as much information as possible to assist you with your diagnosis). :)

Thanks,

Dyson

Here is the list that I have @ hand. As mentioned the users sites are communicating with wordpress.com via xml to create posts.

This was operational with no issues a few days ago. Perhaps a plugin was upgraded permissions changed or alterations made on their xmlrpc.php files or something along those lines?

clairex1.wordpress.com
hhmhealth.wordpress.com
amctrainingcentre.wordpress.com
levidavid77.wordpress.com
Bearzali.wordpress.com
maiah1.wordpress.com
chrisfrancisblog.wordpress.com
noworriesturf.wordpress.com
rosiewebsmith.wordpress.com
rayseeto.wordpress.com
evanoll.wordpress.com
maryn55.wordpress.com

Thank you for your assistance in regards to this.

Dyson

vawwordpress - I've also replied in your other thread.