Thanks for pointing out this bug. I fixed it. New version under CVS.

> Suppose I want to have different password files for all the logbooks, but I want to 
> have a single (admin) user that can log in to all logbooks... Do I need to specify 
> the admin data in all the different password files, or can I use one global 
> password file containing the login name and password for the administrator?

I would not recomment different password files for all logbooks, but a common one and
individual "login user" options on the logbooks, like

[global]
Password file = xxx
Admin user = xxx
...

[A]
Options X = ...
Login user = <user1>,<admin user>

[B]
Option X = ...
Login user = <user2>,<admin user>

This has the advantage that there is only a single password file which is easier to
maintain.

> > I know I can simply copy the settings for logbook B and repeat the settings 
> > for all logbooks C-S. But is there a better way to accomplish this?
> 
> Yes. Put all common settings into the [global] section, only differences into
> the individual logbook sections. Like
> 
> [global]
> Attributes = ....
> Options ....
> 
> [A]
> ; Logbook A is different
> Attributes = ....
> Options = ...
> 
> [B]
> Option X = ...
> 
> [C]
> Option X = ...
> 
> [D]
> Option X = ...
> 
> This way all logbooks "inherit" the settings from the [global] section, only the
> differents are superseeded in the individual sections. Still you need two lines
> for each logbook, but all recurring configuration can be omitted.

Thanks for you quick and correct answer. I have one question left ;-)

Suppose I want to have different password files for all the logbooks, but I want to 
have a single (admin) user that can log in to all logbooks... Do I need to specify 
the admin data in all the different password files, or can I use one global 
password file containing the login name and password for the administrator?

Hi, 

I was just searching your online discussion forum for entries with the 
word 'password' in the subject. I noticed that the 'Full' option in 
the 'full/summary/threaded' line displays the results of all entries in the 
logbook, and not only the entries with the word 'password' in the subject.

I think there is an error in the URL, because when looking for the word 
password in the subject, the URL for the 'Full' option is:
http://midas.psi.ch/elogs/Forum/page1?mode=full&reve&npp=8&Subject=password

If I change the word 'reve' in this URL to 'reversed=1', the results are 
correct

Bartjan Wattel

Your guess is correct. I would like to have that feature in ELOG.

Thanks

> > Is it possible to add one more "text entry" field ?
> 
> I guess you mean the main body text, which is multi-line. No, this is not
> possible right, now, but I added your vote to the wishlist istem "Multi-line
> attributes".

> I know I can simply copy the settings for logbook B and repeat the settings 
> for all logbooks C-S. But is there a better way to accomplish this?

Yes. Put all common settings into the [global] section, only differences into
the individual logbook sections. Like

[global]
Attributes = ....
Options ....

[A]
; Logbook A is different
Attributes = ....
Options = ...

[B]
Option X = ...

[C]
Option X = ...

[D]
Option X = ...

This way all logbooks "inherit" the settings from the [global] section, only the
differents are superseeded in the individual sections. Still you need two lines
for each logbook, but all recurring configuration can be omitted.

> Options Student name  = "Doe, John", "Foo, Bar".

I fixed this bug. Please obtain the newest snapshot (see download page).

Hi,

I want to create a series of logbooks, say logbook A, and logbooks B up to 
including S. I want the logbooks B,C,D,E,...S to have the same options and 
layout, the only difference is: the name of the logbook, and an options or 
extendable options list. All other settings of logbooks B-S are the same, 
while logbook A is a completely different logbook. 

I know I can simply copy the settings for logbook B and repeat the settings 
for all logbooks C-S. But is there a better way to accomplish this?

Thanks, 
Bartjan Wattel