Vulnerability in EPiServer.Forms
I'm have difficulties connecting to my newly created blog here on world.episerver. I've followed this guide -> http://world.episerver.com/System/Blog-info/Blogging-on-EPiServer-World but I get the configuration problems descriped in this blog from 2009 -> http://world.episerver.com/blogs/Magnus-Rahl/Dates/2009/1/Windows-Live-Writer--updated-instructions/.
The issues I'm having is that I when clicking next, after added the address, username and password, it says it can't find the correct configuration I need to enter blog type and the URL.
Have I done something wrong?
I believe the newest version of WLW doesn't support previous config instructions to blog on World. As far as I know there is now an internal tool being used to blog on World, but not sure if that'll be made available for external bloggers.
I see. So what do I need to do to be able to blog att EPiServer? What's the internel tool? I feel I want to blog sometimes :)
Thank you for taking the time and effort to blog :). Hmm, it seems like at the moment that you can have a separate blog and have it "syndicated" on World. I'm not really sure if we can make available that tool, but perhaps you can leave feedback to the World team - http://world.episerver.com/support/Features-on-world/?productFilter=EPiServer+World
Thanks for the answer! I'll have to create a blog then I guess.
You don't have the possiblity to ask inside EPiServer if it's possible to make me an "outsider test-blogger" for your tool until I get a blog that syndicates could you? :)
Haha, would be nice to have outside testers :). Maybe if you asked very nicely in the feature request page you may get rewarded ;).
I'll do it first thing tomorrow, thanks for your help!
@Richly: I think this should be prioritized. A tool should be supported, even if it's just giving people a WYSISYG inline editor directly on World.
Not everyone has, or wants, an external blog syndicated to World.
(Moving this thread to the "Feature requests" forum.For reference, OP has created a World feature request for this issue. /Moderator)