> > With the "Preset text = " specified, when re-editing a logbook entry (say to
> > correct a spelling error) the text of the "Message" is replicated and placed
> > directly below the original text.
> 
> That should be fixed since revision 1.370 from Jul 7th, 2004. Please update.

Thanks!

> After THREE tries to enter a long detailed list of questions, all have been 
> replaced by just one:  why do ELOG textareas and entry forms lose all data 
> if the browser goes back/forward?  Or if a submission causes an error?  
> Other forms in other applications don't have this kind of data loss.
> 
> Submitting this now before I lose it again.  Will submit rest of questions 
> as separate entries.

Really strange. I tried with Mozilla Firefox and IE 6.0 and none of them lost
the entry data. What browser did you use? As far as I learned, data only
vanishes on pages which have an HTTP header containing "Expires: ..." with a
date in the past. But I made sure that the entry form does not contain this.

Please refreain in the future from sending many small entries. People being
registered with email notifications on the forum get flooded by notifications.
In worst case, write your posting using an editor and do copy-and-paste into a
single posting.

> > After THREE tries to enter a long detailed list of questions, all have been 
> > replaced by just one:  why do ELOG textareas and entry forms lose all data 
> > if the browser goes back/forward?  Or if a submission causes an error?  
> > Other forms in other applications don't have this kind of data loss.
> > 
> > Submitting this now before I lose it again.  Will submit rest of questions 
> > as separate entries.
> 
> Really strange. I tried with Mozilla Firefox and IE 6.0 and none of them lost
> the entry data. What browser did you use? As far as I learned, data only
> vanishes on pages which have an HTTP header containing "Expires: ..." with a
> date in the past. But I made sure that the entry form does not contain this.

IE 6.0.   

I am accessing an internal ELOG instance through an Apache reverse proxy on port
80, per the FAQ.  Just tested without the proxy and there is no data loss problem
with back/forward.  

When I access the ELOG forum, I am going through a forward proxy to the Internet,
which probably explains the data loss on error messages.

Will investigate proxy configuration regarding "Expires: " headers and post here
if I find a solution.

> Please refreain in the future from sending many small entries. People being
> registered with email notifications on the forum get flooded by notifications.
> In worst case, write your posting using an editor and do copy-and-paste into a
> single posting.

Sorry about that, will do.

The dump does not help me much. I need to reporduce the problem in a controlled environment.

Stefan

The solution is to use "Subst" instead of "Preset".

 This is not really resolved, since "Subst" creates a new number on both "New" and "Reply". I would like "Subst" to create a new number only on "New" and preserve this number through replies throughout the thread. I would like to be able to say "Subst thread = #" to make a new number for the thread and combine it with "Subst on reply thread = $thread" to preserve the number on replies, but this does not work. Maybe someone has already done this ?

Soren

 This can be solved with something like "Subst <attr> = $shell(cmd...) where cmd calculates a new value of attr, as a function of #, when attr does not already have a value. This thread is closed.
 

Soren

I just reworked the "Subst" command to make it more consistently. Now "Subst on Edit" and "Subst on Reply" are executed after the entry submission,  and they are mutually exclusive. So all you need right now is

Subst Tag = #

and it will not increment when editing or replying to an existing entry. The fix is in SVN revision 2264.