Ok, I found the issue. The "Restrict edit time" is only checked when one clicks on "Edit" in the browser. The elog command line tool does not really an edit, but just submits an entry with an (old) ID. I added a check also for that case so now it should work. The commit is in git.
Stefan
| Heinz Junkes wrote: |
|
Stefan, will send the info off this forum.
Heinz
| Heinz Junkes wrote: |
|
I ask my users where they had the problems and then create a demo for testing.
Thanks Heinz
| Stefan Ritt wrote: |
|
So you are telling me that "Restrict edit time" is not working correctly? In order to fix any problem, I have to reproduce it. Can you post a minimel elogd.cfg file with which I can reproduce the problem?
Stefan
| Heinz Junkes wrote: |
|
Sorry,
I meant "read only" by using "Restrict edit time" settings. e.g.
Restrict edit time = 24
I understand this to mean that an entry should not be able to be modified after 24 hours.
Heinz
| Stefan Ritt wrote: |
|
There is no "read only" flag. Please describe what you exactly did. Probably you want "Restrict edit time" for that.
Stefan
| Heinz Junkes wrote: |
|
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
| Stefan Ritt wrote: |
|
There are two ways:
1) Use different password files for different logbooks. Each password file contains only those users which have access to that logbook.
2) Use "Login user = <usr list>" to restrict access to certain users in that list.
Stefan
| Heinz Junkes wrote: |
|
Since there's no answer to that.
I am the only one with the problem? Did I just configure something wrong?
Thanks Heinz
| Heinz Junkes wrote: |
|
submissions via the elog - program can overwrite entries even if the user has no edit rights
|
|
|
|
|
|
|
|
|
|