Re-using IDs after move to another Logbook overwrite Entries, posted by Barend on Wed Jan 2 15:38:19 2013
|
Hi Stefan,
I have observed following behavior when I move entries from one logbook to another:
The first entry in "Open" get ID "1"
When I move this Item to "Closed", it will keep ID |
Re: Re-using IDs after move to another Logbook overwrite Entries, posted by Barend on Thu Jan 24 10:42:13 2013
|
Stefan Ritt wrote:
|
Importing XML/CSV, posted by Barend on Tue Oct 8 18:14:20 2013 
|
Hi Stefan,
I'm experiencing problems importing XML (.csv is not working at all for me).
My logbook contains 3 date-attributes besides the system DATE (entry time), date-format is defined as %d %b %y. |
|
Re: Importing XML/CSV, posted by Barend on Sun Oct 13 16:32:05 2013
|
Andreas Luedeke wrote:
|
|
Error: Attribute <date> not supplied., posted by Barend on Mon Oct 14 12:08:16 2013
|
Stefan/Andreas,
When I reply to an existing Logbook entry, I get the error page "Error: Attribute Audit Date not supplied. Please go back and enter the Audit
Date field." |
|
Re: Error: Attribute <date> not supplied., posted by Barend on Tue Oct 22 10:54:51 2013
|
David Pilgram wrote:
|
|
Re: Importing XML/CSV, posted by Barend on Tue Oct 22 10:56:13 2013
|
Andreas Luedeke wrote:
|
my_shell (OS_UNIX) uses /tmp/elog_shell - conflict when more than one elogd runs at the same time, posted by John M O'Donnell on Fri May 20 22:45:00 2011
|
all instances of elogd use the same file name in /tmp when calling my_shell. This can cause some inconsistent behavior when two or more copies
of elogd are runnnig at the same time. (eg. one might detect ImageMagik is installed, and the other not,)
|