Re: Problem in logging with LDAP and passwd, posted by Sebastian Schenk on Fri Mar 5 13:54:13 2021
|
Hi,
we use the LDAPS connection in our setup and it works without issues.
You have to specify "LDAP server = ldaps://server.tld:port" and normally it uses a different port (636) than insecure LDAP (389). |
|
Re: Date conversion, posted by Stefan Ritt on Wed Mar 10 17:30:23 2021
|
Do you actually need to convert the date into the internal format? Why not keeping simply the full string YYYY-MM-DD HH:MM. If the use is disciplined
enough to always use the correct format, there should be no issue. I invented the datetime format to "force" all date/time inputs to have the
correct format. If you have a proper YYYY-MM-DD HH:MM format, even sorting (now by string) should work correctly. |
|
Re: Problem in logging with LDAP and passwd, posted by Laurent Jean-Rigaud on Sun Mar 14 17:02:49 2021
|
Hi Sebastian,
Nice to hear ! |
|
Re: Request: make $text available for "subst", posted by Stefan Ritt on Mon Mar 22 15:10:12 2021
|
$text is the full body text and can go over many lines. Since attributes are restricted to single lines, it's not possible to substitute them with
the body text.
Stefan |
|
Re: Request: make $text available for "subst", posted by Andreas Luedeke on Mon Mar 22 19:59:13 2021
|
While the input widget of text attributes is a single line, they can easily be multi-line in the display - when you use HTML at least.
And of course the user can parse the text field and generate a single line, if he wants to.
If you leave it to me, I'll create wonderful applications to that feature :-) |
|
Re: Request: make $text available for "subst", posted by Sebastian Schenk on Tue Mar 23 13:42:27 2021
|
I am not Stefan, but maybe I can add to this issue.
Personally I think it is not a good way to dump all the information into the text field and try to let the server parse it.
This could be archived more simply by using e.g. the python elog scripts or using the elog command tool to directly submit well structured elog |
|
Re: automatically obtain entry ID from search, posted by Stefan Ritt on Wed Mar 24 10:01:34 2021
|
You would have to do that on the scrip level. Use "curl" to search a logbook. Like following URL would search for all entries in this forum
where you are the authoer, then return the entries in CSV format:
https://elog.psi.ch/elogs/Forum/?mode=CSV1&Author=k%F6rner |
|
Re: Request: make $text available for "subst", posted by Stefan Ritt on Wed Mar 24 10:06:26 2021
|
Sure, attributes can be shown multi-line, but they cannot be stored in the elog internal database. The database is a very old design and only allows
for single line attributes. Just look at a YYMMDDa.log file and you will see that. I would have to change the database format to somethign more advanced
like XML, but that would take me a couple of weeks or months. |