Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon5.gif   Duplicate entries, posted by Alan Grant on Thu Mar 16 15:15:34 2017 
    icon2.gif   Re: Duplicate entries, posted by David Pilgram on Thu Mar 16 16:11:02 2017 
       icon2.gif   Re: Duplicate entries, posted by Harry Martin on Wed Dec 2 04:07:57 2020 
          icon2.gif   Re: Duplicate entries, posted by David Pilgram on Wed Dec 2 15:57:25 2020 
             icon2.gif   Re: Duplicate entries, posted by Harry Martin on Wed Dec 2 17:54:51 2020 
                icon2.gif   Re: Duplicate entries, posted by David Pilgram on Wed Dec 2 18:22:37 2020 
                   icon2.gif   Re: Duplicate entries, posted by Harry Martin on Wed Dec 2 22:13:52 2020 
Message ID: 69266     Entry time: Wed Dec 2 04:07:57 2020     In reply to: 68581     Reply to this: 69268
Icon: Reply  Author: Harry Martin  Author Email: harrymartin772@gmail.com 
Category: Question  OS: Linux  ELOG Version: 2.9.2-2475 
Subject: Re: Duplicate entries 

I find that I can reply to a message ("original" message, if you will) without doing anything to the reply message (the "copy" of the original message, if you will).  If I then submit it, it gets saved as a new message, identical to the one I replied to.

I read through the options at the end of the docs.  I did not see anything about a way to suppress identical messages, or a way to force the user to make some kind of change to make the reply different from the original.

David Pilgram wrote:

I've seen exact;y this effect, even though I have branching = 0 in my config file - so ordinarily no chance to have two
 replies to an entry.  My pointer aka mouse (I'm on Linux) is a bit dodgy, and sometimes disconnects/reconnects, so in effect gives a very fast double click.  I've always assumed that was the cause of the problem.  The two replies have incremental IDs, and both those IDs are listed in the "Reply to" header section of the entry.  I'm not sure how this overcomes the branching = 0 detail, though.

That is what I have assumed, but if others see this on occasion, perhaps it's got a different cause.

Alan Grant wrote:

Periodically (rarely) on manually adding a record into Elog it generates a duplicate record with its own incremented ID and I don't know why. I just delete the duplicate in the meantime but would like to know if anyone else has seen this and whether their is a answer/fix for it. Thanks.

 

 

ELOG V3.1.5-fe60aaf