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 ...From localhost to actual siteFrom localhost to actual site
Previous
 
Next
New Post
11/9/2007 11:31 PM
 

I've had this exact problem occur to me (if you search the forum's many months back) and no one offered an explanation.  After many different ways, I gave up and tried a later version of DNN.  And it worked perfectly. 

My opinion is there is a bug in the code, which is why you'll get little response.  It seemingly gets fixed in later releases.  Thus, I no longer rush out and upgrade, but now take the approach to wait till 3 or 4 minor releases are made till I take the plunge.  Which necessitates the need for a test environment if your seriously running DNN in production.

JMM

 
New Post
11/10/2007 3:33 PM
 

Hmm, I doubt there's a bug that causes this behaviour. Having PortalAlias correcctly functioning is pretty crucial to DotNetNuke, so it isn't likely to be broke in a release version.

That said, you still have your problem... Have you made sure the cache is refreshed after you added the Alias? Otherwise the PortalAlias might not match the root of the dnn installation exactly. For example if you have it installed in a virtual folder, the alias should be: www.yourdomain.com/virtualdirectory

 


Web applications, DNN websites, modules, skins and support
 
New Post
11/10/2007 9:53 PM
 

Stefan,

I appreciate your response.  But I just installed 4.7.0 and the problem explained earlier exists.  Everything I type into "Portal Alias" gets re-routed back to "localhost" or whatever I chose when I installed DNN.

I wiped it out and instaled 4.6.3 and it works perfectly.  As expected.

Wiped it out and tried 4.7.0 again and the problem exists.

Standard install, nothing special, following the instructions.  I've installed DNN probably 1000 times and this issue has happened to me only once before in the 4.3.x version.

Just my 2 cents.

JMM

 
New Post
11/21/2007 3:13 PM
 

For what its worth, make sure your host headers are defined correctly in the IIs properties for the instance of your web site and stop/start it after your changes. I would think localhost would be fine on the web server as long as its pointing to its own static IP address or its loopback address. I had a similar problem going from production to test and these were the underlying issues that caused me grief. Peter

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...From localhost to actual siteFrom localhost to actual site


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