Forums

Anthony-

I really love this module.

I am wondering if it is possible to configure the module to work without specifying an extension at all.

For example, instead of having www.mydomain.com/products.aspx

or even www.mydomain.com/products.myextension

I would like to be able to have just www.mydomain.com/products since this is even more marketing friendly and dummy proof for people trying to get to our webpage.

I imagine this might cause some confusion with child portals, but I figure you would know if its even possible since you have already been down this road.

Thanks!

Thinking more about this....

Basically, it would only be necessary on inbound traffic. 

Perhaps if the extension param is set to "" then the module would just assume ".aspx" and map to "default.aspx"

Also, one last thought.

Is it possible to be able to still keep the native DNN spider friendly URL functionality?

It would be great if they could co-exist as both offer nice benefits.

I am guessing that they wont work together if both are trying to modify outbound URLs, but I see no reason why they couldn't be made to work side by side for incoming URLs.

So perhaps a way to selectively turn off outbound modification?

Hi Jay,

The limits on achieving a www.mydomain.com/products style URL are really hard-wired into IIS, since the only way you can really do this is to create a real directory called products, and put a default.asp/aspx/whatever you set up in IIS to redirect to the appropriate page.  Otherwise IIS will report a 404 error (because the folder doesn't exist) without any ASP.NET code even being executed at all.

As far as keeping the native DNN friendly URL feature turned on, you can give it a try and let me know how you go :-).  Just put the <httpModule> entry for HrefExchanger after the DNN one so that it gets to rewrite the URL first (or before, for the opposite results).  I can't guarantee any level of success, because I've found the native rewriting code to be _very_ unfriendly to non-dnn URLs.

If you let me know the results of your tests, I can have a look at providing an option to switch off outbound filtering.

FYI:  I will be on leave until the 30th, so it won't be until then.

Please correct me if I'm wrong, but it seems to me that the disadvantage to using HrefExchanger is that if the tab name changes, the URL changes and is no longer "findeable".  As a broken link, it defaults to the portal's home page. 

Is that correct?  I can see where the native rewriting logic in DNN 3 seems to circumvent that problem.

Assuming this is the case, I'd still like to use HrefExchange to modify the file extension from .aspx.  However that would require being able to switch off output.  Any possibility you could add that switch?

>> Please correct me if I'm wrong, but it seems to me that the disadvantage to using HrefExchanger is that if the tab name changes, the URL changes and is no longer "findeable".  As a broken link, it defaults to the portal's home page. 

Yes, this is correct.  If you have a particular "old" URL that is particularly important (and you are using DNN 3), you can use siteurls.config to set up a server-side redirect (this is a DNN 3 feature, nothing to do with HrefExchanger).

>> I'd still like to use HrefExchange to modify the file extension from .aspx.  However that would require being able to switch off output. 

Do you want to be able to switch off output filtering of URLs?  For what purpose? It won't address the issue of "broken URLs" you have mentioned above.

What I'd like to be able to do is change the file extension from .aspx for all of my portals.  So, I'd like to apply that file extension change throughout the DNN installation.  However, I only want to apply the URL rewriting logic to the portals of my choice --- for which I will take extra care to use the siteurls.config you mention when I make future changes to particularly important pages.

I mentioned the output filtering because I thought that would be a way to "turn off" the URL rewriting by default, and enable it only for those portals I wish to track so carefully.

Shane,

The beta downloads page at http://www.inventua.com/beta.content has a new version of HrefExchanger that allows you to disable HrefExchanger on a per-portal basis.

I've run into some compatibility issues with cataLook.  It isn't just this module, cataLook doesn't work yet with DNN Friendly URL's either.  However, I want to keep my custom file extension.  Unfortunately setting enabled to false turns off the custom file extensions as well as the friendly URLs.  Would you please separate out that functionality?

Also there is a problem with this forum.  I had to click Add Reply at the bottom of the forum, then it worked.  But at first I just click Reply to directly reply to my most recent post, and it brought up an error.  This is the URL the link took me to, which generated the error:

http://www.inventua.com/forums.content?view=post&forumid=1&postid=498&replyid=603

>> However, I want to keep my custom file extension.  Unfortunately setting enabled to false turns off the custom file extensions as well as the friendly URLs.

I don't understand what you mean here.  Can you explain more for me?  It may be that the disable-output-filtering option does what you want.

And thanks for the info on the forum problem.  Its a bug that gets triggered when I delete a post (and fixes itself when a new post is added).

Hi,

What I am trying to do is to keep out put filtering disabled, *except* to still change the file name from the default .aspx extension to the extension I specify.  So, for example, assuming that I have friendly URLs enabled as host, this:

http://www.callcenters24x7.com/Home/YourCallCenter/ManageYourAccount/tabid/64/Default.aspx

Would become this:

http://www.callcenters24x7.com/Home/YourCallCenter/ManageYourAccount/tabid/64/Default.cc24x7

And at the same time, input filtering remains enabled.

As far as leaving input filtering enabled (and everything else off), the disable-output-filtering will do the job for you. 

As far as changing a DNN "aspx" friendly URL to something else, HrefExchanger will not recognize DNN 3 "Friendly URLs" as being anything it should modify.