Hello Everyone,I realize there are various >$100 modules that will handle rewriting easily, but I would definitely like to look at utilizing the built in functionality of DNN, and later leveraging the IIS if necessary. I am trying to send to the URL of a module for my site given a URL that does not include the ID within the URL.http://localhost/alecu/Log/tabid/93/post/this-is-another/Default.aspxtohttp://localhost/alecu/MyBlog/post/this-is-another/Default.aspxThis is what I have so far, and it doesn't work. I had assumed that it would rematch which was my fault. Does anyone know of a smarter way to do this? [^?]*/TabId/(\d+)(.*) ~/Default.aspx?TabId=$1 [^?]*/MyBlog/(.*) ~/alecu/Log/tabid/93/$1 Kind Regards,Kevin

For anyone else that may be wondering out how to do this, I've resolved it myself. It's really quite simple but only when you aren't trying to think of a difficult way around it. Basically what I did was look at the path:

http://localhost/alecu/Log/tabid/93/post/this-is-another/Default.aspx

And realized it was already a product of a FriendlyURL rewrite. So inside of the Host Settings I turned off FriendlyURLs and then revisited the blog page and received the following:

http://localhost/Default.aspx?tabid=93&post=this-is-another

Now that I knew what it looked like (what the querystrings where) I could easily rewrite it as it needed to be, which ended up like this through the backend (Host Settings->Advanced Settings->Add new rule):

MATCH: [^?]*/blog/post/(.+)
REPLACE: ~/Default.aspx?TabId=93&post=$1

I left the TabID as 93 since that is the TabID of my blog module. I then added a second rule following that with:

MATCH: [^?]*/blog/(.*)
REPLACE: ~/Default.aspx?TabId=93

Which will replace any redirect /blog with anything after it that isn't a post to this page. Admin side editing still uses standard DNN. The last bit was to change the ASCX file to generate the new format URLs (this URL for TabId/93 and normal style for anything else). I know this is probably trivial and not news for many of you, and for those of you who have already paid for a solution it is completely irrelevant. Hopefully it helps lead someone down the right track if, like me, they were having a difficult time with a simple chore.

Kevin

Hello Bruce,

Thanks for the reply! Yes, the largest annoyance is the maintaining of the ASCX when I upgrade the module (even though there are no current plans to upgrade, we all know it happens). I was trying to think of an elegant solution around that, and it may be something that the paid solutions actually have a large advantage in.

As to your comment about ASPX, that was what I initially was going for, as you see from my response though my matches don't require that:

MATCH: [^?]*/blog/post/(.+)
REPLACE: ~/Default.aspx?TabId=93&post=$1
Resolves from: http://domain.com/blog/post/this-is-my-post

MATCH: [^?]*/blog/(.*)
REPLACE: ~/Default.aspx?TabId=93
Resolves from: http://domain.com/blog/

Which is a good thing! I do understand your trepidation concerning the maintainability when it comes to upgrades and changes, and if I find that my sites grow beyond two or three that I may move to a dedicated solution. Now, you mention redirecting via the Friendly Url section from the old style to the new style, I've found that this doesn't seem to work well -- but it appears that the rules cannot parse out to another rule without failing. Is there something I'm missing?

I see that you are with the development of URLMaster -- would I be correct in assuming that it would allow me to not worry about modifying the ASCX file and achieve the above result (sans TabID) and then also resolve all in-module clicks?

Kevin