Glenn, fancy running into you here ;)

I would recommend you look at http://www.ifinity.com.au/'s URL Master module. It will allow you to define URLs in a much easier to read/edit format.

Though, as we sorta discussed on twitter earlier. For my conversion from Telligent's Community Server software to DNN I handled things with a sort of hacked solution as an interim. I actually still have CS running on the non-WWW domain, and all incoming requests get redirected to a simple ASPX page that looks up the new blog ID and matches it from the old one. Then it does a 301 transfer to the new URL.

Your other option is to do as you've previously done, mapped your URLs to pages in DNN, for a small number of pages that's okay, for a large site that's a pain in the rear :D

---

Chris Hammond
Former DNN Corp Employee, MVP, Core Team Member, Trustee
Christoc.com Software Solutions DotNetNuke Module Development, Upgrades and consulting.
dnnCHAT.com a chat room for DotNetNuke discussions

I haven't used Graffiti, but I assume it has a similar DB structure to CommunityServer? Where a blog is a Section (cs_section) and posts go into cs_posts based on SectionId?

If that's the case you should look at the scripts on my CodePlex project.

http://cstodnn.codeplex.com/

It's messy, but with some configuration you could probably make it work. It was designed for CS Forums to DNN Forum conversion, but I used a very similar script years ago when I converted my blog from CS to DNN though I converted to a module called Engage: Publish (because I was the primary developer on that product for 5 years, but no longer).

---

Chris Hammond
Former DNN Corp Employee, MVP, Core Team Member, Trustee
Christoc.com Software Solutions DotNetNuke Module Development, Upgrades and consulting.
dnnCHAT.com a chat room for DotNetNuke discussions