I just updated ELOG using the latest elogd.c, and now my Quick Filters seem 
to stop working after the first or second filter attempt. I find that if I 
allow fewer quick filter options it seems to work more consistently. For 
example:

Example 1-
Quick filter = Date
The date filter will work without a problem no matter how many times I use 
it.

Example 2-
Quick filter = Date, Category, Status, Priority
The first filter I use will work, but upon trying a new filter, or just a 
new option in the same filter, all options return to "All Entries" and no 
filter options have any effect on the view.
If I exit the log book, and come back in, it works for the first filter 
attempt, then stops again.

This used to work fine prior to the update. I should also mention that the 
original installation of ELOG was from the Debian package. At that point, 
nothing was where the documentation said it should be (e.g. elogd.cfg was 
called elog.conf and was placed in the /etc/ directory). Everything worked 
fine, so I left it alone. When I recompiled with the newer elogd.c, 
anything that required a path was hosed, so I now have to specify the 
resource directory and the path to the conf file when starting ELOG. I 
don't know why this would affect the Quick Filter, and I'd assume that it 
would just stop working all together. Also, when I recompiled using "gcc -
O -o elogd elogd.c", I received the following warning:

elogd.c:546: warning: conflicting types for built-in function `logf'

Any suggestions?

Thanks!
Todd

Hi 
I followed copied the example config provide to run on my server .
Apparently , the author field was blank when i do a reply .
I was hoping to get it to be the actual reply author.
Just like the way the forum is done up.
Please help ..

Are you using Remove on reply option ? 

regards

With the "Preset text = " specified, when re-editing a logbook entry (say to
correct a spelling error) the text of the "Message" is replicated and placed
directly below the original text.

Commenting out the "Preset text = " line prevents this behavior.  this
occurs under both FireFox and IE6.0 clients.

Something to add to the wishlist:

- Type <attribute> = user

This would define an attribute as being of the type "user" which is a list
of login id's as defined in a password file or on the "Login user =" line. 
In a dataentry form the presence of this ATTRIBUTE would result in a
picklist of loginid's and/or fullnames.

I have an attributes defined as:

 - Attributes = Author, PlannedDate, FunctionalArea, Operation, Category,
HardwareName, Significance, EmailNotify, LastRevision, Subject

I have PlannedDate defined as:
 - Type PlannedDate = date

When I use the following statement:
 - Thread display = $subject, planned for $PlannedDate. Last revised:
$lastrevision

I get the following in my THREADED logbook view:

"Adding new services, planned for 1090519200. Last revised: Thu Jul 15
18:03:52 2004"

Note that the ATTRIBUTE $PlannedDate prints as a (I am guessing) serialized
date and is not formatted.

I'm not sure if this is manifested elsewhere.

Hi Stefan 
YOu have been a great help on the Elog problem solving .
I have another sort of bug , when i have a attribute type as date.
And i have fixed the attribute on reply , i actually get a string of 
number when i reply , and the date becomes not the orginal date in the 
first message.

So the way i work ard is that i did not place the date field in the fixed  
attribute reply which i will run the risk of pple modifying that entry .
Can this be fix?

Thanks 

> > A temporary fix for this is to set summary lines = 0
> 
> Right, that's the only way. I would call this "permanent fix" (;-)

I would too - and it actually produces the output that I wanted to see anyway.

Thanks!

> > Ok, I think I see now.  I was assuming it applied to the entry form as well.
> 
> Well, good idea. I implemented that. Have a look at this forum (just hit reply to this
> entry) and you'll see it. I'm not completely happy with it (at least on small 1024x768
> screens), but it's configurable anyhow. New version under CVS.

Now that creates an interesting display - especially with the icons and radio buttons. 
But it works!

Thanks.