Best practices for implementing a trust filter

[eluser]CroNiX[/eluser]
My point was you don't need to "hack" codeigniter.php. You could create a new one and place it in /application/core and CI will use that one instead. A slightly different approach than extending the controller.

Sure you can present them with a nice message and headers. Just output them and then die() immediately after, or exit(), to stop the rest of the CI code execution cycle (which is essentially what show_error() does).

Yes, this is a nice feature, but I doubt CI would include something like this as it would rarely get used (is my guess, since I haven't been able to find a similar discussion, so not much demand). They don't even have an official CI ACL library, yet. They just like to have the bare essentials to keep bloat down and let the programmer add in what they need. They're not trying to be Zend.