XML-RPC issue

2 views
Skip to first unread message

Peter Fleck

unread,
Jul 28, 2010, 6:59:01 PM7/28/10
to mpls-stpau...@googlegroups.com
I'm having some trouble autoposting from Posterous to a WordPress
blog. Posterous tells me "The site settings for this autopost site
don't allow autoposting." (I think they mean the WP site not the
Posterous site.)

XML-RPC has to be enabled and it is. I've tried giving Posterous both
admin and editor privileges. Posterous can check the authentication
and doesn't complain. But still the error.

I set this site up with 'index.php' at root and WP in the WordPress
folder. I believe I have it configured correctly and I don't get any
errors when browsing the site. But I'm wondering if that affects the
XML-RPC situation.

Any ideas?

Peter

--
Peter Fleck
Blog: http://www.pfhyper.com/blog
Twitter: http://twitter.com/pfhyper
pfh...@gmail.com

Mitch Hislop

unread,
Jul 28, 2010, 11:14:32 PM7/28/10
to mpls-stpau...@googlegroups.com

Like any api, xmlrpc is an endpoint that expects to see what it needs at the top level. Are you pointing the endpoint into the wp folder?

Mitchell Hislop
Geek
6124184992

Sent from my mobile

> --
> You received this message because you are subscribed to the Google Groups "Minneapolis St. Paul WordPress User Group" group.
> To post to this group, send email to mpls-stpau...@googlegroups.com.
> To unsubscribe from this group, send email to mpls-stpaul-word...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/mpls-stpaul-wordpress?hl=en.
>

Garrick Van Buren

unread,
Jul 28, 2010, 11:14:25 PM7/28/10
to mpls-stpau...@googlegroups.com
Peter, are both XML-RPC and Atom publishing checked? Posterous might be going over Atom.

--
Garrick.

Peter Fleck

unread,
Jul 29, 2010, 12:38:43 AM7/29/10
to mpls-stpau...@googlegroups.com
Garrick - Tried it with Atom on and off.

Mitch - if I point to the wordpress folder it says it can't
authenticate because it can't find a valid endpoint. It does seem to
authenticate when I point it at root where index.php sits.

I also tried a symbolic link to the xmlrpc.php file placed at root but
that didn't work.

Peter

Mitch Hislop

unread,
Jul 29, 2010, 1:05:44 AM7/29/10
to mpls-stpau...@googlegroups.com

I'm guessing this is in production, or I would suggest moving the whole folder to root, and ruling out several things.

Maybe try that on a subdomain with a duplicate of the files to narrow down the issue?

Mitchell Hislop
Geek
6124184992

Sent from my mobile

Mitch Hislop

unread,
Jul 29, 2010, 1:07:00 AM7/29/10
to mpls-stpau...@googlegroups.com

Sorry for the double post...

So it auths, but can't post? What version of wp is it? Shared or dedicated hosting?

Mitchell Hislop
Geek
6124184992

Sent from my mobile

On Jul 28, 2010 11:39 PM, "Peter Fleck" <pfh...@gmail.com> wrote:

Peter Fleck

unread,
Jul 29, 2010, 12:06:05 PM7/29/10
to mpls-stpau...@googlegroups.com
It's not quite production, Mitch, so I can experiment. It looks like
it's a Posterous problem.

I did move all the WP stuff to root and got all the linking working
again. Posterous still won't autopost.

So I went to another Posterous blog and hooked it up to the WP site
and it autoposts with no problem. I wish I had tested this before
moving all the files around but that's life. So it must be something
with the new Posterous blog I created yesterday.

Other info... it is WP 3.0 on a shared hosting system - tigertech.net.

I do have a support message in to Posterous. I think Posterous somehow
cached some information on it's end as it tells me the site is
misconfigured immediately after I try to autopost.

Peter

Reply all
Reply to author
Forward
0 new messages