i've done a 4.9.1->5.0 upgrade and do not have the portalaliases issue (will check 4.9-5.0 shortly).

The Admin > Extensions and Host > Module Definitions menu options are correct - extensions cover authentication, skins, containers, languages and modules whereas module definitions just cover modules. In extensions you can configure extension permissions whereas under modle definitions you can configure many other settings such as the module controls and availability to portals. The two options need to exist so that portals can delegate a certain level of control to portal admins (or other users)

Cathal

To add to the PortalAlias issue.  I can only edit the portal alias of sites I am logged into even though I am logged in as host.  In DNN prior to V5.0, I could log into any portal as host and edit the portal alias of any other portal on the installation. 

This is a very important feature to keep.  As a host, I tend to break up portals from time to time.  I will take a DNN folder, duplicate it in Windows and make a new site from it.  I then go and delete all the portals I no longer need and then I have a stand alone site.  I also bring to live staging sites from time to time.  In either case, I usually need to edit portal aliases of portals that I am not logged into just so that I can log into them.

oliver,

would you mind to log this issue in the public tracker (2nd from top) at support.dotnetnuke.com, please. Thank you :)