I put this on the wish list.

- Stefan

> small problem : 
> ****************
> Logbook Tabs = 0  in the guest logbook will close the group header
> may be create a parameter to solve ?
> GroupGuest Extranet = ....

What I would recommend in that case is to run two copies of elogd in 
parallel, one for the public and one for the private section. They can even 
run on differnt ports so the firewall can block the private section. If the 
private logbooks are not defined in the public elogd, they don't show up in 
the logbook tabs, so only the publick logbook tabs are seen. Please note 
that two elogd daemons should not have concurrent write access to the same 
logbook, since there is not locking and the logbook could get messed up that 
way. So only one elogd should have write access to any logbook.

- Stefan

propose to put 
[Submit] [Back] [Submit & Notify] button on top/bottom

new parameter 'shell option' 

[test]
...
Attributes = NotifyMode, Param1....Param10, Adresse, Subject, ...
Options NotifyMode = mail, SMS, Fax, printer...

; this command will invoque a shell command  
; example       
ShellCommand = <my shell command> parameters ...

like in WINDOWS 2000
ShellCommand = START.EXE notify.bat $NotifyMode $Param1, $Param2, $Param3
; in this case no necessity to modify the C source
; in windows I suggest the start.exe with a exit command
; so no necessary to wait the return code from the shell

> From Version 2.2.5 on, the configuration file entries
> 
> User = ...
> Group = ...
> 
> have been changed to
> 
> Usr = ...
> Grp = ...
> 
> in order not to conflict with the new "Group = ..." option which is used by 
> hierarchical logbooks.

not really a bug
works very fine just remarks : with this example
Group Phone & Adress = Whois, Qui_est_Qui
Group Extranet = Aide, Promos_Clients, Qui_est_Qui, Joke

[whois] is a intranet section for us : [qui_est_qui] is public
I add   'copy to = Qui_est_qui' 
so extranet or public can acces to limited information
just remove the attributes and guest user can see only limited info
see example below

small problem : 
****************
Logbook Tabs = 0  in the guest logbook will close the group header
may be create a parameter to solve ?
GroupGuest Extranet = ....

;--------------------  intranet info----------------
[Whois]
Comment = MBA & his Partner all your personal info must be here
Subdir = whoiswho
Menu commands = Back, New, Edit, Find, Help, Copy to
Attributes = Partner, AsTo, YourName, SurName, email1, email2, hotmail,Yahoo, 
GSMmail, Nickname, phone, fax, portable , home , adress, Remarks, birthday, 
QuadroUser, Function, Division
MOptions Partner = Mba, MbaCZ, BusinessCom, Edipax, Ibi, Other
Required Attributes = Parner, CodeName, YourName, email1, phone, birthday
Preset GSMmail = ???@proximus.be
Preset portable = 00 32
Copy to = Qui_est_Qui

Quick filter = Partner, Date, AsTo

;------------------------------------
[Qui_est_Qui]
Comment = MBA et ses collaborateurs à votre service 
Subdir = logbooks/whoiswho/public
Attributes = Partner, YourName, SurName, phone, fax ,portable ,email1 , 
hotmail, GSMmail, Nickname,  Remarks,Function, Division
MOptions Partner = Mba
Date format = %d/%m/%y
Quick filter = Date

;--------------------pas d'acces au autre menu no acces to main menu
Logbook Tabs = 0
Guest menu commands = Find
Guest find menu commands = Find
;-------------- rectriction on edit if not put  1  
Restrict edit = 1
Display mode = full
Help URL = http://www.mba.be







 

> Was wondering if there were any tweaks/suggestions for improving the 
> logbooks responsiviness.  Our logbook was started 31 July 01.  Since that 
> time we have went from 1 logbook to 4 logbooks.  Logbook 1 having 2651 
> entries, logbook 2 having 300 entries, and the last 2 are new logbooks, so 
> only a few entries.

Another trick for large logbooks is to divide them into a logbook with 
recent entries and one with old entries (archive), like I did now in this 
forum. One can enable the "copy to" command for the administrator, who then 
can copy regularly old entries to the archive, keeping the recent logkook 
reasonable small with a good responsiviness. If one wants to search then the 
old messages, one can still go to the archive, but then the search command 
takes longer.

> > may be add a parameter
> > 
> > Restrict Search all logboog = 1 or 0
> > if 1 the switch will not appear 
> 
> The flag "Search all logbooks" is already there! (I forgot about it!). So 
> just set it to "0" and you should be fine.
> 
> - Stefan

I do and it work fine

> Was wondering if there were any tweaks/suggestions for improving the 
> logbooks responsiviness.  Our logbook was started 31 July 01.  Since that 
> time we have went from 1 logbook to 4 logbooks.  Logbook 1 having 2651 
> entries, logbook 2 having 300 entries, and the last 2 are new logbooks, so 
> only a few entries.

In Version 2.2.5, the responsiviness to large (>1000 entries) logbooks has 
been improved dramatically. If no filtering is applied, a page from the 
logbook listing should be displayed with a response time independent of the 
logbook size (I tried 8000 entries). Only when a filter or sort option is 
applied, all entries have to be searched which takes ~5sec for 8000 entries 
on a 1.2 GHz Windows XP Laptop, which is the same speed as before.

From Version 2.2.5 on, the configuration file entries

User = ...
Group = ...

have been changed to

Usr = ...
Grp = ...

in order not to conflict with the new "Group = ..." option which is used by 
hierarchical logbooks.