Re: Log Thread Close Automatically, posted by Stefan Ritt on Fri Mar 12 09:18:11 2010
|
| tom wrote: |
|
If you have a logbook and you create a new entry, is it possible to put a time limit on that new entry so that edits/replies are only valid for certain amount of time. I am looking for a way that would allow me to have a user start a new message, but after 8 hours, that message becomes locked and no one can edit or add to the message. This is for some shift work and we do not want users to go back after their shift and edit the messages.
|
What you need is
Restrict edit time = ...
as written in the manual. |
|
Re: Locking the Text field, posted by Stefan Ritt on Wed Jul 7 18:13:26 2004
|
> Is there a way to disable editing of the textarea, but still allow editing
> of other fields in the entry? (e.g. Fixed Attributes Edit = Text)
I could add that option, but I don't know if it helps you (see below).
> Also, is the data entered in that field accessible through a variable like
> $author? I tried $text, but that doesn't seem to work.
No, that won't work. Attributes are limite to some 500 characters, while the
text body is limited to 250000 characters. If you add $text to an attribute, it
would overflow or you would have to truncate the text, which I guess is not
good in both cases.
If you still want "Fixed attributes edit = text", please explain me you exact
case and I will consider implementing it. |
|
Re: Locking the Text field, posted by Todd Corsa on Fri Jul 9 18:14:59 2004
|
> > Is there a way to disable editing of the textarea, but still allow editing
> > of other fields in the entry? (e.g. Fixed Attributes Edit = Text)
I added a flag
Fix text = 0|1
A division in "fix text edit/fix text reply" does not make sense here, since I only
can lock the whole textfield, therefor just the switch.
New version under CVS (see download page). |
|
Re: Locking the Text field, posted by Todd Corsa on Mon Jul 12 15:13:56 2004
|
> > > Is there a way to disable editing of the textarea, but still allow editing
> > > of other fields in the entry? (e.g. Fixed Attributes Edit = Text)
>
> I added a flag
>
> Fix text = 0|1
>
> A division in "fix text edit/fix text reply" does not make sense here, since I only
> can lock the whole textfield, therefor just the switch.
>
> New version under CVS (see download page).
Thanks Stefan. Again, my hat is off to you for a great app.
Todd |
|
Re: Locking entries, posted by Stefan Ritt on Wed Sep 8 15:48:47 2004
|
One possibility is to use the option "Restrict edit time = <hours>". This way
an entry can only be edited let's say 8 hours after it has been created.
Another way is to maintain two logbooks, a "scratch" logbook and an "archive"
logbook. Users would put their entries into the scratch logbook, the staff
would examine it and move them to the archive logbook, where all users only
have read access to. To move entries between logbooks, you have to put the
"Move to" command in the configuration file like:
Menu commands = Back, New, Edit, Delete, Reply, Find, Move to, Config, Help |
|
Re: Locking a Thread, posted by Stefan Ritt on Wed Feb 13 16:27:18 2013
|
| Hal Proctor wrote: |
|
How can I set up the admins or manager group with the ability to Lock a Thread? I don't wish to keep two log books.
|
With
allow <command> = <user list>
deny <command> = <user list>
you can prevent certain users to use certain commands (like delete a message). If you only allow admins to issue the "edit" command, that would in principle do it, but then normal users cannot edit their entries any more. Unfortunately this command cannot be restricted to certain attributes, like the thread "status". So I guess what you want is not exactly possible with the current implementation. |
|
Re: Locking a Thread, posted by Hal Proctor on Wed Feb 13 16:56:40 2013
|
| Stefan Ritt wrote: |
|
| Hal Proctor wrote: |
|
How can I set up the admins or manager group with the ability to Lock a Thread? I don't wish to keep two log books.
|
With
allow <command> = <user list>
deny <command> = <user list>
you can prevent certain users to use certain commands (like delete a message). If you only allow admins to issue the "edit" command, that would in principle do it, but then normal users cannot edit their entries any more. Unfortunately this command cannot be restricted to certain attributes, like the thread "status". So I guess what you want is not exactly possible with the current implementation.
|
Thanks for the reply. I was looking for a way to stop replies to a runaway thread. Was wondering why the elog system has a "Locked by" attribute, but no way to set it. |
|
Re: Locking a Thread, posted by Stefan Ritt on Wed Feb 13 16:59:06 2013
|
| Hal Proctor wrote: |
|
| Stefan Ritt wrote: |
|
| Hal Proctor wrote: |
|
How can I set up the admins or manager group with the ability to Lock a Thread? I don't wish to keep two log books.
|
With
allow <command> = <user list>
deny <command> = <user list>
you can prevent certain users to use certain commands (like delete a message). If you only allow admins to issue the "edit" command, that would in principle do it, but then normal users cannot edit their entries any more. Unfortunately this command cannot be restricted to certain attributes, like the thread "status". So I guess what you want is not exactly possible with the current implementation.
|
Thanks for the reply. I was looking for a way to stop replies to a runaway thread. Was wondering why the elog system has a "Locked by" attribute, but no way to set it.
|
That's a different meaning. The "Locked by" flag gets set when one user edits an entry. During the editing the entry gets "locked", which means that no one else can change it during that time. This should prevent one person to overwrite the edits of another if they are editing the same entry at the same time. Your "locking" means the locking of threads, which elog doe not "understand", it's just your definition of an attribute in your logbook. |
|