I've seen that problem before but only when an upgrade was not correctly done e.g. in one case I accidentally did a test install of 7.2.1 and then copied the files over an older copy (as my install had cleaned up some files that exist in an upgrade package it caused a failure -and the most noticeable case was that the gettingstarted page popped up each time). I've never seen this happen when an upgrade package was used - could you check you used the right package? As for the file management, this is another sign of a failed upgrade as we introduced the document asset manager (DAM) as a replacement for file manager. During a typical upgrade the old file manager instances get replaced with the new DAM but it appears this hasn't happened for you - you can fix this by dropping a copy of the DAM module onto that page (you may need to go to host->extensions and edit it and allow it to be assigned to a portal). Note: you might want to check the upgrade log (http://www.dnnsoftware.com/community-...) to see if it offers any information on what went wrong during upgrade.

---

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US