Re: Multiple ideas for multiple logbooks, posted by Yoshio Imai on Wed Apr 4 14:20:41 2007
|
[quote="Stefan Ritt"]Maybe some other problem?[/quote]
Possible, but I think it worked also on our server until the number of logbooks in the top group got larger than one. Can you try to see if your code still
works when there is more than one logbook defined? |
#include statements and attachment visibility, posted by Yoshio Imai on Thu Feb 28 19:07:19 2008
|
Hi!
First of all, thank you again for the great software and all the support.
|
Re: #include statements and attachment visibility, posted by Yoshio Imai on Thu Mar 6 18:19:48 2008
|
Thanks you! I just installed the new revision, and it works.
However, it does not seem to work in list mode (with attach=1 option): elog still shows [I]all[/I] the lines of attached text files there.
|
Re: #include statements and attachment visibility, posted by Yoshio Imai on Fri Mar 7 13:07:34 2008
|
| Thank you, works perfectly! |
Problems with elog client, posted by Yoshio Imai on Wed Apr 9 14:41:12 2008
|
Hi!
Since our upgrade to elog 2.7.3, it is not possible any more to edit an existing elog entry using the elog client with -e <id> option. |
|
Re: Problems with elog client, posted by Yoshio Imai on Thu Apr 10 14:21:13 2008
|
I have tried the new revision, recompiling both client and server.
Unfortunately, the overall situation has not changed. We can still create new entries using the [I]elog[/I] client, but editing an existing entry still
does not work. However, thanks to your patch, the [I]-v[/I] option now works again for the client side:
|
|
Re: Problems with elog client, posted by Yoshio Imai on Thu Apr 10 15:56:12 2008
|
[quote="Stefan Ritt"]As I wrote in my previous message, the "SSL part has not been tested" (=means: does not work).[/quote]
Sorry for the misunderstanding. I was probably confused because the creation of new entries already worked, even with SSL.
|
|
Re: Problems with elog client, posted by Yoshio Imai on Thu Apr 17 19:11:36 2008
|
I have tried your sample config file, and this one also works for me.
The problem arises when using top groups. I have produced a minimal config file including a top group, of the form
[CODE]
|