Audit Trail Functionality

[GoogleCodeExporter]

Hi Eugene,

I have a feature request. I would like to see a method built for
maintaining an Audit Trail. Basically just a way to log what users used
what module, what changes they made, when they made them, and if the
changes were successful. The log should also include any attempts to log-in
and it would be nice if we could choose how detailed the logging info was.
It should have the ability to save database queries as well.

The audit system should be accessed similarly to the current debug system
you have in place. The intention of this feature is to allow the senior
admin to record what users and other admin are doing on the site, and to
record any failed and/or successful log-in attempts.

This is something I can work on if you like. I was thinking it should be a
library. What do you think?

During the pre-release, please update your files with the latest svn before
reporting a defect
-----

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?

Please use labels and text to provide additional information.

Original issue reported on code.google.com by rmorga...@gmail.com on 16 Dec 2008 at 6:31

[GoogleCodeExporter]

Hello Randal,

So it's like a event hook? Registered in a database too?
Can you try so that I can see?

Thanks again.

Original comment by heriniai...@gmail.com on 17 Dec 2008 at 12:00