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 ...Add Alias and Logo/Icons Reset to <None Specified>Add Alias and Logo/Icons Reset to
Previous
 
Next
New Post
7/10/2007 7:14 AM
 

Thank you for quickly mentioning this.

I was just thinking: what's next? Now the answer: 4.5.4. (for the StyleSheet Saving issue causing the Logo to revert to <None Specified>, anyway).

I only hope my other issue: missing Module Title Bar Icon resetting to <None Specified> on ALIAS creation - is related, connected to or otherwise found reproducible elsewhere.


If a problem can be solved, there's no use worrying about it.
If it can't be solved, worrying will do no good.
 
New Post
7/10/2007 7:48 AM
 

Here's one possible glitch: I made a full back up of my installation, then tried to Add ALIAS again. Only this time, I tried to do it differently.

I swept into Internet Information Server (IIS) and first added the new DotNetNuke portal ALIAS here, called Host Header in IIS. (Properties > [Web Site] > Advanced > Add).

When I setup for the DNN ALIAS in IIS first, then added the ALIAS in DotNetNuke next (Admin > Site Settings > Add New HTTP Alias), I lost no DNN settings. The Logo and Module Title Bar Icon File Name settings remained as they were set. 


If a problem can be solved, there's no use worrying about it.
If it can't be solved, worrying will do no good.
 
New Post
7/10/2007 8:23 AM
 

Brett,

adding the domain to IIS web site is always recommended, otherwise you cannot switch to the new portal/alias.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
7/10/2007 9:30 AM
 

Yes, Sebastian. Even making sure DNS resolves to the new Host Header before the DNN Alias is set makes good sense, too. For the record, I suppose the logical sequence is:

DNS (A Record)
IIS (Host Header)
DNN (Alias)

Assuming your IIS has a default page that handles domains that are not running just yet.


If a problem can be solved, there's no use worrying about it.
If it can't be solved, worrying will do no good.
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Add Alias and Logo/Icons Reset to <None Specified>Add Alias and Logo/Icons Reset to


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