[eluser]Rick Jolly[/eluser]
[quote author="dcunited08" date="1228435527"][quote author="Rick Jolly" date="1228434688"][quote author="dcunited08" date="1228429568"]Overload the Loader class (create MY_Loader)...
[/quote]
Please don't.
In the name of transparency and consistency, put all application logic that must process on every request in the constructor of a parent controller.
How would any future programmer know why a view wasn't loading? Why sprinkle bits of application specific logic throughout CI system files?[/quote]
I thought the MY_Loader would be in the Application/libraries folder. How would the constructor know what view is being called? Honestly, the best bet would be to limit access to controllers not to views because by the time it is going to the views it is too late to worry about rights to data or to really handle a failure of rights well (send them to login, show a different view, etc..)[/quote]
Yea, MY_Loader would be in applications, but it is a CI system file. Obviously, you are correct that the view would be unknown. I was thinking controller methods, which we both think would be a better way to go.