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...Upgrading DNN P...Upgrading DNN P...Upgrade to 5.06 - Hostname Nolonger RedirectsUpgrade to 5.06 - Hostname Nolonger Redirects
Previous
 
Next
New Post
11/17/2010 6:45 PM
 
Hello,

I've just tried upgrading to version 5.06 from 5.05.1 and have experienced the following issue.

The URL http://example.com is no longer being redirected to the home page. Instead the ErrorPage.aspx page is being displayed but no exception has been generated. As a result it's empty. When the "Return to Site" link is selected DNN works as expected.

To work around the problem code has been added to ErrorPage.aspx to redirect automatically.

Has anyone else experienced this problem? What could have changed in 5.06 that would cause the ErrorPage.aspx to be displayed without an exception having been generated?

Any ideas appreciated.

Thank you,

James


 
New Post
11/17/2010 7:25 PM
 
Is http://example.com the portal alias that you have defined for your website? or do you have something else as the alias?

Chris Hammond
Former DNN Corp Employee, MVP, Core Team Member, Trustee
Christoc.com Software Solutions DotNetNuke Module Development, Upgrades and consulting.
dnnCHAT.com a chat room for DotNetNuke discussions
 
New Post
11/18/2010 3:58 AM
 
Chris,

The http://example.com portal alias was working correctly. The upgrade was applied and http://example.com displayed the ErrorPage.aspx page. No other changes have been made to the environment.

Looking at the code in the ErrorPage.aspx the page is being displayed without any "status" query string, or any exception being available to display. As a result the Catch block is being executed, which as the comments say should never happen. All I've done as a work around is change the code in the catch block to perform a redirect to http://example.com. However it's not a robust long term solution.

Thank for your help,

James
 
New Post
11/18/2010 8:00 AM
 
Have you looked at Admin --> Site Settings (when logged in as host user) or in the PortalAlias table of the database to see if the Portal Alias entries have changed since the upgrade?

Also, in the AppSettings section of the site's web.config file, what is the value of the UsePortNumber setting?

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner
 
New Post
11/18/2010 8:09 AM
 
Bill,

The UsePortNumber element was commented out. I've removed the comments and set it to true. It has not made any difference.

The PortalAlias table contains the same entries as it did before the upgrade but also contains many more new entries that seem to have been added automatically.

Thank you,

James
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...Upgrade to 5.06 - Hostname Nolonger RedirectsUpgrade to 5.06 - Hostname Nolonger Redirects


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