Re: Dynamic attribute values, posted by Stefan Ritt on Tue Nov 10 15:00:15 2009
|
Steve Williamson wrote:
Hi |
|
Re: Dynamic attribute values, posted by Steve Williamson on Fri Nov 13 14:28:25 2009
|
Stefan Ritt wrote:
|
|
Re: Duplicate of a reply should be a reply, posted by Stefan Ritt on Mon Jul 17 13:49:37 2006
|
[quote="Gerald Ebberink"]Hello everybody
This weekend I found that if I duplicate a reply it does not become a reply it self.
|
|
Re: Duplicate entry suggestion, posted by Stefan Ritt on Tue Apr 1 08:01:02 2008
|
Dennis Seitz wrote:
We have configured several logbooks to allow users to duplicate an entry in another logbook, which |
|
Re: Duplicate entry suggestion, posted by Dennis Seitz on Tue Apr 1 20:31:26 2008
|
Stefan Ritt wrote:
|
|
Re: Duplicate entries, posted by David Pilgram on Thu Mar 16 16:11:02 2017
|
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 |
|
Re: Duplicate entries, posted by Harry Martin on Wed Dec 2 04:07:57 2020
|
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 |
|
Re: Duplicate entries, posted by David Pilgram on Wed Dec 2 15:57:25 2020
|
I'm not sure if this is what you want.
If you want to prevent "accidental" replies being identical to the original message, you can force a situation where the user will
be alerted that they have to do something if they really want to make a reply. |