Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 574 of 808  Not logged in ELOG logo
    icon2.gif   Re: Default Date Format, posted by Stefan Ritt on Tue Apr 12 09:13:27 2005 
> I downloaded the latest file and installed but the version number stayed at 
> 2.5.8-2 and did not change to -3.
    icon2.gif   Re: Default "Author" when replying to a log entry, posted by Stefan Ritt on Tue Feb 1 15:43:00 2022 
As you can see, on this forum the author for replies is correct. This is done via the config option:

Preset on reply Author = $long_name




Jan
    icon2.gif   Re: Default "Author" when replying to a log entry, posted by Jan Just Keijser on Tue Feb 1 16:43:34 2022 
Excellent, exactly what I was looking for, many thanks!

 




Stefan
    icon2.gif   Re: Deamon on Debian, posted by Stefan Ritt on Tue Jun 8 09:21:16 2010 


    
        
            Marco Rojas wrote:
        
        
            
            Hi,
    icon2.gif   Re: Datetime format with elog client, posted by Alan Grant on Wed Oct 26 21:41:42 2016 
UPDATE:

As I continue to test and troubleshoot this problem I noticed something peculiar: the Datetime defined field that the client is rejecting when
I attempt a record insert is listed as a Required attribute. However, when I just remove it from the Required list the record including
    icon2.gif   Re: Datetime format with elog client, posted by David Pilgram on Wed Oct 26 22:15:46 2016 
Hi Alan,

I have no idea if this helps but the Date and Time formats in the config file internally interconnect, as I discovered in trying to define them
separately.  Define one, and the other is defined.
    icon2.gif   Re: Datetime format with elog client, posted by Alan Grant on Thu Oct 27 04:16:10 2016 
I really appreciate your reply David.

There's only one Datetime defined field that I'm working with so I'm not sure what you mean, if you don't mind elaborating?
It sounds interesting.
    icon2.gif   Re: Datetime format with elog client, posted by Andreas Luedeke on Thu Oct 27 11:18:17 2016 
Yes, this is a known bug of ELOG, see elog:68404




Alan
Grant wrote:



UPDATE:
ELOG V3.1.5-3fb85fa6