Re: Reverse sort by Attribue, but it's only showing the last 6 entries by default., posted by Anthony on Mon Aug 10 09:01:24 2020
|
Thank you, Andreas! Not sure why I kept overlooking it in the manual. As for the number of entries when I sort, I'm not sure. I'll
set it up to display a larger number and see what happens.
Andreas |
|
Re: How to prevent file path leaks on a 404 page, posted by Stefan Ritt on Wed Aug 26 20:44:38 2020
|
A new RPM has been released at https://elog.psi.ch/elog/download/RPMS/elog-3.1.4-2.el7.x86_64.rpm containing that fix.
Stefan
Ritt wrote:
I removed the version info from the 404 error, but you have to recompile |
Using curl to post new entries, posted by Florian Feldbauer on Wed Sep 2 10:24:58 2020
|
Hey,
i'm trying to use curl to post new entries to our logbook as described here: https://elog.psi.ch/elogs/Forum/68597.
The Elog is installed via the Deban package on Buster. |
|
Re: Using curl to post new entries, posted by Florian Feldbauer on Wed Sep 2 11:56:04 2020
|
After going through the code of the Python API (https://github.com/paulscherrerinstitute/py_elog/blob/master/elog/logbook.py) I tried the following:
$ python3
>>> from passlib.hash import sha256_crypt |
|
Re: Using curl to post new entries, posted by Stefan Ritt on Wed Sep 2 15:42:40 2020
|
This is correct. The elogd daemon needs username and password in parameters "unm" and "upwd". The password must be SHA256 encoded,
so best is to grab it from the password file. This way one does not have to send clear text passwords over the network.
Florian |
|
field selections persist across new log entries?, posted by Anthony Krishock on Tue Sep 8 14:22:11 2020
|
All,
I am using elog as an observation log for amateur astronomy. I have a form configured, but I would like to know if it is possible to |
|
Re: field selections persist across new log entries?, posted by Sebastian Schenk on Tue Sep 8 16:35:14 2020
|
As far as I know, it is not possible, if you make a "new" entry.
You could configure the elog, to always PRESET an atribute, but then it is always the same, not the last.
I think the "duplicate" entry function could provide you partly with the functionality you want, as it copies all old values into a |
|
Re: field selections persist across new log entries?, posted by Andreas Luedeke on Wed Sep 9 10:33:58 2020
|
It is probably possible, but requires a big of a hack.
Whenever you save a new entry or edit an old one, you run a little shell script
to write the value of this field into a file.
Whenever you create a new entry you read the PRESET value with a shell script from that file.
Here
are the relevant excepts from the documentation: |