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

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Bug in 4.3.6 for sites with custom portBug in 4.3.6 for sites with custom port
Previous
 
Next
New Post
11/18/2006 6:22 PM
 

In web.config you can add an application setting:

    <add key="UsePortNumber" value="True" />

There was a change in 4.3.6 to strip the port number by default when matching the PortalAlias. This was done to prevent development environment issues with the Cassini web server which generates port numbers dynamically ( resulting in constant support issues logged in Gemini and in these forums ). I believe we could improve this by checking the Request.IsLocal attribute as well ).


My comments are my own and are offered WITHOUT PREJUDICE

Shaun Walker
http://www.siliqon.com
 
New Post
11/18/2006 6:31 PM
 
The other thing you could do is add the domain name without the port number to the PortalAlias table so that the lookup works correctly ( I am not sure which solution is more appropriate for your specific environent ).

My comments are my own and are offered WITHOUT PREJUDICE

Shaun Walker
http://www.siliqon.com
 
New Post
11/19/2006 11:42 AM
 
Had the same problem and the change in the web.config solved it.  Thanks!
 
New Post
11/20/2006 10:29 AM
 

That is a good feature to have for sure. In addtion to checking if local or not, upgrades NEED to add the change to web config if ports detected or at least inform the user. I was completely in the dark on this one as there was nothing in Gemini that I could find about the change. It was a pretty big change with no documentation on it...

Still, a very useful feature...

 
New Post
11/20/2006 1:25 PM
 

Oh, I should add that adding the change to the web.config fixed my site up nicely.

I also got it working in IIS7 on Vista RTM in classic mode if anyone is interested... :)

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Bug in 4.3.6 for sites with custom portBug in 4.3.6 for sites with custom port


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