A critical vulnerability was discovered in React Server Components (Next.js). Our systems remain protected but we advise to update packages to newest version. Learn More

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

Please login to comment.
Latest blogs
Building simple Opal tools for product search and content creation

Optimizely Opal tools make it easy for AI agents to call your APIs – in this post we’ll build a small ASP.NET host that exposes two of them: one fo...

Pär Wissmark | Dec 13, 2025 |

CMS Audiences - check all usage

Sometimes you want to check if an Audience from your CMS (former Visitor Group) has been used by which page(and which version of that page) Then yo...

Tuan Anh Hoang | Dec 12, 2025

Data Imports in Optimizely: Part 2 - Query data efficiently

One of the more time consuming parts of an import is looking up data to update. Naively, it is possible to use the PageCriteriaQueryService to quer...

Matt FitzGerald-Chamberlain | Dec 11, 2025 |

Beginner's Guide for Optimizely Backend Developers

Developing with Optimizely (formerly Episerver) requires more than just technical know‑how. It’s about respecting the editor’s perspective, ensurin...

MilosR | Dec 10, 2025