Small width layout Medium width layout Maximum width layout Small text Medium text Large text
     Search
Downloads Downloads Directory Directory Forums Forums Forge Forge Blogs Blogs        Marketplace Marketplace Careers Program Careers
Community › Forums Register  |  

Affordable ASP.NET Hosting Service
  Ads  
Iron Speed Designer is a software development tool for building database, reporting, and forms applications for .NET without hand-coding.
 


  Sponsors  

Meet Our Sponsors

CrystalTech Web Hosting™
Webhost4life, specialists in DNN hosting
Mad Development is a full service interactive agency focusing on the merge of design, technology, e-commerce, and affiliate marketing by providing total website solutions.
SteadyRain
DataSprings - Great Ideas. Always Flowing.
R2integrated - formerly bi4ce
 


DotNetNuke Forums
 
  Forum  General DotNetN...  Extend It! (Pro...  Child portals errors
Previous Previous
 
Next Next
New Post 5/19/2008 1:44 AM
User is offline Agung Riyadi
100 posts
9th Ranked


Child portals errors 

I found some errors in DNN when working with child portals.

If we change default document in IIS to something else (eg. Index.aspx), and all child portals will broken.

Any solution on this ?

 
New Post 5/19/2008 9:46 AM
Online now... Brandon Haynes
705 posts
brandonhaynes.org
7th Ranked


Re: Child portals errors 

Hi Agung,

Child portals are implemented via a subdirectory with a DNN-created Default.aspx document inside.  If you reconfigure IIS to not serve this document by default, then the portals will not be served.

You might be able to get away with renaming the Default.aspx to Index.aspx in your child portal directories, but I have not tested this solution (nor would it be a standard configuration).  If you are attempting to cohabitate with another application, why not just server BOTH Index.aspx and Default.aspx?

Brandon


Brandon Haynes
BrandonHaynes.org
 
New Post 5/20/2008 7:46 PM
User is offline Agung Riyadi
100 posts
9th Ranked


Re: Child portals errors 

Thanks Brandon for your response, but the problem is Default.aspx and Index.aspx is separate page. In my case, Index.aspx is just welcome page to show everytime someone access my url. Index.aspx is just a welcome page, not a separate application.

I guess, it's about a code in core library when redirecting to DNN's domain without typing Default.aspx.

Any idea on this ?

 
New Post 5/21/2008 12:07 AM
User is offline Wes Tatters
410 posts
8th Ranked




Re: Child portals errors 

DNN does a whole swag of remapping and URL translation which does assume that default.aspx is the DEFAULT document.

All the friendly URL mappings are set to porint back to default.aspx for starters.

So you should not really have any default document OTHER than default.aspx.

Im not really sure why you need index.aspx as your default - if its just for a splash screen.

Then why not use the built in spash screen capabilities in DNN

Westa

 
New Post 5/26/2008 12:17 AM
User is offline Agung Riyadi
100 posts
9th Ranked


Re: Child portals errors 

Actually, index.aspx is not just splash screen. It's a fully page with some basic information (that's what my client need :(   ).

My DNN site is using 3 languages (bahasa, english, and japanese). And every time a user connect to the domain, it should shows an information page (not default.aspx) but other page with some information like :

... image header
.... English (click here), Bahasa (click here), Japanese (click here)
... footer header

And when client click on those link, it will redirects to appropriate page with it's language. If user do no action, then they only see index.aspx. That's the scenario.

User request --> index.aspx --> 1. English, http://domain/lang/en-us/default.aspx
                                                   --> 2. Bahasa, http://domain/lang/id-ID/default.aspx
                                                   --> 3. Japanese, http://domain/lang/ja-JP/default.aspx

Any idea on this ?

 
Previous Previous
 
Next Next
  Forum  General DotNetN...  Extend It! (Pro...  Child portals errors
 


Forum Policy

These Discussion Forums are dedicated to the discussion of the DotNetNuke Web Application Framework.

For the benefit of the community and to protect the integrity of the project, 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 DotNetNuke.
2. Discussion or promotion of DotNetNuke product releases under a different brand name are strictly prohibited.
3. No Flaming or Trolling.
4. No Profanity, Racism, or Prejudice.
5. Site Moderators have the final word on approving/removing a thread or post or comment.
6. English language posting only, please.

 


Vekkin Solutions
Vekkin Solutions provides complete website solutions and custom module development to churches and small businesses.
www.vekkin.com
Powered by Adcuent®.Com
Adcuent® Consulting & Technology offers custom development web applications and hosting projects under the brand of Powered by Adcuent®.Com
www.adcuent.com
Easily Build DNN Solutions with XMod
XMod makes it easy to build news articles, house listings, custom feedback forms, product reviews and much more - without programming
www.DNNDev.com

DotNetNuke Corporation   Terms Of Use  Privacy Statement
DotNetNuke®, DNN®, and the DotNetNuke logo are trademarks of DotNetNuke Corporation
Hosted by MaximumASP