Dotnetnuke: Portal Redirects to Default Portal in Local Machine

I have encountered an issue with Dotnetnuke about a portal redirecting to the default portal.  The Dotnenuke site have two portals, one is Portal 0 and the other is Portal “private” (let’s name it that).  Portal 0 (default) is accessible via http://localhost and the private portal is http:/localhost/private.

I redeployed the site using a different port, which is port 8081.  When I access http://localhost:8081, i want to see the private portal and not the default portal.  This is where the issue comes in – accessing http://localhost:8081 redirects to the default portal.  To solve this issue, here are the following steps I did:

1. In the private portal – Site Settings, I created portal alias “localhost:8081″
2. In the Host Settings, I set the default portal to be the private portal
3. In web.config – I added <add key=”UsePortNumber” value=”true”/>

After making these settings, I tried http://localhost:8081 again and voila! I can see now the private portal contents.

Tags: dotnetnuke, fixes, issues

You can leave a response, or trackback from your own site.