upgrade problem, posted by Tim Schelfhout on Tue Mar 15 19:53:55 2016
|
Hello there,
After several years of great ELOG usage I decided to upgrade our ELOG server. I am using it to keep
a logbook of my students. |
Re: upgrade problem, posted by Andreas Luedeke on Wed Mar 16 08:39:55 2016
|
Hi Tim,
starting with ELOG version 3 all entries are moved into sub-directories for each year.
If you move the files back
from the sub-directories and restart elogd, then the entries should appear again in the logbook with ELOG 2.9.2.
I don't
know how to solve your other problem. Maybe you should talk to someone locally who can administer your windows server?
Cheers, Andreas
|
Pre-populate filed based on selection, posted by Jimmy Bria on Mon Mar 14 16:00:02 2016 
|
Hi,
Is it possible to pre-populate a field based on the selection of another field. I like to have the Equipment Description field populated
when the use makes a selection on the EQ# field. |
|
Re: Pre-populate filed based on selection, posted by Stefan Ritt on Tue Mar 15 03:48:58 2016
|
Use "conditional attributes" as described in the documentation: https://midas.psi.ch/elog/config.html#conditional
Jimmy
Bria wrote:
Hi, |
|
Installation: Failed Dependencies, posted by Phil Rubin on Fri Mar 11 17:19:02 2016
|
Is there anything I can do about this?
kernel: 2.6.32-279.14.1.el6.x86_64
ldd (GNU libc) 2.12 |
|
elogd -m Error sending local entry: Error transmitting message, posted by Dave on Thu Mar 10 00:26:03 2016
|
I'm running ELOG on a seperate Windows Servers.
When I try to synchronize the logbooks using "elogd -m", I get an "Error sending local entry: Error transmitting message"
If I click on the "Synchronize" link in the logbook, it can correctly send entry to remote ELOG. |
elogd -m , posted by Dave on Thu Mar 10 00:16:33 2016
|
I'm running ELOG on a seperate Windows Servers.
When I try to synchronize the logbooks using "elogd -m", I get an "Error sending local entry: Error transmitting message"
If I click on the "Synchronize" link in the logbook, it can correctly send entry to remote ELOG. |
Execute new|edit doesn't seem to work, posted by Juergen Diefenbach on Fri Feb 26 17:35:54 2016
|
I am trying to use the "Execute new|edit|delete" feature to track changes to an elog using git.
When a new entry is created a shell script should be executed (certain attributes of the logbook entry should be passed as arguments to it). The script |
|
Re: Execute new|edit doesn't seem to work, posted by Andreas Luedeke on Sun Feb 28 18:24:58 2016
|
[quote="Juergen Diefenbach"]I am trying to use the "Execute new|edit|delete" feature to track changes to an elog using git.
[...]
However, I experienced unreproducible behavior when creating "new" entries. Sometimes the command specified by "Execute new=" is called, sometimes the |
|
Re: Execute new|edit doesn't seem to work, posted by Juergen Diefenbach on Mon Mar 7 13:03:13 2016
|
[quote="Andreas Luedeke"]I'm just guessing, but you could try to disable the "save drafts" feature and see if the behaviour changes:
Save drafts = 0
|
|
Re: Execute new|edit doesn't seem to work, posted by Andreas Luedeke on Tue Mar 8 14:12:26 2016
|
[quote="Juergen Diefenbach"][quote="Andreas Luedeke"]I'm just guessing, but you could try to disable the "save drafts" feature and see if the behaviour
changes:
Save drafts = 0
|
|
Attribute Field Size Limited to 255 Characters, posted by Mike Bodine on Thu Mar 3 00:12:45 2016
|
I currently have an Attribute defined in my .cfg file as "Format <Attribute> = 0, attribname, attribvalue, 120, 500".
I've found if I exceed 255 characters elogd.exe fails. Is there a method that will allow me to exceed 255 characters? |
|
Re: Attribute Field Size Limited to 255 Characters, posted by Andreas Luedeke on Thu Mar 3 14:51:55 2016
|
No. At least there is no simple method.
You would need to edit the source code and recompile elogd. But the number 256 is used for about 300 times in the source code, you'll have
a hard time finding the right one to increase. |
|
Attribute Field Size Limited to 255 Characters, posted by Mike Bodine on Thu Mar 3 00:02:26 2016
|
I currently have an Attribute defined in my .cfg file as "Format <Attribute> = 0, attribname, attribvalue, 120, 500".
I've found if I exceed 255 characters elogd.exe fails. Is there a method that will allow me to exceed 255 characters? |