Hello,

when creating a Windows Live Writer account for remote "news articles" provider the Add Weblog Account wizard ends with the following message:
(posting url is "http://mydomain/metapost.ashx?key=news articles")

---------------------------
No Weblogs Found on Server
---------------------------
A successful connection was made to your account however the server
reported that you do not currently have an active weblog. Please ensure
that your account with this provider is current before proceeding.
---------------------------
OK  
---------------------------

my environment is
metapost 1.1.7
DotNetNuke 4.8
Ventrian News Articles 0.5.77

Blog, Text/HTML and FAQs provider are working well

Andreas

Hi Andreas and Roland,

First of all, thanks so much for trying metaPost.  I'm sorry you've had problems getting it to work properly.  I believe some of these issues have been resolved in the next release which I will make available publicly this evening (03/02/2008). 

@Andreas - is the friendly name set to "news articles" for the News Articles module or has it been modified.

@Roland - The design goal I had for the provider key was to make sure it was easy to configure and the easiest thing I could think of would be the name that appears in the dropdown list that the end users will see.  I've changed the latest set of providers to return this name to metaPost for the key comparison.  This means that if you change the name of the News Articles module to Publish, you can use http://www.yourdomain.com/metapost.ashx?key=publish for your connection URL.  It also means that if you change the name of the provider later from Publish to Contribute, then you'll have to update your WLW account to reflect the new name. 

HTH,

Don

Hi Andreas,

Thanks for your post and I'm sorry you're having all of this trouble.  I hope we're able to get it resolved for you quickly.

By Friendly Name, I'm referring to the name that's listed in the dropdown when you go to add a module to a page.  This is coming from the FriendlyName column of the DesktopModules table. 

Let me know if upgrading to the latest version of Ventrian doesn't solve the problem for you,

Thanks,

Don