Products

Solutions

Learn More

Partners

Community

Blog

About

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 ...The Site Alias Name You Specified Already Exists. Please Choose A Different Site Alias.The Site Alias Name You Specified Already Exists. Please Choose A Different Site Alias.
Previous
 
Next
New Post
1/2/2015 1:32 PM
 
Panagiotis,
please understand that same symtoms might have different causes, the old thread is NOT related.
Thanks

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
3/18/2015 10:11 PM
 
Sebastian,

You wouldn't have a pointer to the jira issue?

The problem is obvious (and exists in 7.4.0)

the problem is in PortalAliasController.cs, the logic is not correct, around line 103, you find this (BTW this is not the only problem in this code)
//remove the domain prefix ( ie. anything.domain.com = domain.com )
if (httpAlias.IndexOf(".", StringComparison.Ordinal) != -1)
{
strPortalAlias = httpAlias.Substring(httpAlias.IndexOf(".", StringComparison.Ordinal) + 1);
}
else //be sure we have a clean string (without leftovers from preceding 'if' block)
{
strPortalAlias = httpAlias;
}
//try an explicit lookup using the wildcard entry ( ie. *.domain.com )
portalAlias = GetPortalAliasLookupInternal("*." + strPortalAlias.ToLower()) ??
GetPortalAliasLookupInternal(strPortalAlias.ToLower());
if (portalAlias == null)
{
//try a lookup using "www." + raw domain
portalAlias = GetPortalAliasLookupInternal("www." + strPortalAlias.ToLower());
}


if you already have a portal with an alias of "blah.com" and then try to create another portal with "broken.blah.com" I am pretty sure that this code will consider these 2 strings to be the same and thus the error. I know that if you try this in practice, this code will not let you move forward. I think this code is trying too hard and drawing incorrect conclusions.

Just above, there is this:
//domain.com and www.domain.com should be synonymous
if (portalAlias == null)
{
if (httpAlias.ToLower().StartsWith("www."))
{
//try alias without the "www." prefix
strPortalAlias = httpAlias.Replace("www.", "");
}
else //try the alias with the "www." prefix
{
strPortalAlias = string.Concat("www.", httpAlias);
}
IMHO This is not the best assumption. No where is it REQUIRED that www.blah.com and blah.com be the same place. WWW is just another hostname for a domain. There is a CONVENTION where people set these up to be the same. But by no means is this required.
 
New Post
3/18/2015 10:18 PM
 
Never mind, I found the jira issue: https://dnntracker.atlassian.net/brow...
It appears to have been fixed in 7.4.1.... 7.4.0 has been a challenge, looking forward to all the bug fixes... Still loving my DNNTurboSQL!
 
New Post
3/19/2015 4:28 AM
 
I am glad you were able to find the issue, you may try the fix on a test environment using a nightly build of DNN.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...The Site Alias Name You Specified Already Exists. Please Choose A Different Site Alias.The Site Alias Name You Specified Already Exists. Please Choose A Different Site Alias.


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.

Content Layout

Subscribe to DNN Digest

Subscribe to DNN Digest

DNN Digest is our monthly email newsletter. It highlights news and content from around the DNN ecosystem, such as new modules and themes, messages from leadership, blog posts and notable tweets. Keep your finger on the pulse of the ecosystem by subscribing.  

What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out