> > 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.

> Display Subsystem = <a href="/LogBook1/?Subsystem=$Subsystem" style="color:
> saddlebrown">$Subsystem</a>
> 
> ABC and DEF links would perform filter searches of a _different_ logbook.   
> 
> MOptions does not work because the options are not fixed.   The options can be any
> numeric ID for items in a related logbook.
> 
> Consider the case of two logbooks, where we wish to associate items in the second
> logbook with more than one item in the first logbook.  We could define separate
> attributes for each "parent item", e.g. Parent1, Parent2, Parent3, then use a
> "Display" spec to convert a numeric ID into a hyperlink to the first logbook's item.
>   The exact relationship is not important, could be parent/peer/child - some generic
> relationship.
> 
> The benefit here would be the same as having separate links for MOptions attribute
> values.

Ah, now I'm getting your point. You want kind of relational database where a logbook
correspond to a table, using the entry ID as primary key. Well, elog was not designed
having that in mind, so its capabilities will always be very limited. A MySQL with
phpMyAdmin might be better for that.

But what you could do is to put manual links betweek logbooks. If you enter in an
attribute following text:

elog:Forum/816 elog:Forum/806

then you get two links to entries 806 and 816. Writing this is a bit more than just 
"816 | 806", but it's less than writing directly an HTML link.

When creating new logbooks, I will create a single entry to test the  
configuration. After revising the configuration I want to delete that  
single entry and create a new one based on the revised config.  
  
elogd will crash every time upon deleting that single entry with an  
xrealloc error. Here are the syslog entries leading up to the crash:  
  
Oct  9 08:09:41 obstin8 elogd[20614]:  
GET /Support/1?cmd=Delete&nextmsg=0&confirm=Yes HTTP/1.1^M Connection:  
Keep-Alive^M User-Agent: Mozilla/5.0 (compatible; Konqueror/3.3; Linux)  
(KHTML, like Gecko)^M Referer: http://localhost:8080/Support/1?cmd=Delete^M  
Accept: text/html, image/jpeg, image/png, text/*, image/*, */*^M  
Accept-Encoding: x-gzip, x-deflate, gzip, deflate^M Accept-Charset:  
iso-8859-1, utf-8;q=0.5, *;q=0.5^M Accept-Language: en^M Host:  
localhost:8080^M Cookie: urem=0; upwd=dDRubjNyBDI=; unm=mstolove  
Oct  9 08:09:41 obstin8 elogd[20614]: xrealloc: not enough memory  
  
This is on a Slackware 10 box using kernel 2.6.7. Elogd is accessed  
directly, not through an Apache proxy.  

This problem has been fixed in revision 1.491 and will be published in version
2.5.4-6.

Has been fixed in revision 1.492.

> Has been fixed in revision 1.492.

Thanks, Stefan.

I have the following in a local logbook config: 
 
  append on edit = "\n\n[$date: $short_name]\n" 
 
When I upload an attachment to an entry, it appears like the page is 
getting refreshed in the browser and the 'append on edit' action is called 
again. This results in two appended strings in the text entry, one for the 
initial edit and one for the upload. 
 
Is this by design or an inadvertent result of uploading an attachment? 
 
My preferred handling of this - and perhaps a more intuitive behavior - 
would be to have the append/prepend actions happen once and only once for 
each edit or reply. 
 
BTW Stephan, many thanks for the great program. 

I have the following in a local logbook config: 
 
  append on edit = "\n\n[$date: $short_name]\n" 
 
When I upload an attachment to an entry, it appears like the page is 
getting refreshed in the browser and the 'append on edit' action is called 
again. This results in two appended strings in the text entry, one for the 
initial edit and one for the upload. 
 
Is this by design or an inadvertent result of uploading an attachment? 
 
My preferred handling of this - and perhaps a more intuitive behavior - 
would be to have the append/prepend actions happen once and only once for 
each edit or reply. 
 
BTW Stephan, many thanks for the great program.