Hello.

Please look at the entry 66525 of this forum (just 5 thread before this one):

 ->  chain.crt, posted by Gerhard Schneider on Thu Sep 3 21:55:52 2009         (66525)
  |->    Re: chain.crt, posted by Stefan Ritt on Fri Sep 4 08:33:16 2009       (66526)
  |->    Re: chain.crt, posted by Gerhard Schneider on Wed Oct 7 07:56:52 2009 (66556)

When you collapse the thread, it is collapsed to the 66526 instead of the 66556 (more recent)

  +      Re: chain.crt, posted by Stefan Ritt on Fri Sep 4 08:33:16 2009  

I guess it is because both 66526 and 66556 replies to the first entry. 
I have the same problem with Elog v2.7.7-2246 and Windows. 

In general, it seems to work well only if you always reply to the last entry of a thread.

  Thank you.


b.t.w. : is there any tip to always force reply to the last entry of a thread?

Dear all,

Is it possible to have a dynamic "preset text" option without remplace text if it has changed?

I would like to switch the template file depending on the attribute value (Type). 

If user already started editing the text body, on change (Type) he could lose this data. 

I'm using this example code :
Attributes = Type, Subject
Options Type = One{1}, Two{2}, Three{3}
Show text = 0

{1} Preset text = text1
{2} Preset text = text2
{3} Preset text = text3
{1,2,3} Show text = 1

I the attribute type change the user lost the data, because the text has been replaced.

Any idea about how to solve it?

Thanks!
Cheers

Here are some things for your wish list:                                        
                                                                                
1) elogd should report quota or disk-full problem:  In case a logbook           
   entry cannot be saved (quota or disk full) then a message like               
   'Could not save last entry.  Please contact administrator.' should           
   be displayed.  Currently nothing happens.  Only the submitted                
   entries 'vanish'.                                                            
                                                                                
2) default page view per user, i.e. the 'Back' link goes to                     
   ?mode=Full,summary,... depending on the user that is logged in.              
   Some users complained that 'Back' is not really back.  Maybe                 
   consider renaming 'Back' to 'Default View' or something.                     
                                                                                
3) (related to 1) the 'Back' link should go back to the last used mode          
   (full, summary, threaded,...) and not to the default mode                    
                                                                                
4) mark messages as unread/read on a per user basis: The                        
   implementation of this might be quite involved but it would be               
   rather useful.  One way would be to add a default attribute 'Seen            
   by' to each entry, which lists the login names of the users.  Or 
   files LOGIN_NAME.has_seen can be created which contain the entry 
   IDs of the viewed entries for each user.   
                                                                                
5) alignment of attribute table (using <td colspan=2> for multi line            
   stuff): see elog:669 :)                                                      
                                                                                
You can count my vote for:                                                      
                                                                                
- Use "and" and "or" operands in queries                                        
                                                                                

I g

Hello to all,
i'm running ELOG on FreeBSD 5.2.
We've noticed an issue where e-mail notification from ELOG seem to
have their arrival time in the future, looks like it's about 13 hours ahead.


E-mail gateway to which ELOG posts its e-mail shows this e-mail transaction:
--------------------------------------------
Received: from elogunixbox.somewhere.net ([x.x.x.x]) by  
mailunixbox.somewhere.net with SMTP id <143408>; Mon, 11 Oct 2004 12:22:43 
+1300
To: crypt0@somewhere.net
From: elogposter@somewhere.net
Subject: New ELOG entry
X-Mailer: Elog, Version 2.5.3
X-Elog-URL: http://elog.somewhere.net/somelogbook/47
X-Elog-submit-type: web|elog
Date:  Mon, 11 Oct 2004 12:26:28 -3736512
--------------------------------------------


The last line in that log seems to have some strange time zone offset
(-3736512)
Usually you'd see a GMT+13 (New Zealand time zone on summer time).


Here's ELOG's own logs of that same e-mail delivery:
--------------------------------------------
11-Oct-2004 12:26:28 [crypt0@somepc.internal.lan] {somelogbook} X-Mailer: 
Elog, Version 2.5.3
11-Oct-2004 12:26:28 [crypt0@somepc.internal.lan] {somelogbook} X-Elog-URL: 
http://elog.somewhere.net/somelogbook/47
11-Oct-2004 12:26:28 [crypt0@somepc.internal.lan] {somelogbook} X-Elog-
submit-type: web|elog
11-Oct-2004 12:26:28 [crypt0@somepc.internal.lan] {somelogbook} Date: Mon, 
11 Oct 2004 12:26:28 -3736512
11-Oct-2004 12:26:28 [crypt0@somepc.internal.lan] {somelogbook} Content-
Type: TEXT/PLAIN; charset=US-ASCII
--------------------------------------------

I noticed that there was a post talking about ELOG on MacOSx having some 
time issues, but nothing mentioning FreeBSD..

Any ideas?
Thanks to all in advance.
GL.

It would be nice if elogd would recognise the whole of this as a link
http://support.microsoft.com/default.aspx?scid=kb;en-us;138354 rather than 
just the first bit.

Has been fixed in revision 1.492.