iFinity

Hi,

#1. For what I have seen, I love your work!

I've downloaded and installed URL master today onto my DNN 4.8.2 site and it seems to work great for most pages. However, when trying to reach my blogentries, I get 404 errors.

Example:
1) With URL master switched off (default provider), the url for my blog entry = http://www.xend.nl/dotnetnuke_2/Blogs/Ewoksauthenticationuniverse/tabid/64/EntryID/1/Default.aspx

2) When I switch on URL master, the url changes into http://www.xend.nl/dotnetnuke_2/Blogs/Ewoksauthenticationuniverse/EntryID/1.aspx
This url generates a 404 error , the resource cannot be found.
If I enter the original url 1) into my browser, my blog entry opens fine (not redirected)

If i feed the original url 1) into the "Test url Rewriting" box on the Host Menu, I get the following:

Page Found This is the name of the tab that was found from the test request.	Ewok's authentication universe
Rewrite Path (internal path processed by DotNetNuke) This shows the Url that DotNetNuke uses internally in processing.	/DotNetNuke_2/Default.aspx?TabId=64&EntryID=1
Redirection Result If the tested request would result in a redirection to another Url, the Http response header results is shown in this field. If the Url locates the correct page without a redirection, it will show a '200-OK' status, as you would see in the Http Response headers.	301 - Permanent Redirect Location: http://www.xend.nl/dotnetnuke_2/Blogs/Ewoksauthenticationuniverse/EntryID/1.aspx Reason: Unfriendly Url

If I feed the url listed under internal path processed by DotNetNuke (prefixed with my domain ofcourse) http://www.xend.nl/DotNetNuke_2/Default.aspx?TabId=64&EntryID=1, my blog entry opens fine as well.

If I feed the path http://www.xend.nl/DotNetNuke_2/Default.aspx?TabId=64&EntryID=1 into the Test rewriting url box, I get:

Page Found This is the name of the tab that was found from the test request.
Rewrite Path (internal path processed by DotNetNuke) This shows the Url that DotNetNuke uses internally in processing.	Default.aspx
Redirection Result If the tested request would result in a redirection to another Url, the Http response header results is shown in this field. If the Url locates the correct page without a redirection, it will show a '200-OK' status, as you would see in the Http Response headers.	302 - Redirect Location: http://www.xend.nl/dotnetnuke_2

The rewrite above seems to indicate it is getting redirected to the home page (which doesn't happen, it opens my blog entry fine). It also indicates no correct pagename...

I am completely lost here! Have I misconfigured or have I run into a bug?
Please help, since I would really like URL master to enhance our site (but since blogging is an essential part of the site, I cannot for now).

Kind regards,

Erik Cheizoo
eXcellence & Difference
The Netherlands
mailto: echeizoo at XenD dot nl

NB: one other, unrelated question. http://www,xend.nl/dotnetnuke_2 is our mainsite, but I would really like to get rid of the /dotnetnuke_2 part in the url (without loosing the ability to have multiple child sites in the future). Can you point me to a page with a HowTo or give me a clue on how to achieve this?

Sjeiz

Thanks for the detailed post.   I'll have a look into the problems and try and recreate on your setup - but this will take a day or so, you'll have to be patient with me!  

FYI it is possible to remove the 'dotnetnuke_2' from your portal name.  First you need to set up your IIS site so that it is accessible via xend.nl/ , then you need to update your portal alias to xend.nl instead of xend.nl/dotnetnuke_2/

I suspect you have a virtual directory defined when perhaps you want to create a new website.   If that's not enough information for you I should be able to point you in the right direction.

-Bruce

I had a light-bulb moment.  If you're running iis7 you probably need to modify the <system.webserver> element, so that the Url rewriting is done by the correct provider.

Try modifying your web.config manually to insert this line into the <system.webserver> section:

<add name="UrlRewrite" type="iFinity.DNN.Modules.UrlMaster.UrlRewriteModule, iFinity.UrlMaster.FriendlyUrlProvider" preCondition="managedHandler"/>

and remove the 'old' one:

<add name="UrlRewrite" type="DotNetNuke.HttpModules.UrlRewriteModule, DotNetNuke.HttpModules" preCondition="managedHandler"/>

And tell me how that goes.

The problem is you are generating the friendly Urls OK, but not interpreting them correctly - which is a url rewriting problem.  It works OK in the test section because the test section ignores the web.config and works on an in-memory version of the provider.

 

---

Chief Software Hacker