Yes, I have been manually sorting and resorting. We have extendable attributes and the list keeps growing so I have to resort every so often. I thought perhaps a simple alphanumeric sort as an option would be popular with most users so I thought I'd ask for it. It would really simplify things for me. Users who want to sort manually could do so by disabling the option. It never hurts to ask!

Ok, I implemented

Sort attribute options = 1

in the current SVN revision. 

* Withdrawn *

The HTML layout produced by elogd is horrendous to deal with programmatically; I give up.

Hi,

I'm writing a greasemonkey script to slightly alter the look of the pages served by the ELOG server.  One difficulty that I'm struggling with is how to identify what type of page ELOG has created.  While I have several methods to determine the page type, such as a log entry vs. log entries summary, the solutions are not straight forward and not clean.  As far as I tell, there's no specific identification in HTML document currently that describes and identifies the type of page being served by the ELOG server.

So, I'm requesting that the pages created by ELOG be identified in some fashion with the META element, such as:

    <meta name="description" content="elog log entry" />

or

    <meta name="description" content="elog log summary" />

or even using the keywords attribute:

    <meta name="keywords" content="elog log summary" />

Thanks!

Sorry, I didn't yet have time to implement your request.

Have you considered to download an entry in plain text? Like this entry you can load with

https://midas.psi.ch/elogs/Forum/66555?cmd=Download

which should be much easier to interprete. If you write your entries in ELCode or plain format, it should be even easier. 

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?

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

As the person who suggested this concept, I have to admit I've yet to think of a good way around this issue. 
Preventing "branching" is all very well, but sometimes it is relivent to have a branch (although I usually try to
avoid them).  Unless elog scans every possible branch to find where the latest entry, I cannot think of a
foolproof, practical scheme.