ACL mistake

[Arakattack]

Ok, so I was trying to figure out the ACL half on my own, and half according to a tutorial. I made the mistake of getting ahead of my tutorial, and not thinking quite so literally about the meanings of the user groups. I went to my root channel, and changed permissions for @all to Deny access to Write ACL. Now, I also have Admin as Allow Write ACL, but now I cannot edit the ACL for any of my channels, even as the SuperUser I can only change the ACL for @Admin in the root channel, and not for anyone, in any other channel. All the options for @all's ACL are greyed out (I assume because @all (which includes @admin) are denied the ability to edit ACL)

I think I derped pretty hard doing that. Also, my server is remote, it's not running on my machine, so I don't think I have direct access to the ini files.

Is this borked and I have to start over?

[kissaki]

SuperUser bypasses the ACL and can *always* be used to fix the setup.

[Arakattack]

In theory, I'd agree with you. But when I'm on SuperUser, and I try to alter the "@all" permissions for my root, all the options are greyed and locked in their current states. It won't let me alter them. If it helps in a few hours I can post a screen grab.

[ngollan]

You cannot change that "root" @all entry, it's a baseline to always have working defaults (IIRC it's even hardcoded). To change those, you add a new @all entry with the proper overrides and inheritance.

[Arakattack]

Okay, thank god! I thought I had somehow removed my own ability to edit ACL's because I'd set @all in Root to deny access to ACL's, and suddenly I couldn't modify @all, and I thought I'd permanently broken it! Thank you!

-Shaun.