From ea7a53c07a51a0d616508c064480b6b98ee7d073 Mon Sep 17 00:00:00 2001 From: Stefan Ritt Date: Tue, 15 Jul 2003 12:15:40 +0000 Subject: [PATCH] *** empty log message *** SVN revision: 583 --- doc/ChangeLog | 7 ++++++- doc/config.html | 10 ++++++++++ doc/wishlist.html | 2 +- 3 files changed, 17 insertions(+), 2 deletions(-) diff --git a/doc/ChangeLog b/doc/ChangeLog index 8cebbd6a..b9dc35e9 100755 --- a/doc/ChangeLog +++ b/doc/ChangeLog @@ -12,9 +12,14 @@ Version 2.3.9, released June xxth, 2003 - Send attachments as email attachments - Don't display more than 10 email recipients - Made default for "Filteres browsing" zero -- Added "Format = width, size, flags, css1, css2" +- Added "Format = width, size, flags, css1, css2", this requires + an update of the default.css file - Display error if email notification fails - Added execute on new/edit/delete functionality, added -x flag +- Fixed problems with coloring hyperlinks in the find result page +- Reply in elog utility now puts "> " in front of old text +- elog utility can edit old messages (with new "-e" flag) +- Added "loggin level = 1,2,3" Version 2.3.8, released June 4th, 2003 ====================================== diff --git a/doc/config.html b/doc/config.html index a74fe12e..08af8aa4 100755 --- a/doc/config.html +++ b/doc/config.html @@ -206,6 +206,16 @@ name you can get from your email program or your local system administrator. This option specifies a filename which logs all login/logout activities and successful user connections for logbooks with user level access.

+

  • Logging level = 1 | 2 | 3 +
    +Specifies the logging level:

    +

      +
    • 1: Log only login and logouts +
    • 2: Log also write accesses +
    • 3: Log also read accesses +
    +

    +

  • URL = <http[s]://host.domain[:port]/[subdir/]>
    If one of the three cases is true:

    diff --git a/doc/wishlist.html b/doc/wishlist.html index 6a99e3c5..7661cb9c 100755 --- a/doc/wishlist.html +++ b/doc/wishlist.html @@ -47,8 +47,8 @@ starting at the items with the most votes. You can vote for a feature, or sugges Edit existing messages with elog utility1 Implement multi-line attributes1 Add more detailed user logging, like $user $date $logbook $ID read/edit/new/delete1 -More elaborate attribute formatting, see here1 Derive attribute options from list of entries of another logbook1 +Separate administrators for different logbooks should only see their section in elogd.cfg2