The logbook name is in the URL of your browser. In the demo installation, there is a link in the start menu pointing to http://localhost:8080/demo.  If you rename your logbook to something else, you have to change the URL accordingly. The simplest thing is to point it to http://localhost:8080, then you will be presented with a list of available logbooks.

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

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

You could write a script/program that calls the ELOG client with the necessary attributes to submit the entry (see the user's guide).

 To use "Language = french" it is necessary to remove or substitute the accent character ' with something else in eloglang.french and then the Javascript code works again.

Soren

 To overcome this problem it is sufficient to switch language from "Language = french" to "Language = english"

It was a mistake not to include the "global" settings in this bug report.

What probably happens is that something in the French translation (accents ?) disturbs the java scripting.

Soren

Hi,

This little logbook has a problem:

------------------------

Attributes = Author, Category, Type, Subject, Number

Type Number = numeric

Options Category = General{1}
{1} Options Type = Routine

------------------------

(it was of course more complicated to start with).

When creating a new entry and selecting the Category option, there is a problem with the JavaScript which will populate the Type option.

To avoid the problem, I just comment out the line "Type Number ... "

Is this a bug ?

Thanks for your time

Soren

(P.S. Using a reserved name as an attribute name is maybe not optimal, but it does not seem to be the  problem).

For our application we have a lot of very common events we would like to log.  It would be preferable that for certain events/entries we could setup a single button / quick entry method.  Is there away to accomplish this?