Good day,

I'm new to Elog and I find it really nice and straight foward...

I still have a few questions that I couldn't address reading the manuals.

-I'm creating a logbook with a lot of attributes. I would like to know if there is a way to name (display) my attribute differently then it's original name. That way I could program $attrib1; $attrib2, etc, and map a name to display the column accordingly... Is it something possible ? 

-Is it possible to hide the field "Entry Time" when creating or editing an entry ?

-I saw the Cell Style fonction to set Color (really nice...), My attribute1 is a worker name; Attribute2 is how the work is going on (stop, ready, in process) I would like to hide Atribute2 in list mode but change Attribute1 cell color based on Attribute2 status... is it possible to do so?

-When using "Show Text = 0" (i'm only using attributes), creating a new entry present the menu "Submit", "Save", "Preview" and "Back".... Pressing "Save" leaves the page, shows "OK with a number" and "Preview" is useless. Is it possible to tune what button should be present or not ? I would like to remove Save and Preview....

For the info, my config file

[GCT]
Theme = default
Show Text = 0
Enable attachments = 0
Show attachments = 0
Use lock = 1
Bottom text = 
Comment = Gestion de la charge de travail
omit email to = 1
Suppress Email to users = 1
Suppress default = 2
Suppress Email on edit = 2
Resubmit default = 2
Enable browsing = 0
Back to main = 1
List after submit = 1
'Mode commands = 0
Menu commands = Select, edit, Delete
List menu commands = Select, New, Find
Attributes = #Réception, #Galée, Infographiste, Traitement, Réviseur, Révision, Contrôleur, Contrôle, Correcteur, Correction, Contrôle final
List display = Edit, #Réception, #Galée, Infographiste, Traitement, Réviseur, Révision, Contrôleur, Contrôle, Correcteur, Correction, Contrôle final
Fixed Attributes Edit = #Réception
Preset #Réception = #####

Format #Réception = 0,attribname,attribvalue,5,5
Format #Galée = 0,attribname,attribvalue,10,10
Format Infographiste = 0,attribname,attribvalue,2,2
Format Réviseur = 0,attribname,attribvalue,2,2
Format Contrôleur = 0,attribname,attribvalue,2,2
Format Correcteur = 0,attribname,attribvalue,2,2

Options Infographiste = ??, ML
Options Réviseur = ??
Options Contrôleur = ??
Options Correcteur = ??

Preset Infographiste = ??
Preset Réviseur = ??
Preset Contrôleur = ??
Preset Correcteur = ??

Extendable options = Infographiste, Réviseur, Contrôleur, Correcteur 

ROptions Traitement = ., En cours, Prêt, Vérification
ROptions Révision = ., En cours, Prêt
ROptions Contrôle = ., En cours, Prêt
ROptions Correction = ., En cours, Prêt
ROptions Contrôle final = ., OK

Cell Style Traitement En cours = background-color:#FF0000 
Cell Style Traitement Prêt = background-color:#33FF33
Cell Style Traitement Vérification = background-color:yellow

Cell Style Révision En cours = background-color:#FF0000 
Cell Style Révision Prêt = background-color:#33FF33
Cell Style Révision Vérification = background-color:yellow

Cell Style Contrôle En cours = background-color:#FF0000 
Cell Style Contrôle Prêt = background-color:#33FF33
Cell Style Contrôle Vérification = background-color:yellow

Cell Style Correction En cours = background-color:#FF0000 
Cell Style Correction Prêt = background-color:#33FF33
Cell Style Correction Vérification = background-color:yellow

Cell Style Contrôle final OK = background-color:#33FF33

Cell Style Contrôle final En cours = background-color:#FF0000 
Cell Style Contrôle final Prêt = background-color:#33FF33
Cell Style Contrôle final Vérification = background-color:yellow

Thanks alot for your help :)

First, I can only fix problems which are reproducible. Can we do another power outage at PSI again?

But seriously, I guess what happened is that elog sees an empty directory when the AFS server
goes down. If this happens, it rebuilds its internal (RAM based) indes, and sees no entries there.
So the next entry will be ID 1. That should be independent of the ELOG version. I guess if PSI
would have a power outage a year ago, you could have had the same problem.

I had problem some long time a go with AFS, where the network access blocked the program
for several minutes. I decided then to ONLY use local filesystems for elog servers, and do the
backup via rsync to an AFS account. Since then I never had problems.

Now it is hard for me to develop code which avoids the mentioned problem. I could maybe
check if there are many entries, and all over sudden there are no entries any more, the server
just stops with some detailed error message. But it is hard for me to mimic the AFS server 
outage. I can try to manually delete elog files and see what happens, but this only partially
mimics network problems.

/Stefan

> I'm running ELOG since several years with rather heavy usage.
> Last week I've upgrades from 3.0.0 to 3.1.0 and this week I had twice the same problem:
> elogd lost the index for old entries and showed empty logbooks, without having restarted.
> The logbooks appeared to be empty; new entries started with index "1".
> The first time the origin of the problem were network troubles;
> the second time it had been caused by a severe problem of our AFS file system service.
> I never experienced this consequence for ELOG in the past when we had AFS problems.
> 
> Since the logbooks are used for the operation log of a user facility they continued to do new entries.
> The next day I had to re-number the new entries and restart elogd and everything was fine.
> 
> I could understand if elogd crashes when the filesystem of the logbook goes away.
> And when it restarts with an (temporarily) empty filesystem, that would explain what happened.
> But it did not restart and the log file does not contain any information about any problem, 
> just that suddenly all new entries in each logbook started with ID "1" again.
> 
> Stefan, any idea?
> Anyone else ever experienced that with the new ELOG version (or older ones)?

I'm running ELOG since several years with rather heavy usage.
Last week I've upgrades from 3.0.0 to 3.1.0 and this week I had twice the same problem:
elogd lost the index for old entries and showed empty logbooks, without having restarted.
The logbooks appeared to be empty; new entries started with index "1".
The first time the origin of the problem were network troubles;
the second time it had been caused by a severe problem of our AFS file system service.
I never experienced this consequence for ELOG in the past when we had AFS problems.

Since the logbooks are used for the operation log of a user facility they continued to do new entries.
The next day I had to re-number the new entries and restart elogd and everything was fine.

I could understand if elogd crashes when the filesystem of the logbook goes away.
And when it restarts with an (temporarily) empty filesystem, that would explain what happened.
But it did not restart and the log file does not contain any information about any problem, 
just that suddenly all new entries in each logbook started with ID "1" again.

Stefan, any idea?
Anyone else ever experienced that with the new ELOG version (or older ones)?

Thanks Stefan, that did the trick.

Had a bit of an effort with the git repository, though, kept getting 403 errors when tried the

git clone https://bitbucket.org/ritt/elog as per the "download" page.

error: The requested URL returned error: 403 while accessing https://bitbucket.org/ritt/elog/info/refs

This problem has been fixed in Version 3.1.0-2. Please upgrade.

Ok, I fixed this in the current GIT version. You might check if that works for you.

The changelog is here: http://midas.psi.ch/elog/download/ChangeLog

It is save to install the new version over the old one.

congrats, any detail changelog? I assume in software packages?

is it save just install and overwrite the old version?