• I can't find any simple way to return to the "every entries" display .. may be the link has to be switched to a checkbox to be actived or not
  
• I found a way (at least)... following the "config" link, doing nothing and coming back restores the view .. this is a feature now, but when a less tricky mechanism will be implemented will become a bug
  
  

" shortcut .. it will be very usefull

PS:
Writeing the wish above I noticed that the [ *] is interpreted as an item also otside the LIST tag .. so .. or the LIST tag is optional, or the [ *] should not be interpreted outside of it ... it's another bug ? P

• this is a real bug (see attachment).. if a file is referred inside the text (as shown in elcode docs) it is correctly not shown when in single message view, but it remains visible both inline and as attachment in the full list view
  
• it would be nice for the user having, as in the single message view, the possibility of show or hide a single or all the attachements of a single message ..
  

I have several date-fields defined in my logboek. But when I click the icon and select another month the pop-up 
window get's filled  with the contants of the logboek instead of the date-selection.

Date format = %Y%m%d

Ok this really is 2 questions.

1)
I have been running ELOG on FreeBSD no problem for a year now,
but this new version 2.5.8-x doesn't seem to wanna work, it compiles fine 
with a few warnings (see attached logs).
But has issues with password files, now it shows message "Can't open 
passwords.pwd" for all my logbooks. It did convert the password files to 
xml format. I had a good hard look at file permissions and config file with 
no luck. So I went back a version and compiled 2.5.7-1 which works just 
fine with old password files. So something with XML & FreeBSD?...

2)
Version 2.5.7-1 (maybe this has been fixed in 2.5.8?)
When I run a ./elogd -C http://elog.blah.here:88 it clones the config file 
just fine, also seems to copy over all logbook entries.
But once I look through them there's a fault with one of the fields it 
copies over, so entries never show up.

It should be:
========================================
Date: Tue Mar 01 19:41:29 2005
In reply to: 24
Work done by: someuser
Work done at (dd/mm/yy hh:mm):  1/03/05 3:30pm
Downtime duration: 0 min
Planned: Yes
Reason: Normal work
Attachment:
Encoding: plain

But once cloned it looks like this:
========================================
Date: Tue Mar 01 19:41:29 2005
In reply to: 24
Work done by: someuser
Work done at (dd/mm/yy hh: m):  1/03/05 3:30pm
Downtime duration: 0 min
Planned: Yes
Reason: Normal work
Attachment:
Encoding: plain


For some reason it looses the "m" so line 4 instead of having
"hh:mm" has "hh: m"


Cheers,
GL.

Hi

I've written a powershell script parse a html table that contains old log book data that i would like to import to a elog book.  I've attached a example of the output.

When i attempt a import i get this error

"XML file does not contain <ENCODING> element"

The file does contain an encoding for utf-8  I've tried converting the xml to ANSI and ISO-8859-1 encodings but i get the same error.

is there something obvious that I'm missing?

here is the config of the log book:

[WLTST]
Theme = default
Comment = Test Logbook
Attributes = Author, Object, Action
Comment Author = Username
Comment Action = What
Comment Text = Why
Required Attributes = Author, Object, Action, Text
Page Title = Test Logbook
Reverse sort = 1
Quick filter = Date, Type

When an attachment is later added to an exisiting entry, we see that the string "Uploaded <date>" has the wrong
time: in our case it is one hour into the future.
I'm testing it now here in the forum.

I can reproduce it in this forum: the Uploaded time should have been 10:35, but it shows 11:35.

Cheers, Andreas