Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 335 of 808  Not logged in ELOG logo
    icon2.gif   Re: Record date isn't set to current date when replying to elogs, posted by Stefan Ritt on Mon Apr 15 17:50:20 2024 
Have you tried the config option "Preset on reply <attribute> = $date". On a reply, the <attribute> will be preset with the current
date.

Stefan
    icon2.gif   Re: Record Proliferation, posted by Stefan Ritt on Wed Mar 14 14:45:23 2012 


    
        
            Paraic Fahey wrote:
        
        
            
            Saving, using Submit sees recently updated fields cleared after hitting SUBMIT.
    icon5.gif   Re: Record Proliferation, posted by David Pilgram on Wed Mar 14 15:34:41 2012 


    
        
            Stefan Ritt wrote:
        
        
            
            
            
    icon2.gif   Re: Record ID corruption, posted by David Pilgram on Sun May 3 18:05:32 2020 
Hi,

I've had problems in the past due to a dodgy pointer creating branches despite a "No branches" in the configuration file. 
It would be very interesting to see what the 200428a.log file looks like with these entries: in the screenshot they appear to be shown in time order, but
    icon2.gif   Re: Record ID corruption, posted by Frank Baptista on Sun May 3 22:43:12 2020 200428a.log
Hi David,

Thanks for the quick response!  Well, I'd have to say that the sequence is as tangled as it looks in the logbook -- I've attached
a copy of the log file for your reading pleasure. 
    icon2.gif   Re: Record ID corruption, posted by David Pilgram on Mon May 4 14:55:53 2020 
Hi Frank,

There are two interesting points about the log file. 

1.  Entry 5658 is timestamped later than 5659, but is earlier in the entry list.  It also is "In Reply to" 5659. despite
    icon2.gif   Re: Record ID corruption, posted by Frank Baptista on Fri May 22 21:03:05 2020 
Hi David,

Well, you've made some very interesting observations, and raised some excellent questions.  So, I went back and did some homework, reviewing
a number of logbooks to find instances where this strange 'record twist' occurs.  You had asked, "Do you have enough information to decided
    icon2.gif   Re: Record ID corruption, posted by David Pilgram on Sat May 23 16:15:38 2020 
Hi Frank,

Good bit of detective work.  To me it suggests that something as yet undetermined occurs, that, when the 57th reply happens, causes the
issue.  If that "something" hasn't happened, all is well.  Apart from Heinz varieties (not true, in fact), 57 isn't an obvious
ELOG V3.1.5-3fb85fa6