Hi guys,

I have been battling with Parent/Child Portal installation since yesterday. It made me delete diff. versions and install another but to no avail.

I just go over it and realized that it's a bug in it or all versions (anyway i found this in DNN 4.4.1)

If you installed DNN afresh on IIS server with non-default HTTP port (say 3333), after installation, check the available Portals info (i.e. Host privilege: Hosts->Portals), you will see that you installation is referenced with default port.

See this:

My Website

127.0.0.1/dotnetnuke 127.0.0.1:3333/dotnetnuke

1

2

0

0.00

Though you can add alias to it, it will try using the above (wrong port--port 80) when installing another parent/child portal thereby making your new parent/child portal unavailable.

Though i found out that the folders where created, I couldn't reach my portals.

-- When I changed IIS to port 80 default, I was able to create Portals hitch-free. When i changed port to initial 3333, all accesses to portals failed.---I restarted DNN, IIS and so on but futile.

 

NOW I HAVE TO CHANGE MY APACHE PORT NUMBER FROM DEFAULT 80 to something else. I stopped it to detect this defect in DNN.

Betterstill, they should make the 1st alias in the SUPER PARENT DNN editable.

I hope it's being looked into in future versions.

MIKE

If you want DNN to use the port number, set the UsePortNumber setting in the appSettings section.  (I think that is the name of the key).

---

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


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