Re: Page history and author audit function

At 14:19 07/03/2005, you wrote:
>Is it possible to get the username of the publisher and the author
>of a specific published state of a jahia page? We want to realize
>something like:
>
>1. Show every published version of a page since it's creation (as a
>table for example)

This should be possible as we do it in the versioning engine. So please 
refer to the code in the versioning engine if you want to reuse it within a 
JSP template.

>2. Show the author & the publisher + the date for a specific
>version of this page.

The date is not a problem as we store the date within the version number. 
For the Author and Publisher it is more complicated as there is no 
"metadata" support for each contant object in Jahia 4.0.x. This feature 
will be (=is already) added for Jahia 4.5. Furthermore you do not have a 
unique author/publisher per page but for each content object on a page. The 
same is true for the versioning. Even if the GUI were done to restore 
versions on a page per page basis (more easy to use), the back-end stores 
incremental versions per content object. So if you modify only one 
container on a page, we will only version the changes for this container, 
the page field and thoter containers on the page being intact and exactly 
the same.

>3. Don't show the actual changes (like a diff) but the commit
>message which is used in the publish menu and the notification mail.

For the moment we do not store/log the workflow msg. So this may be an 
enhancement to bring to the platform for a next release.

>The background of this is to give the users of the intranet portal
>the possibility to see in what kind the page changed and who
>changed it.
>
>I'm hoping that there's some functionality that I can use from the
>versioning functionality jahia allready uses to show this data. But
>I did not see any link between author/publisher and a specific page
>state. Also the commit message doesn't seem to be available for
>later lookup. Is this true?

If there was such information in Jahia 4.0.x we would have used them in the 
versioning module. But that was not the case. All the information we have 
are present. The rest should be added by modifying the platform (= for a 
next release). Globally this means:
- adding automatic metadata (author, last modifier, last validator, 
creation date, publishing date, etc..) -> done for Jahia 4.5.
- modifying content objects descriptions (today the content object you 
retreive have no "human speaking" description (= only id in the database or 
name of the list/field in the template). So this is not easy for the 
end-user to know which object was modified on a page (without using some 
visual diffs). We are refactoring the Jahia definition in order to better 
support the new standard JSR170 content definintion. So this will be, at 
least partially, added in Jahia 4.5
- Log/store history: another customer wanted to contribute a full 
refactoring of the Jahia events/logging system. This would be great as this 
system is quite old and clearly needs to be refactored. So let's see the 
result. Else someone else will have to do it one day...

Best Regards
Stéphane