Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 211 of 234  Not logged in ELOG logo
icon4.gif   Bugs in newer updates w/ Debian install?, posted by Todd Corsa on Thu Jul 22 16:50:19 2004 
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
    icon2.gif   Re: Bugs in newer updates w/ Debian install?, posted by Stefan Ritt on Wed Jul 28 21:49:32 2004 
> 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.

Can you try if you can reproduce the problem with the current version? I tried
your settings and could not reproduce it. I remember that I fixed some problems
with quick filters, but that was some time ago (Apr 04). If the problem
persists, can you send me your exact elogd.cfg?
       icon2.gif   Re: Bugs in newer updates w/ Debian install?, posted by Todd Corsa on Wed Jul 28 22:12:03 2004 
> > 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.
> 
> Can you try if you can reproduce the problem with the current version? I tried
> your settings and could not reproduce it. I remember that I fixed some problems
> with quick filters, but that was some time ago (Apr 04). If the problem
> persists, can you send me your exact elogd.cfg?

Recai Oktas replied to me and let me know that I needed to use dpkg to create the 
new Debian package instead of manually compiling it. I reverted to the original 
Debian package to get everything running normally again, but I haven't had a 
chance to try the upgrade again. As soon as I went back to the original elogd 
everything worked fine (no changes to the elog.cfg required). I'm assuming that 
the problem came from attempting to recompile a Debian package install manually. 
Sorry for the bug scare!

Todd
icon3.gif   WISHLIST: Type <attribute> = user, posted by Steve Jones on Fri Jul 16 17:51:52 2004 
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.
    icon2.gif   Re: WISHLIST: Type <attribute> = user, posted by Stefan Ritt on Wed Jul 28 21:29:28 2004 
Acknowledged. Added your vote to the wishlist.
       icon14.gif   Re: WISHLIST: Type <attribute> = user, posted by Steve Jones on Wed Jul 28 22:08:16 2004 
> Acknowledged. Added your vote to the wishlist.

Thanks!
icon4.gif   getcfg problem in v1.410: Truncation of long config strings, posted by Steve Jones on Wed Jul 28 18:25:32 2004 
Just compiled 1.410 and have run into an issue that *may* have been
introduced in 1.393.

Config file directives such as "Welcome title" could be very long strings. 
After compiling 1.410, our "Welcome title" is truncated and, while I haven't
counted the actual chars, I suspect that the truncation happens at 1024
characters.  The procedure 'getcfg' has a declared passed paramater "int
vsize". 

I haven't looked to see if this effects any other large configuration
strings that are managed by "getcfg" but this procedure is perhaps the most
popular one by far in elog.
    icon2.gif   Re: getcfg problem in v1.410: Truncation of long config strings, posted by Stefan Ritt on Wed Jul 28 21:54:36 2004 
> Just compiled 1.410 and have run into an issue that *may* have been
> introduced in 1.393.
> 
> Config file directives such as "Welcome title" could be very long strings. 
> After compiling 1.410, our "Welcome title" is truncated and, while I haven't
> counted the actual chars, I suspect that the truncation happens at 1024
> characters.  The procedure 'getcfg' has a declared passed paramater "int
> vsize". 

Actually before 1.393 you got a buffer overflow if any string in the
configuration file was longer than 500 chars, so it's a miracle that your elogd
did not crash on the long Welcome Title. I added the "vsize" parameter to avoid
such crashes. To satisfy your need for a long Welcome title, I increased the
string size for that particular case to 10000 chars. Hope this is enough.
       icon14.gif   Re: getcfg problem in v1.410: Truncation of long config strings, posted by Steve Jones on Wed Jul 28 22:07:31 2004 
> > Just compiled 1.410 and have run into an issue that *may* have been
> > introduced in 1.393.
> > 
> > Config file directives such as "Welcome title" could be very long strings. 
> > After compiling 1.410, our "Welcome title" is truncated and, while I haven't
> > counted the actual chars, I suspect that the truncation happens at 1024
> > characters.  The procedure 'getcfg' has a declared passed paramater "int
> > vsize". 
> 
> Actually before 1.393 you got a buffer overflow if any string in the
> configuration file was longer than 500 chars, so it's a miracle that your elogd
> did not crash on the long Welcome Title. I added the "vsize" parameter to avoid
> such crashes. To satisfy your need for a long Welcome title, I increased the
> string size for that particular case to 10000 chars. Hope this is enough.

Hmmm, it is a wonder.  Our welcome text was not significantly longer (about 20
chars longer) so perhaps . . . ?

Thanks, will recompile and report back.
icon14.gif   Fixed Attribute Reply , posted by Geo Geo on Fri Jul 16 06:20:40 2004 
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 
    icon2.gif   Re: Fixed Attribute Reply , posted by Stefan Ritt on Wed Jul 28 21:25:52 2004 
> 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?

Yes, I fixed this. Revision 1.412 under CVS, new snapshot for Windows at the
download page.
icon4.gif   List Dispaly produces wrong output in 2.5.3 built 23.7.04 (snapshot), posted by Ulrich Trüssel on Tue Jul 27 17:56:56 2004 
I did not have the following problem in any snapshot before 23.7.04 .
Actually I do not have a possibility to test the snapshot under an other
system than win xp pro sp 1 (fully pached). 

Using my logbooks as well as the demo logbook works well under older
snapsgots of 2.5.3 as well as long as the "List Display = <attributes>" is
not used!

Using "List Display = <attributes>" produces an ususal output with the text
field content in the first row and a row title of the first 3 letters.

Ex.:
Attributes = Customername, Customeraddres
List Display = Customername, Customeraddres

Output:
¦Cus¦Customeraddres¦

If no record is in the logbook, only the "Cus" is dispalyed! Removing "List
Display = <attributes>" produces a normal output with same logbook!

By the way: Thnak's for the Format in the entry/edit view!!!
    icon2.gif   Re: List Dispaly produces wrong output in 2.5.3 built 23.7.04 (snapshot), posted by Stefan Ritt on Wed Jul 28 14:17:25 2004 
> Using "List Display = <attributes>" produces an ususal output with the text
> field content in the first row and a row title of the first 3 letters.

I fixed that problem. Please get the snapshot from July 28th 14:16.
       icon14.gif   Re: List Dispaly produces wrong output in 2.5.3 built 23.7.04 (snapshot), posted by Ulrich Trüssel on Wed Jul 28 16:13:04 2004 
Thank you very much Stefan!!!

Also the horizontal alignement with "Format = 1" looks much better   as before
with standard css files! Really great work!

> > Using "List Display = <attributes>" produces an ususal output with the text
> > field content in the first row and a row title of the first 3 letters.
> 
> I fixed that problem. Please get the snapshot from July 28th 14:16.
icon5.gif   Author field on reply, posted by Geo Geo on Mon Jul 19 06:07:54 2004 
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
    icon5.gif   Re: Author field on reply, posted by Stefan Ritt on Wed Jul 28 14:14:05 2004 
> 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 ..

This (new) behaviour came from the request that some people id *NOT* want to
have the new author on the reply, but the *ORIGINAL* (they used an attribute
"Origial author" which should not be replaced on a reply). Therefor I added a
new option to resolve that. So please use

Preset Author = $long_name
Preset on reply Author = $long_name

if you want to have the attribut "Author" replaced by the current one both on
new entries and on replies.
icon5.gif   Possible Formatting bug: Summary view, posted by Steve Jones on Wed Jul 14 22:52:18 2004 
I've run into a situation where the SUMMARY view of a logbook will extend
beyond the righthand border, thus requiring the user to scroll right.  This
does not occur in FULL or THREAD mode.  Long lines in the TEXT attribute
appear to be "pushing" the display too far to the right.  Limiting the
number of displayed summary lines works unless the first line is too long.

A temporary fix for this is to set summary lines = 0
    icon2.gif   Re: Possible Formatting bug: Summary view, posted by Stefan Ritt on Thu Jul 15 09:44:08 2004 
> A temporary fix for this is to set summary lines = 0

Right, that's the only way. I would call this "permanent fix" (;-)
       icon14.gif   Re: Possible Formatting bug: Summary view, posted by Steve Jones on Fri Jul 16 04:37:47 2004 
> > 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!
icon5.gif   Question on how "Format <attribute> = " works, posted by Steve Jones on Wed Jul 14 21:35:32 2004 
It is not clear to me how "Format <attribute> = " works.  At first I thought
it would allow me to rearrange how attributes are organized on the html
"page"  using 
# <flags> Sum of following flags:

    * 1: Display attribute in same line as previous attribute
    * 2: Display radio buttons or check boxes in separate lines (if applicable) 

but this does not result in any behavior that I can see.  I must admit that
I am not sure what "Values used for single message display page:" means.

My goal is to provide a more compact page, taking small attributes and
running them across the page rather than straight down.

Thanks
    icon3.gif   Re: Question on how "Format <attribute> = " works, posted by Stefan Ritt on Wed Jul 14 21:53:02 2004 
Just have a look at elog:571 which should answer your question. Also look at
elog:Config+Examples/4 which is the configuration of this Forum (which as you can
see has all attributes in a single line, even using different fonts).
       icon3.gif   Re: Question on how "Format <attribute> = " works, posted by Steve Jones on Wed Jul 14 22:59:05 2004 
> Just have a look at elog:571 which should answer your question. Also look at
> elog:Config+Examples/4 which is the configuration of this Forum (which as you can
> see has all attributes in a single line, even using different fonts).

Ok, I think I see now.  I was assuming it applied to the entry form as well.

Thanks!
          icon2.gif   Re: Question on how "Format <attribute> = " works, posted by Stefan Ritt on Thu Jul 15 21:21:50 2004 
> 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.
             icon14.gif   Re: Question on how "Format <attribute> = " works, posted by Steve Jones on Fri Jul 16 04:36:51 2004 
> > 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.
ELOG V3.1.5-fe60aaf