I have been battling with Portal Aliases for most of the day and my Google searches indicate that they have been a source of problems for years.  With most development platforms, you simply point your domain name to a location or use the IP address and optionally a port and viola.  If you use relative URLs for images, stylesheets and the like, the application really does not care much what DNS name is used.  If the app did care for some reason, the DNS name is easy enough to get from the URL.

Maybe my Portal Alias troubles would be less frustrating if I understood why they are needed.  What is it that I am missing?  (Honestly, this is not meant to be a design criticism, but to help me understand).

Thanks -

I have around 30 or so different domain pointing at PokerDIY. To get 301 redirects working properly I also have to add "www.pokertourneymanager.com" AND "pokertourneymanager.com" (don't ask me why - I spent a long time playing around with Fiddler getting this working, but it was not doing a proper 301 redirect without this. This is in conjunction with URL Master - I am not sure where the problem is).

Anyway, perhaps it could be more intelligent - if you have not child portals then perhaps it could switch off? Not many large websites run with multi-portal functionality for performance and admin reasons.

---

Entrepreneur

PokerDIY Tournament Manager - PokerDIY Tournament Manager<
PokerDIY Game Finder - Mobile Apps powered by DNN
PokerDIY - Connecting Poker Players