Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 351 of 807  Not logged in ELOG logo
    icon2.gif   Re: Problems with execute delete, posted by Stefan Ritt on Tue Dec 23 12:22:51 2008 
 

    
        
            Stefan Kanitz wrote:
        
        
            
    icon2.gif   Re: Problems with execute delete, posted by Stefan Kanitz on Tue Dec 23 12:31:39 2008 


    
        
            Stefan Ritt wrote:
        
        
            
             
    icon2.gif   Re: Problems with elog client, posted by Stefan Ritt on Wed Apr 9 23:03:53 2008 


    
        
            Yoshio Imai wrote:
        
        
            
            Since our upgrade to elog 2.7.3, it is not possible any more to edit an existing elog entry using the elog
    icon2.gif   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:
    icon2.gif   Re: Problems with elog client, posted by Stefan Ritt on Thu Apr 10 15:39:26 2008 
[quote="Yoshio Imai"]
[CODE]> elog -s -h elog -p 443 -l current -u <user> <password> -e 1 "EDIT THIS ENTRY" -v
Successfully connected to host elog, port 443
    icon14.gif   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.
    icon2.gif   Re: Problems with elog client, posted by Stefan Ritt on Tue Apr 15 20:34:49 2008 
[quote="Yoshio Imai"]Another thing: I have noticed that when using conditional preset texts, the "Preset Text =" statements have to be declared for each
logbook of a logbook group; it is not sufficient to only declare it in the "[global]" section of the logbook group. This means that we only need to declare
the conditions once, e.g.
    icon2.gif   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]
ELOG V3.1.5-3fb85fa6