Can you test 7.0.3 out locally just to see if the issue is still there?

---

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

The regexMatch=.... value in the web.config controls what characters are allowed in and out of the url path. However, a non-match in here usually means you get that in the querystring rather than the path. That bit is FYI.

I didn't see where a change happened with the standard friendly url provider.

One thing you *could* try..

[WARNING WARNING WARNING only try with backup and probably not recommended]

...is getting an earlier build of DNN and separating out the friendly url provider into a separate DLL, or finding the bit that has changed and building a new one, and configuring that in your web.config. I stress that you need to build a separate assembly, becuase all of the HttpModules are built into the one assembly. But there is no reason why you can't separate the provider/url rewriter out into a new assembly, if you need a quick'n'dirty fix.

While it wouldn't be pretty, once you changed the namespace and hooked it into your web.config, future upgrades shouldn't break that build.

Of course 7.1 should fix that little squeaky issue by giving you the ability to include/exclude characters from the Url by tuning the regex.

Thanks Chris, Bruce and Julie. I will decide how to tackle it on Monday and let you guys know.

Stuart

---

Owner, Hilbert Solutions, LLC
http://www.HilbertSolutions.com From Module Development to DNN Upgrades, your one stop DNN Shop