Request: make $text available for "subst", posted by Andreas Luedeke on Mon Mar 22 14:56:12 2021
|
Hi Stefan,
I've just tried to read the $text with subst into another field and failed.
It looks like $text is only available for the execution of shell scripts in the "execute new|edit|delete = <script>" command. |
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 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. |
Re: Request: make $text available for "subst", posted by Andreas Luedeke on Wed Mar 24 22:09:56 2021
|
Hi Stefan,
no problem: if I just strip all newlines from the $text field (in HTML you use <br> anyway, the newline has no function apart from whitespace),
and my multiline attribute is fine to go. |
|
Re: Request: make $text available for "subst", posted by Andreas Luedeke on Mon Jun 14 18:06:06 2021
|
I should tell that I found a simpler way to achieve the same:
I suppress the "text" field and use a single line text input field instead.
The single line input in "free text" modes just contains "<br>" : I would have had to use those in the text field anyway. |
|
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 |
Additional forbidden attributes, posted by Sebastian Schenk on Mon Jun 14 16:15:10 2021
|
Hello Stefan,
I stubbled on a issue with our elog.
We introduced an attribute "mode" to one of the elogs and it breaks the "Find" function as this attribute is already used for |
|
Naming a Notebook KTAG Wipes Out Formatting. Why?, posted by Phil Rubin on Sat May 22 20:44:33 2021
|
An experiment's ELOG installation, using the default theme, names logbooks after its subsystem's acronyms. One subsystem is referred to
as KTAG, but when this name (or its lowercase version) is used for a logbook name, the logbook appears unformatted. Changing the name, even to K-TAG,
works fine. Nothing close to KTAG appears in elog.css. Does anyone know why this happens and whether it is possible or worth the while to get |
|
New user not working, posted by Gabriel Lopez on Thu May 20 21:01:41 2021
|
Running elog-3.1.4-3 Can't add users through the web interface. Clicking add user and writing all the fields in with something doesn't add
a user into the PWD file of that logbook. Running a tail -f on the password file shows elog writes the user info with the hashed password 3 times and then
deletes the information about 20 seconds later. Has anyone else had a similar issue? This is running on RHEL8.3 |
Bug: "Append on edit" triggers too often, posted by Faith on Tue May 4 14:45:47 2021
|
The command "Append on edit = " is getting executed everytime, when a dropdown menu is changed. This happens even at the first creation of
an entry, so the append text stucks up multiple times in the text body. |
|
Re: Bug: "Append on edit" triggers too often, posted by Sebastian Schenk on Tue May 4 15:24:56 2021
|
I can confirm the issue also for "prepend on edit".
To be more precise, it gets executed everytime the condition state changes, if placed in the config without condition, or if placed in a condition,
everytime the condition gets activated. |
|
Real-time mirroring?, posted by Frank Baptista on Mon Apr 26 15:40:36 2021
|
Hello!
We have a number of local ELOG servers, all mirrored to a single "remote" ELOG server. We have users that create updates at the |
|
Re: Real-time mirroring?, posted by Sebastian Schenk on Mon Apr 26 16:41:50 2021
|
Hello Frank,
It seems, you are using the mirror function of elog. It should resolve conflicts by itself acording to the documented rules. (https://elog.psi.ch/elog/config.html)
As I don't use this function, I can't say how good it works. |
|
Re: Real-time mirroring?, posted by Frank Baptista on Fri Apr 30 20:29:45 2021
|
Hi Sebatian,
Thank you for taking the time to answer...very much appreciated!
|
|
Re: Real-time mirroring?, posted by Sebastian Schenk on Fri Apr 30 21:13:39 2021
|
Hi Frank,
I am not sure, if I understood your setup correctly. But in my eyes, you don't need the local elog servers. The only difference for
the users at the chambers would be to directly use the 'mirror' remote elog url instead of the local elog url in their browsers. "which |
|
Re: Real-time mirroring?, posted by Frank Baptista on Fri Apr 30 21:55:23 2021
|
Hi Sebastian,
You're absolutely correct that the users at the chambers could directly use the remote ELOG server (without having a local server),
and I did originally think about this. Unfortunately, there are times that our network "goes down" (for maintenance and other issues), |
|
[Bug?] Admin restrict edit time, posted by Faith on Fri Apr 30 07:27:31 2021
|
I would like to know, if the command "Admin restrict edit time = " does really work as intended.
In my case I have the following global configuration:
Admin user = <me> |
|
segfault in auth.c:366, posted by gary holman on Fri Apr 23 04:59:58 2021
|
Elog version: ELOG V3.1.4-611489ba
I am running openldap on the localhost. For some reason now, elogd is segfaulting when (I believe) when a new user is being added to the
password file. For example: |
|
Re: segfault in auth.c:366, posted by Sebastian Schenk on Fri Apr 23 15:46:39 2021
|
Hi Mr. Holman,
The problem you are facing is more likely the issue, that the LDAP method is only provided as-is from a different developer.
I had a similar issue with the LDAP of my university. |
|
Re: segfault in auth.c:366, posted by Stefan Ritt on Fri Apr 23 16:21:05 2021
|
Well, if you find a solution with works for everybody, I'm happy to commit it to the main repository. But unfortunately I cannot test it because
I don't have LDAP here, so I'm flying blind.
Stefan |
|
Re: segfault in auth.c:366, posted by Laurent Jean-Rigaud on Sun Apr 25 15:17:27 2021
|
Hi,
Maybe it could be useful to add new parameters in elogd.cfg to define the attribute name to use to retrieve the given name, login name and email
from LDAP server. |
|
Re: segfault in auth.c:366, posted by gary holman on Wed Apr 28 04:01:49 2021
|
Dear Mr Ritt, Mr Schenk,
Thank you for the responses. This was indeed my issue and direction to fix the crash.
Thank you, |