Wow Stefan thanks for your kind reply.  This gives me a reason to finally pickup JavaScript, which I am finding both easy and fun, esepcially with all the modules/coding out there already, which makes things easier to do while learning it! I will let you know as I progress on my 'top secret' hack of your masterpiece ;)

Deleting a logbook in the config page (via "Delete this logbook") only removes the logbook defiition from the config file. To really erase all information you have to go to the file system and delete the whole directory belonging to that logbook. You have one subdirectory per year, containing all logobok entries and also attachments, so make sure you do a recursiver directory removal.

Stefan

Stefan,

Thank you that is exactly what I needed to know.

Steve

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

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

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