Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...SEO, Friendly URLs & Grandchild PortalsSEO, Friendly URLs & Grandchild Portals
Previous
 
Next
New Post
6/21/2006 9:55 AM
 

Greetings. I have a question - is it possible to create a child portal of a child portal?

The reason for this oddness is to get around a limitation in DNN:
We wish to be able to reference pages in an search engine friendly way such as:
www.website.com/EN/home/sitearea/pagename/
instead of something like:
www.website.com/EN/home/tabid/37/Default.aspx

Whilst the SiteUrls.config XML allows something like:
www.website.com/EN/home/sitearea/pagename/pagename.aspx
It is not so straightforward to allow URLs without specifying a .aspx file.

One solution is to create child portals as mentioned in the comments of this article: Friendly Urls Hack
However this only works for one level of directories such as:
www.website.com/EN/home/sitearea/
But this does not allow something like .../sitearea/pagename/ as this requires a child portal named 'pagename' of the child portal 'sitearea'.

Has anyone any suggestions to assist, other than the ideas expressed in the Friendly Urls Hack article. My thanks in advance

 
New Post
6/21/2006 2:22 PM
 

what you are asking for will not work until IIS7

you need the whatever.aspx file so IIS6 knows it is the ASP.NET pipeline you need

otherwise you could rip out the friendly url feature and replace it with your own solution (alot of work, and still limited by IIS6)

 

the child portals hack works because a child portal makes a subfolder in your install containing a default.aspx file wich redirects to the root default.aspx

in theorie, if you would make a subfolder tree in your dnn wwwroot containing default.aspx files that add the necessary values to the querystring parameter collection and then do a server.transfer to the root default.Aspx file, what you ask for could work. It's an ugly hack but it could work (no guarantee, I am making this up as I type)

this should work because IIS knows the path exists & default.aspx is in the default documents
you would need to set at least the tabid in the querystring collection and then server.transfer (not redirect)

when you do this you would have clean entrypoints into DNN, altough when browsing thru DNN, DNN would contineu to use the standard friendly url's

 

I hope this inspires your *hacking* session's


Edit your Skin.xml and Container.xml files with:
Yannick's SXE
 
New Post
6/22/2006 5:51 AM
 
Many thanks for this,

Your absolutely right regarding your suggestion - I have currently been creating a subfolder tree (with default.aspx) in each folder as a solution, but of course less maintainable than I prefer. However it does work well completly removing any vestige or hint of DNN in the URL.

I suspected that there wasn't a better solution than this, but your post has been very useful to confirm this.

Regards
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...SEO, Friendly URLs & Grandchild PortalsSEO, Friendly URLs & Grandchild Portals


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out