<a href="mailto:user@domain.com">user@domain.com</a>

Email System CareWare = ..., $user_email

Hi - again a configuration question.

How can I suppress all email notifications? The "Suppress default = 2" flag 
allows me to always produce a notification, but the flag does not provide 
an option to never produce a notification. The flag "Suppress Email on 
edit" does help a bit, but still notifications for new messages will be 
sent.

I'm looking forward to your fast response... So far your support is 
fantastic!

Bartjan Wattel

hi again,

we have been doing a bit of stress testing for Elog. The most important 
thing we found is that Elog stops responding when a user uploads a large 
attachment (we used a 240 Mb attachment). 

Is it possible to add a flag in the configuration file, to specify the 
maximum size of an attachment?

Bartjan Wattel

> How can I suppress all email notifications? The "Suppress default = 2" flag 
> allows me to always produce a notification, but the flag does not provide 
> an option to never produce a notification. The flag "Suppress Email on 
> edit" does help a bit, but still notifications for new messages will be 
> sent.

Suppress email to users = 1

RTFM

> 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.

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!!!

> 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.

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.