Have set up 3 top level groups, each with their own password file.
Ever since users have to 'login' twice to get to the appropriate elog.
You click on top level group, get to log book and click on the one you want 
and get login/password dialog box, click ok and and you get it again and 
then you finally get into the elog book.

Anything I can check on this behavior?

Hi everybody,

several people have reported of strange problems concering the login/logout
behaviour of elog. After editing elogd.cfg, they could not logout any more
from a logbook, or they were not able to log in. Here comes some
explanation. If you are not interested in the details, skip to the last section.

The login parameters (user name and password) are sored in cookies, which of
course have to be enabled for the elog site in your browser. Each cookie can
contain an optionsl "path=..." statement, which defines for which subtree in
the URL the cookie is valid. If you use a "global" password file (one where
the "password file = ..." statement is in the [global] section of
elogd.cfg), the elogd server stores a cookie with path "/", so it will apply
to the whole site and therefore to all underlying lobooks. If your password
file is defined in an individual logbook section, the elogd server stores a
cookie with path "/<logbook>", so that it applies only to the specific logbook.

The problem arises now if one moves the password file statement from the
global section to the logbook section or back. The browser might still have
old cookies, whic can override any newly set cookie.

Long story short conclusion: If you observe this behaviour, just delete all
cookies in your browser and you should be fine. I added some additional code
to version 2.5.4 which catches a few cases but unfortunately not all.

When I use the <Login user => option to specify what users I want to be 
able to login into the different logbooks it does not seem to work.  Is 
there something else you are supposed to do to restrict what logbooks users 
can log into?

Hello,

I have installed the latest elog version from your web site.

My Admin user and my Login user are set in the elog.cfg to use the Self register process within the first login.

The issue is that I get only one time access to my log on the server (XP) and that is direct after the Selfregister process.

If I log out and login to test my admin and user account I will not get access to my server anymore.

My login page stays without any error message.

1 Notebook  XP Client internet explorer http://host ip:8080/demo------> 2nd Notebook XP Server

I have the deleted the cookies after each try.

I have retested later the accounts several times (login/logout) successful with the internet explorer http://host ip:8080/ on the server itself.

 Please could you help me to identify the issue?

Good Afternoon

Im trying to automatically post an entry using information saved in a text file. I have followed the example in the users guide but i always seem to get a error message saying transmission failed. Lets say for instance I have a user named John and his password is Blue and he wants to log into a logbook called home from a textfile the command im using to log a message from the file is

elog -h localhost -p 8080 -u John Blue -l home -a Author=John -m textfile

I cant seem to figure out why i keep getting this error message. I even tried deleting the password file because i thought it might be an authentication issue.

Can anybody assist me please it would be much appreciated.

Regards

Is there any way to log child events on the detail pages for a fixed number of entries on the main page? For example, I have 15 vehicles to enter on the main page, ID'd by Vehicle Number. Within each of those entries I will be logging ongoing repair service entries with certain attributes.

So how might I design this concept without having repeating vehicle entries on the main page for every service event, and preferably without splitting the information between two linked logbook tabs?