Thread:Extension talk:Lockdown/Why is there a "Warning" for 1.16 on the main page?

Shouldn't the warning be modified to read "Possibly broken for 1.16 if client-side caching is enabled and users don't read the instructions"?

It seems like almost all the issues that people are having are client-side caching or RTFM failures.

I use a combination of Lockdown for Action and Special Page lockdowns, and Extension:SimpleSecurity for namespace management. I have found this to be a rock-solid combination for my relatively simple needs since 1.14 and through 1.16.1, including a public-facing CMS as well as completely private extranet sites with multiple (albeit relatively simple) permission needs.

For those with the freedom to hack and patch their source code and the time to configure things (and work out all sorts of possible Javascript, skin, database, and administration issues), Halo Access Control List may be a possible option, but I have yet to be able to get it to work in a way that meets my needs.