The clean install works perfectly (can even be bodged to work with our mssql cluster, ignore mssql for now however
However, when upgrading a copy of the production 1.6.1 (mysql) database, all seems to go well until we visit the /admin pages:
"Sorry, but you do not currently have permissions to do that (Change site configuration)"
Looking at the database, it seems all the roles have been assigned correctly. Are there known problems with converting 1.6.* databases to the new roles system?
Are there any hacks available to get an admin account in there?
We are using the ntlm authentication module (i.e. with ActiveDirectory ldap and auto login via IE or not-so-auto login with FireFox), it seems to work fine as I got automatically logged into Moodle after supplying credentials to the browser. However, it no longer recognises me as an admin user.
So neither the primary admin user nor my personal admin account have the admin role correctly applied.
EDIT:
This is Weird with a capital WTF...
I tried sneaking up on 1.7b from behind: I changed the config to use the clean 1.7b database, then logged in as admin, no problems. Then I changed the config again to use my copy of the live 1.6.1 database that was upgraded by 1.7b. Somehow my admin's web session stayed alive and now it seems to recognise me as an admin!
EDIT again:
OK, that just seemed to confuse it into giving me admin permissions for that session. (I could see that all the admin accounts clearly had the role assigned).
After logging out and in again, I'm back with no admin access.
