World is now on Opti ID! Learn more

Magnus Rahl
Jan 27, 2009
  6198
(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

Please login to comment.
Latest blogs
Make Global Assets Site- and Language-Aware at Indexing Time

I had a support case the other day with a question around search on global assets on a multisite. This is the result of that investigation. This co...

dada | Jun 26, 2025

The remote server returned an error: (400) Bad Request – when configuring Azure Storage for an older Optimizely CMS site

How to fix a strange issue that occurred when I moved editor-uploaded files for some old Optimizely CMS 11 solutions to Azure Storage.

Tomas Hensrud Gulla | Jun 26, 2025 |

Enable Opal AI for your Optimizely products

Learn how to enable Opal AI, and meet your infinite workforce.

Tomas Hensrud Gulla | Jun 25, 2025 |

Deploying to Optimizely Frontend Hosting: A Practical Guide

Optimizely Frontend Hosting is a cloud-based solution for deploying headless frontend applications - currently supporting only Next.js projects. It...

Szymon Uryga | Jun 25, 2025

World on Opti ID

We're excited to announce that world.optimizely.com is now integrated with Opti ID! What does this mean for you? New Users:  You can now log in wit...

Patrick Lam | Jun 22, 2025

Avoid Scandinavian Letters in File Names in Optimizely CMS

Discover how Scandinavian letters in file names can break media in Optimizely CMS—and learn a simple code fix to automatically sanitize uploads for...

Henning Sjørbotten | Jun 19, 2025 |