Removal of ID and Date attributes, posted by James Darrow on Sun Mar 13 21:20:56 2022 
|
Hello all,
I just found elog which is a great piece of software! I'm implementing it for use to log my shortwave listening contacts. The problem
that I have is I'm moving over a current log to elog which already has a date of when the record was created, which is important.I renamed the old |
Re: Removal of ID and Date attributes, posted by Stefan Ritt on Mon Mar 14 08:49:44 2022
|
Use the configuration option
List display = Day, Station Type, Start time UTC, ...
as written in the documentation. |
|
Re: Removal of ID and Date attributes, posted by James Darrow on Mon Mar 14 18:45:14 2022
|
That worked! Thanks Stefan
Stefan
Ritt wrote:
Use the configuration option |
|
Use different HTML class for drafts compared to not existing entries, posted by Edmund Hertle on Wed Mar 9 16:25:31 2022
|
Right now a Draft shows a red error indication, that the entry is currently a draft. For the CSS styling it uses the HTML class="errormsg".
The same class is also used if an entry does not exist.
Would it be possible for the draft version to use a different HTML class (for example class="draftmsg")? It can also use the same visual |
Invalid activation code, posted by Konstantin Olchanski on Wed Mar 2 18:29:08 2022
|
Something is not right with the elog account activation, I get the email
for "Registration request for ELOG logbook "haicu"", but when I follow the given URL,
I get "Invalid activation code". Account activation requests go to two people,
|
|
Re: Invalid activation code, posted by Konstantin Olchanski on Wed Mar 2 23:15:11 2022
|
> Something is not right with the elog account activation...
I did a test:
|
|
login cookie confusion, posted by Konstantin Olchanski on Wed Mar 2 18:35:48 2022
|
we had an elog with only one logbook and one password file,
we added a second logbook with a second password file and everything broke.
|
elog c++ and LDAP, posted by Laurent Jean-Rigaud on Wed Feb 16 22:24:18 2022
|
Hi Stefan,
I've seen that ELOG is build now with gcc-c++ now, so i tried to check rpmbuild script with all options. It seems that ldap api is different
with c++ (quick search : https://www.openldap.org/lists/openldap-software/200706/msg00177.html) and elogd can not been build anymore with ldap support. |
|
make all messages on ubuntu LTS 20.04.03, posted by Konstantin Olchanski on Tue Feb 8 00:52:47 2022
|
For the record, compiler messages from elog tip of branch elog/master.
Most of the stuff is the usual same-old that we mostly fixed in midas:
|
|
Re: make all messages on ubuntu LTS 20.04.03, posted by Stefan Ritt on Tue Feb 8 09:14:25 2022
|
> /usr/include/x86_64-linux-gnu/bits/stdio2.h:36:10: note: ‘__builtin___sprintf_chk’ output 2 or more bytes (assuming 4097) into a
> destination of size 4096
|
|
Re: make all messages on ubuntu LTS 20.04.03, posted by Stefan Ritt on Tue Feb 15 13:45:02 2022
|
Well, I bit the bullet and fixed all of these warnings. Took me like two days of work, but now should be fine. You might want to test it again. I only have
gcc 9.2.0, there it compiles now without warning.
|
|
Re: make all messages on ubuntu LTS 20.04.03, posted by Konstantin Olchanski on Tue Feb 15 20:55:02 2022
|
> Well, I bit the bullet and fixed all of these warnings. Took me like two days of work, but now should be fine.
> You might want to test it again.
|
|
Re: make all messages on ubuntu LTS 20.04.03, posted by Stefan Ritt on Wed Feb 16 08:45:15 2022
|
I fixed these as well, please have a look again. BTW, midas had a few of these as well.
Stefan |
|
Re: make all messages on ubuntu LTS 20.04.03, posted by Konstantin Olchanski on Wed Feb 16 20:01:17 2022
|
> I fixed these as well, please have a look again. BTW, midas had a few of these as well.
confirmed. elog commit d828aa58305ee8ce2ae882c0ff3c34cfa66650e5
|
|
ELOG problems with certificates, posted by Ezio Zanghellini on Thu Feb 10 19:03:56 2022
|
Recently I have had problems with ELOG not accepting the certificates (in this case from https://letsencrypt.org/)
probably due to the old version of the SSL library of the binary distribution for Windows.
I have tried to follow the instructions to set up ELOG to work with Apache but they are probably old. |
|
"New User" option does not work when Authentication=Webserver, posted by Jan Just Keijser on Fri May 29 09:27:32 2020
|
Our setup uses "Authentication=Webserver" + no automatic user registration. Thus, logbook admins should add a user by clicking "Config"
and then "New user". However, no matter what they fill in in the "new user " dialog, as soon as they hit "Save" an error
pops up saying that their username (the admin one, not the new one) already exists. I found the following code: |
|
Re: "New User" option does not work when Authentication=Webserver, posted by Stefan Ritt on Tue Aug 4 13:29:23 2020
|
Unfortunately I locallly don't have Webserver authentication, so I cannot check or debug. If you send me a diff that works for you, I'm happy
to incorporate it.
Stefan |
|
Re: "New User" option does not work when Authentication=Webserver, posted by Jan Just Keijser on Wed Aug 18 09:05:51 2021
|
here's the patch that I use to enable use creation and deletion in combination with Webserver authentication.
The idea behind the patch is that if the user logged in via "http_user" is an elog admin, then {s}he is allowed to save a random
user configuration, including creating or deleting a user. |
|
Re: "New User" option does not work when Authentication=Webserver, posted by Stefan Ritt on Thu Feb 10 17:32:42 2022
|
Thanks for your patch, I committed it.
Stefan |