Re: Elog ID entry bug at >99999 entries, posted by Andreas Luedeke on Sat May 5 20:55:23 2018
|
Well, in my example the ID link worked just fine.
There could be a string length limitation, but it could be as well the way you are creating the ID that is the source of the problem: I would
need the part of your elogd.cfg that defines how you format your ID in order to try to reproduce your problem. |
|
Re: about shiftcheck, posted by Andreas Luedeke on Tue May 15 10:35:32 2018
|
An attribute is similar to a variable. Do you know any programming language that allows to start a variable with a digit? I don't.
The solution is very obvious: start your attributes with a letter.
Cheers, Andreas |
|
Re: Report Generating Tool?, posted by Andreas Luedeke on Wed May 23 16:19:48 2018
|
Here's a little example for a query for this logbook:
curl -f -s -k "https://elog.psi.ch/elogs/Forum/?jcmd=Search&mode=CSV1&last=7&Category=^Question%24"
You
can easily process this output with perl, to create reports. I use it for example to create counts for specific enties, like "Bug reports" that |
|
Re: number of entries in Login user list, posted by Andreas Luedeke on Thu Jun 14 12:37:22 2018
|
Hi Janusz,
You can change the following line in elogd.h and recompile:
#define MAX_N_LIST 100 |
|
Re: edit templates from config page, posted by Andreas Luedeke on Thu Jun 14 18:17:07 2018
|
> Dear all,
> I have some logbook which uses preset text depending on some option values, and uses text files for this.
>
|
Problem with eloglang.german_UTF8, posted by Andreas Luedeke on Tue Aug 7 10:53:45 2018
|
I had a problem with restarting ELOG since about a year, and finally I found the culprit. I just want to share it here, to prevent anyone else to make
the same mistake,
Apparently the files resources/eloglang.* are rather sensitive to the syntax. But it doesn't tell you: no warning or error message comes |
|
Re: Compile issues on Fedora withe current elog source, posted by Andreas Luedeke on Wed Sep 12 20:52:22 2018
|
Stefan said "code is commited": that means you can download the latest version from https://bitbucket.org/ritt/elog, as described in https://elog.psi.ch/elog/download.html,
and then compile it. Clear now?
Stefan |
|
Re: Logfile not registering entry numbers?, posted by Andreas Luedeke on Fri Oct 19 13:08:30 2018
|
It looks like you've found a bug in ELOG. I've checked my elog.log and see that all NEW entry lines show "#0".
I've looked into the code: the message is written before the new entry is submitted, and only then the entry ID is defined.
For
new entries one would need to make the logging print line later - but that would blow up the code.
The message IDs are correct for saving |