Wouldn't it be easier/more the ez way to create a new attribute "logger" that tracks that ? No need for a separate table and you put that only on the content you want to track.
For those of us (ie. me ;) that have some difficulties to follow all the nice extensions you spoil us with, could you remind me what this content object edit extension handler does ?
If you're having objects that can be edited by many people (eg. in a wiki), other people's changelog notes can get deleted by accident. I believe in some cases it's better to just have a changelog attribute, in other cases not.
You can read more about the new content edit extension handler functionality at http://pubsvn.ez.no/nextgen/trunk/doc/features/3.8/content_edit_extension_handler.txt ( I didn't invent this one ;-) ).
Xavier, you were right about the attribute. If we have a custom datatype (based on the text field) that clears it's own attribute content whenever a new version of the attribute gets created, then each object version can contain it's own changelog note. It will be very easy to display those notes eg. in the content/versions view in an additional column.
Thanks for bringing me back on the right track with your good advice! :)
