The lognode module is an attempt to log events occuring on a node.
The types of events logged are:
* create: logs an event when a node is created.
* update: logs an event when a node is updated.
* delete: logs an event when a node is deleted.
* new revision: logs an event when a new revision is created on a node.
How is this different from dblog?
Dblog is a logging system while with lognode, you can see all changes your
content has been through.
How is this different from revisions?
Their goals are different.
With revisions, you'll not know what has changed if the user do not click on
"Create new revision". Then, if I update a node, one will only know that the
node has been modified, but will not know WHAT has been modified. The only way
to know what what was changed is to click on "Create new revision".
But not all users are allowed to do it.
With lognode, each time a node is modified, you know what has changed. But
let's explain what we understand when we say "MODIFIED".
With drupal (dblog) , every time you save a node, the node is marked as
"updated", even if NOTHING has really changed within the node. But with lognode,
the node is saved in logs ONLY when we detect something has changed.
Then, you're able to know the real life of a node. What the node has been