Starting from version 2.2.5 on, an new directory scheme has been 
implemented. The idea is to separate the config file from the theme/icon 
and the logbook directories. This can now be achieved by specifying the 
configuration file via the "-c" flag and the directories with the "-d" flag 
for the logbook root and the "resource directory" with the "-s" flag.

Alternatively, the resouce and logbook directories can be specified in the 
configuration file with

Resource dir = ...
Logbook dir = ...

The old "Data dir" statement is still possible but deprecated. Instead, the 
statement "Subdir = ..." should be used which is taken relative to 
the "Logbook dir". If no "Subdir" is given, the logbook name itself is used 
as the subdir. For this demo logbook I use now:

[global]
...
Resource dir = /usr/local/elogdemo
Logbook dir = /usr/local/elogdemo/logbooks

and no "Data dir" statements any more. The logbooks "Linux", "Database" 
and "Forum" are then located at

/usr/local/elogdemo/logbooks/Linux
/usr/local/elogdemo/logbooks/Database
/usr/local/elogdemo/logbooks/Forum

respectively. The help, theme and icon files are located at their old 
position ("themes" is automatically added to the "resource dir" as it was 
before).

I have some problem with email notification
for some logbooks I would like to notify only to specific adress
I try
Email All = adress1, adress2

Elog send well at 'adress1' and 'adress2' 
but also to all of other users ?
how to restric these only to 'adress1 and adress2 ?

is it possible to notify according to attribue value like

Attributes = Test1, Test2
Email All = $Test1

or concatenation of  $Test1 + '@mba.be' for example

Thanks

this is a wonderfull tools !
to improve documentation : true example are missing too much 'theorie'
but when I'm finish I'll put true sample on the net 

> I have some problem with email notification
> for some logbooks I would like to notify only to specific adress
> I try
> Email All = adress1, adress2
> 
> Elog send well at 'adress1' and 'adress2' 
> but also to all of other users ?
> how to restric these only to 'adress1 and adress2 ?

Some implementations rely on the fact the email is sent to all users plus a 
few other addresses. What I can do is put in another flag like "Supress 
email to users = 1" which would satisfy both requirements.

> is it possible to notify according to attribue value like
> 
> Attributes = Test1, Test2
> Email All = $Test1
> 
> or concatenation of  $Test1 + '@mba.be' for example

This is not possible right now, but I can put it on the wishlist.

> to improve documentation : true example are missing too much 'theorie'
> but when I'm finish I'll put true sample on the net 

I fully agree, so if someone has nice examples, I'm delighted to put them 
into an "examples" section of the documentation.

- Stefan

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

i can expand and collapse via the links, or if i make sure the url includes it.

> 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

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

I checked your elogd.cfg: The flag is called "Expand default" not "Expand" as 
you had it. With "Expand default = 0" it works fine. Just RTFM...

- Stefan 

> I checked your elogd.cfg: The flag is called "Expand default" not "Expand" as 
> you had it. With "Expand default = 0" it works fine. Just RTFM...

i could probably recite the manual from memory :/ i wouldn't ask if i wasn't confused about something.

i thought the 'default' word was explaining what the default was for the 'expand' flag, not an actual part of the flag. 

unless i missed these in the docs some place:

1) a threaded display but collapsed threads unstead of all replies showing

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

> 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

> This feature has been added in Version 2.2.4 which has been released today. 
> Use the "collase" button.

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

thanks. that was quick :)

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.

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.

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

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

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

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

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

> 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 

that's ok. i just it was driving me nuts there for a while...everything is fine now...

i've tried other web based msg boards, but i keep coming back to elog...

Typing in a text for a new entry results in an error message, whenever
one forgets to fill in mandatory attributes (as it should happen !). However
after using the back button in this case (Using netscape 4.79) I made the
experience, that the text typed in gets lost. Other browsers like Mozilla
or IE do not have this problem. Any idea how this problem can be
avoided for netscape as well ?