elog program does not respect "Allow edit" list, posted by Heinz Junkes on Mon Mar 11 11:18:02 2019
|
| submissions via the elog - program can overwrite entries even if the user has no edit rights |
Re: elog program does not respect "Allow edit" list, posted by Heinz Junkes on Wed Apr 24 09:43:02 2019
|
Since there's no answer to that.
I am the only one with the problem? Did I just configure something wrong?
Thanks Heinz |
|
Re: elog program does not respect "Allow edit" list, posted by Heinz Junkes on Wed Apr 24 10:21:58 2019
|
Thanks for the answer. The real problem is that you can overwrite existing entries even if you have set an entry to "read only", i.e. you have
forbidden further editing.
Heinz |
|
Re: elog program does not respect "Allow edit" list, posted by Heinz Junkes on Wed Apr 24 11:03:26 2019
|
Sorry,
I meant "read only" by using "Restrict edit time" settings. e.g.
Restrict edit time = 24 |
|
Re: elog program does not respect "Allow edit" list, posted by Heinz Junkes on Wed Apr 24 11:56:24 2019
|
I ask my users where they had the problems and then create a demo for testing.
Thanks Heinz
Stefan |
|
Re: elog program does not respect "Allow edit" list, posted by Heinz Junkes on Fri Apr 26 11:24:21 2019
|
Stefan, will send the info off this forum.
Heinz
Heinz |
elog server crashed due to cookies send by client, posted by Heinz Junkes on Mon Sep 18 13:49:05 2023
|
Our elog instance (elogd 3.1.4 built Jan 13 2021, 20:44:20 revision ce2a48e9) has been running for years without any problems.
We have a new user who consistently crashes the elog:
GET /Omicron-STM-XPS/?rsort=Record%20date HTTP/1.1 |
|
Re: elog server crashed due to cookies send by client, posted by Heinz Junkes on Tue Sep 19 10:58:14 2023
|
The server is crached because the author field was accidentally filled with a long string due to an automated (remote) script:
“
Author: The ion getter pump has successfully recovered and appears to be operating steadily once more. Consequently, I proceeded with sputtering |