| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
68939
|
Wed Apr 24 11:03:26 2019 |
 | Heinz Junkes | junkes@fhi-berlin.mpg.de | Bug report | All | elogd 3.1.4 | Re: elog program does not respect "Allow edit" list |
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
|
|
|
|
|
|
|
68940
|
Wed Apr 24 11:30:37 2019 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | All | elogd 3.1.4 | Re: elog program does not respect "Allow edit" list |
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
|
|
|
|
|
|
|
|
68941
|
Wed Apr 24 11:56:24 2019 |
| Heinz Junkes | junkes@fhi-berlin.mpg.de | Bug report | All | elogd 3.1.4 | Re: elog program does not respect "Allow edit" list |
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
|
|
|
|
|
|
|
|
|
68944
|
Fri Apr 26 11:24:21 2019 |
| Heinz Junkes | junkes@fhi-berlin.mpg.de | Bug report | All | elogd 3.1.4 | Re: elog program does not respect "Allow edit" list |
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
|
|
|
|
|
|
|
|
|
|
68945
|
Fri Apr 26 17:22:46 2019 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | All | elogd 3.1.4 | Re: elog program does not respect "Allow edit" list |
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
|
|
|
|
|
|
|
|
|
|
|
68986
|
Fri Jun 14 11:29:30 2019 |
 | Sebastian Schenk | sebastian.schenk@physik.uni-halle.de | Bug report | All | 3.1.4 | Find cannot find values with brackets |
For demonstration, I created https://elog.psi.ch/elogs/Linux+Demo/8
The Find search for category aaa(bb) does not give results.
A quick filter corrects the value to aaa\(bb) and delivers results.
I made a simple fix and submitted it as PR to the bitbucket repository. |
|
68987
|
Fri Jun 14 12:43:04 2019 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | All | 3.1.4 | Re: Find cannot find values with brackets |
I‘m happy to merge the PR after a quick test next week.
Stefan
| Sebastian Schenk wrote: |
|
For demonstration, I created https://elog.psi.ch/elogs/Linux+Demo/8
The Find search for category aaa(bb) does not give results.
A quick filter corrects the value to aaa\(bb) and delivers results.
I made a simple fix and submitted it as PR to the bitbucket repository.
|
|
|
69028
|
Wed Oct 9 12:39:45 2019 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | All | 3.1.4 | Re: Email boolean |
> > Hello Elog forum
> >
> > Is it possible to email boolean statements, like if a checkbox is checked to email certain people?
> >
> > My Configuration looks like this but dosn't work:
> >
> > Attributes = Bruger, Station, Emne, Status, PM5
> > Options PM5 = boolean
> > Email PM5 = fj@tvis.net
> >
> > Kind Regards
> >
> > Finn
>
> I still don't have a solution to the above, but this works:
>
> Attributes = Bruger, Station, Emne, Status, PM5
> ROptions PM5 = Ja
> Email PM5 Ja = th@tvis.net, fj@tvis.net
>
> Kind Regards
>
> Finn
You were so close: boolean has the two values "0" (unchecked) and "1" (checked).
Attributes = Bruger, Station, Emne, Status, PM5
Options PM5 = boolean
Email PM5 1 = fj@tvis.net
That does work, I've tested it. |