Since there were no responses, I decided to make good use of the fact that the software is thankfully open-sourced. I modified elogd.c and added just a couple of lines to get what I wanted.
22245,22250d22244
< if (old_mail && getcfg(lbs->name, "Use Email Subject Edit", subject, sizeof(subject))) {
< i = build_subst_list(lbs, slist, svalue, attrib, TRUE);
< sprintf(str, "%d", message_id);
< add_subst_list(slist, svalue, "message id", str, &i);
< strsubst_list(subject, sizeof(subject), slist, svalue, i);
< } else
These lines just follow the comment line: /* compose subject from attributes */
Erkcan Ozcan wrote: |
Hi,
The default email subject line for a new entry is: "New ELOG entry", and the default email subject line for an edited entry is: "Updated ELOG entry". However when we set "Use Email Subject", both new entries and the updated entries use the same email subject. Is there an equivalent of "Use Email Heading Edit" for the subject line? I tried "Use Email Subject Edit", to no avail.
Thanks in advance,
e.
|
|
Please excuse my double-posting. But my first entry was not displayed on the forum and I haven't received feedback yet. I think this is because I responded to an entry that was still in draft mode, whereas my entry was a "normal" entry. My initial entry has the Message ID: 69870 and was in reply to: 68348
***
Dear Andreas and Stefan,
First of all thank you for the template for a checklist. I have created my own version of it and the HTML looks fine. For comparison, I temporarily also included the shiftcheck template provided by Stefan to my ELOG.
However, I have the same problem as JD. After submitting the data in shiftcheck, I receive the error "Cannot open file passwords.pwd: No such file or directory" and the URL is http://localhost:8085/ShiftCheck/?cmd=Submit&suppress=1&unm=&upwd=&Author=Marcel+Zauner-Wieczorek&edit_id=&D=1&M=4&Shift=Morning&a4=&h2=&a5=&a6=&c1=&c2=&c3=&c4=&c5=&bb1=&cr1=&cr9=&cr18=&cr20=&cr21=&cr23=&cr24="
I have tried to include the path of the password file in the cfg file (using "", <>, <"">, and only the path name), but then the elogd.exe won't start at all unless I change it back to the simple "Password file = passwords.pwd".
Here is an excerpt of my config file:
****
[global]
port = 8085
Password file = passwords.pwd
Login expiration = 1
Admin user = Marcel
Login user = Marcel
Self register = 1
Group General = ShiftCheck
Group Gas phase instruments = Checklist_MARGA
Restrict edit time = 1
Admin restrict edit time = 0
Autosave = 60
[ShiftCheck]
Comment = Shift Check List
Attributes = Author, D, M, Y, Shift, a1, a2, a3, a4, a5, h1, h2, h3, h4, h5, c1, c2, c3, c4, c5, c6, c7, bb1, cr1, cr2, cr3, cr4, cr5, cr6, cr7, cr8, cr9, cr10, cr11, cr12, cr13, cr14, cr15, cr16, cr17, cr18, cr19, cr20, cr21, cr22, cr23, cr24, cr25, cr26, sw1, sw2, sw3, sw4, sw5
Quick filter = Shift, Author
Options Shift = Morning, Evening, Night
Enable attachments = 0
Show text = 0
Custom new form = shiftcheck.html
Custom edit form = shiftcheck.html
Custom display form = shiftcheck.html
List after submit = 1
[Checklist_MARGA]
Comment = Check List for MARGA
Date Format = %d.%m.%Y
Time Format = %d.%m.%Y %H:%M:%S
Reverse sort = 1
Attributes = Author, D, M, Y, On, DP2h, T_SJAC, T_heat, EC_An, EC_Cat, IonBal, IS_Cat_Ae, IS_An_Ae, IS_Cat_Ga, IS_An_Ga, P1, P2, Err, Com
Quick filter = Author
Enable attachments = 0
Show text = 0
Custom new form = checklist_MARGA.html
Custom edit form = checklist_MARGA.html
Custom display form = checklist_MARGA.html
List after submit = 1
***
I am actually confused about the passwords.pwd file. I have successfully created several users with passwords and I can use their credentials to log into the different labbooks. However, none of these users (let along their (encrypted) passwords) turn up in the passwords.pwd file. I don't know where ELOG saves these information, but it's apparently not the passwords.pwd file that is defined in the cfg file and that I have access to.
I hope that someone can help me with this issue. Otherwise, I would omit the password function within ELOG and find an external solution for a password protection.
Cheers,
Marcel |