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

HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0New Portal CanNew Portal Can't Be Viewed
Previous
 
Next
New Post
1/15/2008 4:19 AM
 

Hi All,

I'm still very new in the whole DNN thing, I'm still only learning and playing around.

But now I am stuck. When I create a new portal, I go to Host > Portals...

Then I click on 'Add New Portal', and I add the following details (I also include passwords, but it didn't copy).

Portal Setup


 

 




 Customize





Default Website Template

  Security Settings







 

When I click 'Create Portal', I get the following

There was an error sending confirmation emails - frichthus@gmail.com: The specified string is not in the form required for an e-mail address.. However, the website was created. Click here to access the site.

And when I click on the link, it redirects me to http://newportal/ and displays 'Internet Explorer Cannot Display The Webpage'.

When I create a child portal it redirects me to the root directory e.g. http://localhost:1234/DotNetNuke/

All data does get inserted into the Portals & PortalAlias tables.

I would appreciate any advice.

Kind Regards

Frikkie

 
New Post
1/16/2008 12:28 PM
 

If you are on a local installation in a sub folder, you would need to create a child portal, and the URL would be http://localhost:1234/DotNetNuke/PortalName as long as the root directory path is the first portion of it.

If you are looking to test an additional root site you would need to create a hosts entry to alias the incoming, but the same paths would apply.  http://www.youralias.com:1234/DotNetNuke/


-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.
LinkedIn Profile

Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services
 
New Post
1/18/2008 4:18 AM
 

I think you should understand the different between Parent and Child.

In my opinion, CMIIW, if you choose Parent portal then you have to make sure that your Portal Alias can be PING-ed. If you type "newPortal" name as parent portal then i assume that "newPortal" is a computer name that you can PING from your Command Prompt. If you can't PING to "newPortal" then your DNN will failed to load the website. So, it's easy to understand that parent portal can be :

To test it, go to Command Prompt and do PING to your parent portal.

PING newportal

And then see the result. If it's ok, then the parent portal can be used. If failed, then you can't use that as your parent portal.

If you choose Child portal, then the url should be http://domain/childportalname, so the pattern will use your active domain. Then no need to ping your domain because you have the active one.

CMIIW.

 
New Post
1/18/2008 4:31 AM
 

I think you should understand the different between Parent and Child.

In my opinion, CMIIW, if you choose Parent portal then you have to make sure that your Portal Alias can be PING-ed. If you type "newPortal" name as parent portal then i assume that "newPortal" is a computer name that you can PING from your Command Prompt. If you can't PING to "newPortal" then your DNN will failed to load the website. So, it's easy to understand that parent portal can be :

To test it, go to Command Prompt and do PING to your parent portal.

PING newportal

And then see the result. If it's ok, then the parent portal can be used. If failed, then you can't use that as your parent portal.

If you choose Child portal, then the url should be http://domain/childportalname, so the pattern will use your active domain. Then no need to ping your domain because you have the active one.

CMIIW.

 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0New Portal CanNew Portal Can't Be Viewed


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