Re: Is there a way to limit users to view only the entries they have created?, posted by Herman Sherman on Tue Sep 9 16:12:45 2008
|
| Stefan Ritt wrote: |
|
| Herman Sherman wrote: |
|
We are using elog to allow users to enter their time spent on a project and we would like them to be able to see the entries that they themselves have
created but not the entries that other users have created.
Thanks,
Herman
|
In that case you have to make one logbook per user and restrict the access to it using the "Login user = ..." directive.
|
I understand.
Thank you for the quick response. |
Moving individual messages in a thread, posted by Eoin Butler on Sat Sep 13 23:34:37 2008
|
It is possible that the Move to... and Copy to... commands can be configured so that when they operate on a message that is part of a thread, that only that message will be moved, instead of the whole thread? |
|
Re: Moving individual messages in a thread, posted by Stefan Ritt on Thu Sep 18 14:39:17 2008
|
| Eoin Butler wrote: |
|
It is possible that the Move to... and Copy to... commands can be configured so that when they operate on a message that is part of a thread, that only that message will be moved, instead of the whole thread?
|
This has not been implemented on purpose. Assume you have a thread with
A
B
C
So A links to B, B links back to A and so on. If you would move now B into another logbook, A and C would point to an entry which does not exist any more. Furthermore, C may contain some sentences which are a reply to something which has been said in B. So even if the "Move To" mechanism would re-link A to C and C to A, the entry C would maybe make no sense any more if B is missing. That's why you only can move threads as a whole. If you want to move individual messages, don't use replies. You can actually disable the reply command in the configuration file. |
Deny Wildcards, posted by Neo on Wed Oct 8 15:10:25 2008
|
|
Ist there a possibility to use wildcards specifiing the users who are allowed to use a command, like ...
Allow New = admin1, admin2, admin3
Allow Edit = admin1, admin2, admin3
Deny New = *
Deny Edit = * |
|
Re: Deny Wildcards, posted by Stefan Ritt on Wed Oct 8 15:23:56 2008
|
| Neo wrote: |
| Ist there a possibility to use wildcards specifiing the users who are allowed to use a command, like ... Allow New = admin1, admin2, admin3 Allow Edit = admin1, admin2, admin3 Deny New = * Deny Edit = * |
Wildcards are not implemented for that purpose. But a "Allow New = admin1, admin2" implicitly denies this command for all other users, I guess that's what you want. There is also the possibility to use "Guest Menu Commands" to allow everybody to read entries, but only logged in users to write and modify them. |
|
Re: Deny Wildcards, posted by Neo on Wed Oct 8 15:31:49 2008
|
| Stefan Ritt wrote: |
|
| Neo wrote: |
| Ist there a possibility to use wildcards specifiing the users who are allowed to use a command, like ... Allow New = admin1, admin2, admin3 Allow Edit = admin1, admin2, admin3 Deny New = * Deny Edit = * |
Wildcards are not implemented for that purpose. But a "Allow New = admin1, admin2" implicitly denies this command for all other users, I guess that's what you want. There is also the possibility to use "Guest Menu Commands" to allow everybody to read entries, but only logged in users to write and modify them.
|
I tried it in a global group configuration
[global monitoring]
Allow Edit = admin1, admin2
Allow New = admin1
But I as admin2 am still able to create new entries in the corresponding log books.
Is this configuration only for logbooks? |
|
Re: Deny Wildcards, posted by Stefan Ritt on Wed Oct 8 21:37:32 2008
|
| Neo wrote: |
|
I tried it in a global group configuration
[global monitoring]
Allow Edit = admin1, admin2
Allow New = admin1
But I as admin2 am still able to create new entries in the corresponding log books.
Is this configuration only for logbooks?
|
I just tried myself with following config:
[global]
port = 8080
password file = passwd
Allow New = joe
[demo1]
Theme = default
Attributes = Author, Subject
and it jus worked fine. When I'm not logged on as "joe", the "New" command even does not appear. If you would have supplied your correct ELOG version, I could have checked if you have an old version. In that case you could upgrade. |
|
Guest Account doesnt work, posted by Brassmann on Mon Oct 13 13:06:59 2008
|
Hi ,
i have a little problem with the guest access. There is no acces to the logbooks as a guest. Evereytime i see the loginbox after clicking the logbook.
[Informations]
Guest menu commands = List, Back, Find, Login, Help
Guest find menu commands = List, Find, Select, Login, Help
Password file = ./passwd
Self register = 1
Logfile = elogd.log
Logging level = 3
Login expiration = 24
Admin user = testuser
Theme = default
Preset Author = $long_name
Attributes = Author, Subject
Locked Attributes = Author
Required Attributes = Author, Subject
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Subtext
Thanks for help, Brassmann |
|