hello,
I use url master 2.02.02; powerdnn IIS 7 integrated and I have follow this howto:

http://www.activemodules.com/active...ve-forums/

http://www.activemodules.com/active...nity-urls/

my web.config seems ok.

but I have this error:


"Not Found.

The requested document was not found on this server"


there are some settings to configure in plesk powerdnn control panel?

thanks

You need to be running in Integrated Mode for it to work. However, enabling the URL rewriter in Active Forums broke a couple of other features in DNN for me. So, it seems a little buggy.

The URL Rewriter in Active Forums is not buggy at all. If you just click the buttons in the control it will setup everything for you automatically. If you get 404 errors after that then something with your IIS config is overriding 404 errors. Also, you need to make URL Master isn't processing ANY pages within Active Forums. If something else alters our URLS beyond the standard DNN config then you will get 404 errors. None of those items are within our control.

Hey Will,

When I enabled the AF URL Rewriter, I had 2 issues....

1) no direct links to docs/PDF's worked anymore.

For example... www.mydomain.com\Portals\1\PDF\document.pdf This does not work with URL rewriter enabled on my site. It will work if I try the LinkClick approach, but I prefer not to use this.

As soon as disabled AF URL Rewriter the link www.mydomain.com\Portals\1\PDF\document.pdf works again.

2) I have a document.html that sits in the Portal\0\ folder. It renders fine with no AF URL rewriter, as soon as I turn it on the document brings up a 404 error.


Also, I observed that when you enable the AF URL Rewriter, it placed 2 entries into the web.config file. But, when disabling it, it removes only 1 of them.

I am not sure if its my setup or not, but both of these don't work with the URL enabled. I would love to get the URL Rewriter working with out the above issues.

FYI.

DNN 5.6.1
IIS 7.0 Integrated Mode (running .net 4.0)
AF 4.3.4

Correct. This is due to a change in DotNetNuke 5.6.x. They tried to fix it in 5.6.1, but supposedly it will be fixed properly in 5.6.2. Nothing we can do about it.


Same as above.


Once DotNetNuke fixes what they broke it will work fine. Basically, DotNetNuke made a change that causes a 404 to occur in the default URL Rewriter for any page request that doesn't look like a typical dnn page.

Again, none of this is a bug in the AF ReWriter.

Will - 5.6.2 Beta is out. Does this release appear to fix this issues above?

At first glance, yes, but I haven't had a chance to run the code yet.

OK - Thanks.

Please report back once you have the chance to review.

Hey Will, Can you let us know of the new release of 5.6.2 fixes the issues listed?