Hi,

Is it possible to remove the "demo" logbook?

If I rename the section in elogd.cfg , it complains:

Error: logbook "demo" not defined in elog.conf Please use your browser's back button to go back

But there are other logbooks it can show instead. Is the "demo" logbook hardcoded in elogd?

/tony

 I now upgraded to ver. 2.7.8, but I still cannot remove or disable the demo logbook.

 Thanks Stefan, I managed to get it to work now.

Stefan, 
We are interested in using your ELOG (which we consider to be a wonderful 
application) even more. We would like to make a few adaptations in your 
source code, above all to add some functionality that we are missing.

I was wondering if there is a way we could coordinate the development 
together. For instance, would it be of your interest to receive the code 
adaptations we do and implement it in your future releases? 

To be more specific, for the moment we are really interested in 
implementing the SHELL script execution on the server (I noticed it is in 
your wishlist).

Best regards,

Tomas Rudolf
Micro Belgium Application

> > We are interested in using your ELOG (which we consider to be a wonderful 
> > application) even more. We would like to make a few adaptations in your 
> > source code, above all to add some functionality that we are missing.
> > 
> > I was wondering if there is a way we could coordinate the development 
> > together. For instance, would it be of your interest to receive the code 
> > adaptations we do and implement it in your future releases? 
> 
> Sure, I'm very interested in those and ready to merge it into the main 
> development tree.
> 
> - Stefan

Thanx for your quick answer.
I'll keep you updated as we move ahead with the development.
Tomas

Hi Stefan,

I have a question concerning the Email notification in ELOG.

I have been testing various combinations of the parameters you describe in 
your documentation :

Email <attribute> <value> = <list> 
Use Email Subject = <string> 
Use Email From = <string> 
Omit Email To = 0|1 
Suppress Email to users = 0|1 

And I have encountered a problem using the Email <attribute> <value> = 
<list>. While this works fine for me when the <attribute> is of a type 
textfield, Options or ROptions, I don't seem to be able to have it working 
for the MOptions <attribute> = <list>.

The aim is to have an email notification sent only to selected people 
instead of everybody. I was hoping that this would work :

[MyLogBook]
MOptions Message_To = NB,LW,EC,MD,CD,TV,AH,TR,JS
...
...
Suppress Email to users = 1
Email Message_To TR = tomas@mba.be
Email Message_To EC = etienne@mba.be
...
...

Of course, the tricky part is that it is "multiple choice" so any 
combination of recipients is possible.

Am I missing something? 
Thanx for any ideas how to solve this,

Tomas

Hi,
We prepared a customized theme to use with ELOG. It's called for example 
my_theme and is situated in the THEMES directory (together with the DEFAULT 
theme).

I defined the my_theme the global theme for ELOG:

[global]
Theme = my_theme

And it works fine for all the logbook in ELOG. However. The login screen 
and the main menu screen (the one with list of logbooks and # of entries) 
still takes the DEFAULT theme. 

If I change the my_theme name to default then everything works correctly 
(logon + main menu + all logbooks have the desired look).

Is the DEFAULT theme somehow hardcoded for the login screen and the main 
menu ?

Thanx for your answer

Tomas Rudolf

Hi,

I was wondering if anyone had a solution for my problem.
We are trying to run several books on one server. The books are grouped 
such as follows :

Group Users1 = Book1, Book2, Book3
Group Users2 = Book4, Book5, Book6
Group Users3 = Book7, Book8, Book9

We would like to give access to selected users to only their Group. So that 
for instance Users1 cannot access the books of group Users3. I was 
wondering if there is any notion of "User profile" or security per logbook 
Group implemented?

What we do for now is that we have 3 different PASSELOG files and for each 
Book we need to specify which PASSELOG should be used for authentication. 
This works fine except that we prefer that users do not see the other 
logbooks listed in the main menu nor the other "inaccessible" logbook tabs 
in the logbook view. Is there a way to hide these for them (but only for 
them)?

Tomas