$egLoopsEnabledFunctions - Backwards settings
All functions are enabled by default, but there is a setting to enable functions. This logic is broken. There really should be a setting for which functions to disable.
In your opinion, what is broken about this? You can have problems both ways, when only having a setting to enable or disable certain functions. The reason why I chose to allow enabling only certain functions instead of defining which ones should be disabled is because when introducing new functions, the admin who is updating the extension might not realize that there are new ones. Suddenly users of the wiki could start writing new templates using that function which should actually be disabled. This doesn't happen when having the option for exclusively enabling because here all previously enabled functions will still work, only newly introduced ones might not until some admin explicitly adds them. Anyhow, admins should always read the changelog when updating extensions to adjust configs if desired.
Last edit: 21:51, 12 September 2012
I can see Alexia's point on the extension. I've had to do some edits to help build this extension into my wiki farm. If you don't mind, I would like to commit it to the repo for your review when I finish making sure it's hundred percent ready.