Re: Multi Logook Login, posted by Stefan Ritt on Wed Apr 15 09:51:35 2009
|
Hal Proctor wrote:
|
ROptions value changed in the edit page, posted by Gabriele Sirri on Wed Apr 15 11:43:14 2009
|
When ROptions items contain the same substring and this substring is also an ROptions item (ex: notdone,
done), the value of the entry could change in the edit page.
It depends on the item order in the config file.
|
|
Re: ROptions value changed in the edit page, posted by Stefan Ritt on Wed Apr 15 12:56:18 2009
|
> When ROptions items contain the same substring and this substring is also an ROptions item (ex: notdone,
> done), the value of the entry could change in the edit page.
> It depends on the item order in the config file.
|
|
Re: Multi Logook Login, posted by Yoshio Imai on Wed Apr 15 14:44:42 2009
|
Hi, Stefan!
[quote=Stefan Ritt]If [B]"password file = xxx"[/B] is however in each individual logbooks configuration, then you get [B]"path=/<lobook>"[/B]. You can |
|
Config so that users can delete only their own entries?, posted by Dennis Seitz on Wed Apr 15 17:57:19 2009
|
I've tried
Deny_Delete = All
|
|
Re: Config so that users can delete only their own entries?, posted by Stefan Ritt on Thu Apr 16 08:34:03 2009
|
[quote="Dennis Seitz"] I've tried
Deny_Delete = All
|
mail to localhost?, posted by Mike on Fri Apr 17 22:44:58 2009
|
Initially I thought you had to specify a port number after localhost for emailing.
As it turns out just putting "localhost" as the email server in the elog config
file works just fine. We have a strange problem where our elog server is running. |
|
Re: Config so that users can delete only their own entries?, posted by Dennis Seitz on Sat Apr 18 00:33:53 2009
|
Thanks for reminding me of that, it will do fine. A suggestion: Separate Restrict Edit into Restrict Edit and Restrict Delete or some functional equivalent.
Then we have the choice to restrict one or the other or both. Is that worth doing?
|