Hi,

A user tried to import a CSV file, which caused e-log to add a field called "date" to the list of attributes (and then crash). This caused the log-book to be blocked until someone (guess who) would go edit the elogd.cfg file and then trigger a reload.

1. suggestion : E-log should not crash in this case

2. suggestion: E-log should not allow invalid attributes to be added via CSV Import, which causes the log-book to be blocked.

For the time being, I will just  "Deny import" (by the way, the doc says it is "Deny CSV import", but I think the syntax is "Deny import". Not really important.

I think this should be quite easy to reproduce.

Thanks a lot

Soren

Hi Stefan and Andreas

Yesterday I reported I had some issues with the latest elog: but now I can reproduce one.  
elog 2.9.2-a738232

I started a new entry, and attached three pdf files.  I did not get the problem of not seeing the png thumnbnail
this time, although that is annoying if you want/need to adjust the thumbnail image before submitting.

However, if I then look at the running processes, I have the following listed (ps -A)

23677 tty1     00:00:04 elogd
23809 tty1     00:00:00 elogd <defunct>
23825 tty1     00:00:00 elogd <defunct>
23847 pts/0    00:00:00 ps

23677 was when I started the elogd daemon, having killed off the previous daemon etc for test purposes.

23809 and 23825 appeared after a couple of pdfs were added (second and third ones to be precise).  They can only
be killed off by killing off the original running daemon.  It appears that attaching a second and further pdf
attachments to any entry generates an elogd <defunct> in the processes list, although attaching a jpg in the
middle of a list of pdfs didn't (but the next pdf did).  This is happening while adding attachments, that is the
Submit button has yet to be pressed, so it seems to be generated  when the pdf file is being processed for some
reason.

You can end up with quite a stack of these in the process list!

I never saw this behaviour with the previous version I was running, SVN2475 I think.


By the way, I still cannot send an attachment over to this server (showing a screenshot) without the 502 error.

hi there,

Is it possible to attach a default value for a radio button when submitting a new form/record, for example: 
I now have an item "Confirmed" Yes/No, and I want the "no" option to be selected by default when a new form/record is created.
Does anyone know how to arrange this?

Thanks in advance!

RJ

How do I set a default list option?
 I have an attribute called Active with options yes, no
When I do a list I want to see just the records having yes.
When required, the quick filter allows me to see records with option = no or all the records.
Thanks

Hi,

Is it possible to have a default filtered view in E-log?

Lets say we have a record with status finished on one attribute.

Is it possible to have a default list view that just shows records with this status?

I really don't know if anybody already had this problem or i just didn't 
find the solution in the documenttaion: 
 
There is a possibility to sort the log by the value of a attribute as 
well as a flag for reverse sort. anf it's quite easy to build up a 
command line with the sort attribute and value. But this only works from 
a self written command line. 
 
Is there any possibilty to make ELOG soring by default (without a 
command line option) by a other attribute than date? I would use a date 
set by the user manually to sort the log file, even the user clicks on 
the log-name.  
 
or may it be a possibility for a additional feature, like a logbook 
option "Default sort = my own date" and the logbok get sorted by this 
attribute and option by default. 
 
Would be happy about every tip! ThankX!