Remote blog post publishing via Word 2010

Developer
Dec 10, 2010 at 5:36 PM

I tried to set up remote blog publishing via Word 2010 with no luck:/ Has anybody made it work? I tried the same settings like in LiveWriter, but always end with an error. 

LiveWriter is working fine.

Coordinator
Dec 10, 2010 at 6:30 PM

We certainly never tried it. We will follow-up on the bug post 1.0. Thanks for the heads up.

Coordinator
Dec 10, 2010 at 7:00 PM

I just tried w/ Word 2010 and got it working but it wants a different URL for the “Blog Post URL” than Live Writer. Word really wants the XML-RPC endpoint which is ~/xmlrpc (e.g. http://myorchardsite.com/xmlrpc) for Orchard. Give that a shot and let me know if it still gives you trouble.

-Nathan

Developer
Dec 10, 2010 at 7:01 PM

Sure, not a showstopper for me, but it'll be good to have it working some day. Cheers

Developer
Dec 10, 2010 at 7:02 PM

Ok, I'll try that one and see of it works. Thanks!

Developer
Dec 10, 2010 at 7:09 PM

Ok, it worked without problems - thanks! It'd be good to put that info in the docs.

Cheers

Coordinator
Dec 10, 2010 at 7:14 PM

I updated http://orchardproject.net/docs/Blogging-with-LiveWriter.ashx with a note to that effect.

Jan 24, 2011 at 8:23 PM

I'm confused on XMLRPC support.  I have my blog (www.ariankulp.com) working just fine in Live Writer using your documentation (http://www.orchardproject.net/docs/Blogging-with-LiveWriter.ashx).  If I try to just hit www.ariankulp.com/xmlrpc I get a "resource cannot be found" error.  Word blogging support seems to be ok with it, but Blog Writer on Windows Phone doesn't like it.  For other blog packages, what is the exact URL I should use for XMLRPC support?

Coordinator
Jan 24, 2011 at 8:47 PM

You can only get at ~/xmlrpc with a POST so hitting the URL in a browser should result in a 404.

Live Writer can discover a blog's MetaWeblog API capabilities when you point it at your blog because of a couple of <link /> elements that the RemoteBlogPublishing feature drops into the blog's <head />. One is a Live Writer specific manifest, ~/xmlrpc/livewriter/manifest, telling Live Writer what capabilities your blog supports so it can tweak its UI accordingly. The other, looking something like ~/blogs/remoteblogpublishing/rsd?blogSlug=[your blog's slug], points to the (MetaWeblog) API endpoint(s) with the relevent blog ID. That's how Live Writer is cool with you giving it the URL to your blog. This seems to be something Word doesn't understand, so it doesn't follow.

What Word wants is that xmlrpc endpoint directly and IIRC it pulls the blog list from the service from there. As for Blog Writer on Windows Phone, I'm not sure what it wants. I'd assume it would be ~/xmlrpc with maybe the blogID but I can't say for certain. Is that for WP7?

Jan 24, 2011 at 8:55 PM

Yes, WP7.  I remembered wrong, it's Blog Client.  Thanks for the detailed info.  I'll see if that helps.

Jan 25, 2011 at 10:23 PM

I'm still bit confused.  My blog slug is "blog" and the ID = 698.  Both formats fail in the app.  Would you mind seeing if you can find out what my endpoint would be on my site (ariankulp.com)?  It might just be the client of course.

I tried:

http://www.ariankulp.com/blogs/remoteblogpublishing/rsd?blogSlug=blog
http://www.ariankulp.com/blogs/remoteblogpublishing/rsd?blogSlug=698

Thanks so much!

Coordinator
Jan 26, 2011 at 5:43 PM

From what I see in the routes, it would be /blog/rsd

Coordinator
Jul 22, 2011 at 8:57 PM

** adding a little more info to an old thread in case folks end up here looking for Orchard XML-RPC URIs **

Bertrand was right with his correction, the rsd URI is the blog URI with "/rds" appended.

 

If you're curious about how all of the URI's fit together:

- ~/xmlrpc when posted to with the "blogger.getUsersBlogs" method name will return a list of blog info including the blog URIs

- in the source of each blog (e.g. ~/my-blog) there are two link elements when remote blog publishing is enabled:

  - a rel="wlwmanifest" link that points to ~/XmlRpc/LiveWriter/Manifest - this tells the client what capabilities the blog supports

  - a rel="EditURI" link for the RSD which, if following the ~/my-blog example, would point to ~/my-blog/rsd and if you look at that URI in a web browser you can see the info it's describing