Re: Wishlist: TOOLTIP for ATTRIBUTES, posted by Stefan Ritt on Thu Jul 15 10:01:03 2004
|
Ok, I added the option
Tooltip <attribute> = ...
I apply the HTML "title" tag to the whole table row, so the tooltip appears on the
whole line, not only the attribute name. I guess this is much more intuitive. Give
it a try. New version under CVS and available as a snapshot. |
|
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. |
|
Re: Request: limit size of attachments, posted by Stefan Ritt on Thu Jul 15 22:01:55 2004
|
> Is it possible to add a flag in the configuration file, to specify the
> maximum size of an attachment?
I implemented a "max content length = xxx" flag, which defaults to 10MB. If an
attachment is larger, an error gets displayed. The problem is that elogd can
only send the error message to the browser *after* it received the whole
request, so it has to "drain" the 240 MB first, which could take quite some
time on a slow connection.
Alternatively, I can cut the connection to the browser immediately, since the
HTTP header contains the content length after the first ~500 bytes, but in
that case the browser only shows a message box "Document contains no data"
which gives the user noe clue of what's wrong.
Anyhow the biggest problem of elog in high stress environments is that it's
single threaded. So if someone issues a search in a large logbook, it could
take some time, in which elog cannot respond to other requests. Maybe I will
find time in the future to make elog multithreaded, but certainly not in the
near future. |
|
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. |
|
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. |
|
Re: WISHLIST: Type <attribute> = user, posted by Stefan Ritt on Wed Jul 28 21:29:28 2004
|
Acknowledged. Added your vote to the wishlist. |
|
Re: Date format problem in "Thread display = ", posted by Stefan Ritt on Wed Jul 28 21:34:35 2004
|
> I get the following in my THREADED logbook view:
>
> "Adding new services, planned for 1090519200. Last revised: Thu Jul 15
> 18:03:52 2004"
That should be fixed by the current version. Please update. |
|
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? |