Magnus Rahl
Jan 27, 2009
visibility 8339
star star star star star
(0 votes)

Windows Live Writer – updated instructions

Update

The below steps are no longer needed since a bug in the EPiServer version used on world.episerver.com has been fixed, as mentioned in this blog post. You should now be fine following the instructions in the EPiServer World Blogging Guidelines. That also ensures that Live Writer will know all the capabilities (publishing images etc.) of your EPiServer World blog.

Original text

After recently downloading Windows Live Writer to edit this first blog post I discovered that the instructions in the EPiServer World Blogging Guidelines were a bit outdated. Part of the remedy was reading Dariusz Macina’s blog post on the subject. However, it seems some things have changed. These are the steps I followed to get Live Writer to work with my blog:

  1. EPiServer world uses a MetaWeblog interface, for which you need the API URL. Dariusz Macina mentions the line http://world.episerver.com/util/xmlrpc/RSD.aspx?pageid=25466 in his blog post. You will need this, but it does not seem to be available in the blog page header anymore. What is available however, is the ID of your blog, namely in the tag <meta name="CommunityPageId" content="27340" /> where I assume 27340 is the ID of my blog. I substituted this into the url to get http://world.episerver.com/util/xmlrpc/RSD.aspx?pageid=27340. Browsing to this URL indicates that the ID is actually the ID of the blog.
  2. Create a new account in Windows Live Writer (from the Tools – Accounts menu, or use the wizard which opens the first time you use the program). Choose the “Other” account type.
  3. Enter the url of your blog (in my case http://world.episerver.com/Blogs/Magnus-Paulsson/), user name and password. I think Dariusz Macina used the API url at this stage, but the normal URL worked fine for me.
  4. Choose the Metaweblog API provider, and enter the API URL constructed in the first step above.
  5. Finish the wizard and start blogging!

Now let’s see if I can post this to verify the correctness of the instructions… ;)

Jan 27, 2009

Comments

Eric
Eric Sep 21, 2010 10:32 AM

There has been an upgrade of the site and blogmodule and we missed one of the settings needed for the blogmodule to work correctly. Thanks for notice! :)

Magnus Rahl
Magnus Rahl Sep 21, 2010 10:32 AM

Glad to help, even though it was happenstance :)

Antti Alasvuo
Antti Alasvuo Jul 8, 2013 07:58 AM

I know this is an old post, but seems like the API url is now : http://world.episerver.com/Util/xmlrpc/RSD.aspx?pageid=YOUR_BLOG_PAGE_ID and you can find it by looking at the HTML source of your blog page (find:

Ashraf Al-Safoo
Ashraf Al-Safoo Feb 25, 2015 08:17 PM

None of all these work
not episerver guidelines,
not Dariusz
not yours Magnus
and not Antti comment

error Please login to comment.
Latest blogs
Extending a Contract: What You Can Override

Contracts share fields across content types — but not every field setting can be overridden. Push the same contract onto several components, and CM...

Chirag Khanna | Sep 18, 2026 |

Building a Blazor Server UI Inside the Optimizely CMS 13 Admin Shell

What I learned shipping a Blazor Server UI inside Optimizely CMS 13 — Razor components in a NuGet package, the Blazor hub next to MapContent(),...

Stanisław Szołkowski | Sep 17, 2026 |

Giving Optimizely 13 Content Types Meaningful Icons and Thumbnails

When working with an Optimizely CMS solution that has evolved over time, it is common to end up with many content types. As the number grows, the...

Pär Wissmark | Sep 16, 2026 |

force-dynamic vs connection() for Optimizely Graph

If you have built an Optimizely CMS SDK site, you already know getContentByPath on a catch-all. This post is about the part that file never says ou...

Chirag Khanna | Sep 16, 2026 |