> this is happened before, and it just happened upgrading from 2.2.2 to 2.2.3
> 
> the link at the bottom of the page shows a previously installed version.
> 
> i don't install to the elog directory, i install to a ram disk and copy 
over the new executables, the source, readme and help html.
> 
> the link showed 2.1.2 until i upgraded to 2.2.2 (i didn't do anything 
different than the above. now i'm at 2.2.3 and the link is showing 
2.2.2...not that it's a big deal, i'm just wondering what i did wrong

Of course you have to stop the old elogd program and start the new one. Have 
you done that?

> > Of course you have to stop the old elogd program and start the new one. 
Have 
> > you done that?
> 
> on windows i run it as a service through firedaemon, but i stop it before 
upgrading...that was one of the first things i checked...

Well, the other thing is that the previous page is till in the cache of 
Netscape. You have to hit "Reload" in order to properly update the page.

Besides these two things - browser cache and not stopping the old versoin - 
there is no possibility how you could see the old version at the bottom of 
the page, I update this very carefully on each distribution.

Ooops, I just realized that the Windows 2.2.3 distribution contained the old 
(2.2.2) executable for elogd.exe. I apologize for that. I have updated the 
elog223.exe distribution just now, so please download it again in order to 
get the new file.

- Stefan

> In the "find" command, when searching over all logbooks, it
> would be nice to see ALL attributes, which are common for all
> logbooks (e.g. typically the author name), not just
> logbook name, date and text.

That depends on how you specify what gets displayed in a search (with 
the "Display search" option for example). If you try the following link:

http://midas.psi.ch/elogdemo/Forum/?mode=summary&all=1

you see that all attributes are displayed from the three logbooks in this 
installation.

> > > In the "find" command, when searching over all logbooks, it
> > > would be nice to see ALL attributes, which are common for all
> > > logbooks (e.g. typically the author name), not just
> > > logbook name, date and text.
> > 
> > That depends on how you specify what gets displayed in a search (with 
> > the "Display search" option for example). If you try the following link:
> > 
> > http://midas.psi.ch/elogdemo/Forum/?mode=summary&all=1
> > 
> > you see that all attributes are displayed from the three logbooks in 
this 
> > installation.
> 
> How does the corresponding elogd.cfg entry look like for the
> display search command ? - I can't reproduce this behaviour...

Ok, finally I can confirm the problem. It will be fixed from Version 2.2.4 
on.

Starting from version 2.2.4 which has been released today, the 
option "quick filter" has been added. A "quick filter" is a drop down box 
on the message display page. By selecting a value from the drop down box, 
only messages of that type are displayed. See this forum which uses "Quick 
filter = Date, Category".

This new option adresses a couple of installations which require a large 
number of logbooks. Instead of using many similar logbooks, the old logbook 
name can now be defined as an attribute. All messages get now mixed, but by 
defining the logbook attribute as a quick filter, one can display the 
messages belonging to the individual logbooks separately with a single 
click.

> unless i missed these in the docs some place:
> 
> 1) a threaded display but collapsed threads unstead of all replies showing

This feature has been added in Version 2.2.4 which has been released today. 
Use the "collase" button.
 
> 2) the subject is the link along with the icon. it would make it a little   
easier to click on the message if you run your montior on a high resolution...

This feature has been added in Version 2.2.4 as well. Use "line as link = 1" 
in elogd.cfg

> i have expand flag set to 0 but it doesn't seem to be working...

It workes here flawlessly. Can you double check the spelling etc. If 
everything is ok, can you send me your elogd.cfg for analysis?

- Stefan