Hi,

Is there any solution to obtain an non-clickable column ?
For example here : http://midas.psi.ch/elogs/Config+Examples/ what should 
I do to obtain the data of the Category column non clickable?
I don't have find a solution in the Syntax of elogd.cfg  
(http://midas.psi.ch/elog/config.html)

Thanks a lot

Stefan,

I finally got it installed on a server at work (only took a year to work through all the red tape). I have seven logbooks up and running and only one is giving me trouble. It is an On-Line Help book where I wanted to store documents that could be referenced by our staff. It is the simplest of my logbooks (see config file below) but when I hit the "Submit" button it crashes the program. I can not see the error myself but the server guys are telling me that that we are getting an "Internal error, no valid header!" error. The only other thing that I can think to mention is that the entry that is crashing the program is a 60k Microsoft word table that I had cut and pasted into elog.

Thank you, Mike

[OnlineHelps]
Write Password = SWNlQ3ViZQ==
;DISPLAY
Theme = default
Display mode = threaded
Mode Commands = 0

Thread display = --------------  $Title  --------------
Comment = On-Line Helps

Attributes = Title

Required Attributes = Title
Page Title = ELOG - $subject
Reverse sort = 0
 

Hello Stefan,
Did you have a release Date for Elog V2.6.0 ?
Thanks in Advance.

Hi.

I'd like to use elog as a tool ta keep my notes, links, passwords... It's installed on my personal computer at home (Debian Squeeze), behind a Ip-Cop firewall, so I guess it won't be accessible from anywhere outside. But I'd like to protect the log with a password anyway. BTW, I had some hard time figuring out how to configure the different files for french (there was a problem with UTF8 mixing up with Latin1... I recoded the language file to UTF8 to solve it).

I followed the procedure described here, but I have a problem with second stage :

• I set Password file = elog.pwd in the elog.conf file (it's not elog.cfg on Debian...)
• I restart the daemon
• I try to login to http://localhost:8080/, and receive the message : "error opening the file elog.pwd"

I get this message even after :

1. adding my user account to the elog group
2. launching Epiphany as root

So I guess I have to create (how ???) the file elog.pwd, which, if I understand correctly, can be empty at the start... But where do I save it ?

Thank you for any help, and sorry if I'm a little confused. I had hard time figuring out where to find everything.

\bye

Running elog-3.1.4-3 Can't add users through the web interface. Clicking add user and writing all the fields in with something doesn't add a user into the PWD file of that logbook. Running a tail -f on the password file shows elog writes the user info with the hashed password 3 times and then deletes the information about 20 seconds later. Has anyone else had a similar issue? This is running on RHEL8.3

Hello,

I'm new to elog. I've installed it under Slackware 11. Everything worked smoothly until I wanted to establish access control. I followed the steps described under Access control heading in Syntax of elog.cfg chapter. I specified a new password file name and the following steps with no problem. After having created a new user I stopped elogd  and added  Admin user to config file. And here is my problem - each time I want to login to elog, I get "Invalid user name or password!" message. The meaning of it is obvious. So I have repeated all the steps several times. Of course I paid attention to enter user name and password correctly but I can't get rid of this message. For sure I making something wrong, but what it is ?

Here is part of my elogd.cfg:

[global]
Port=8080
Logfile = elogd.log
Logging level = 3
Password file = passwd
Self register = 1
Admin user = eloga
charset = utf-8
 

Here is what happens after elog restart:

elogd 2.8.0 built Oct 22 2010, 11:04:31 revision 2313
Falling back to default group "elog"
Falling back to default user "elog"
Falling back to default group "elog"
Falling back to default user "elog"
ImageMagick detected
Indexing logbooks ... Converting password file for logbook "Demo" to new encoding ... ok
done
Server listening on port 8080 ...

Here is the password file :

<?xml version="1.0" encoding="ISO-8859-1"?>
<!-- created by MXML on Wed Nov 24 13:13:43 2010 -->
<list>
  <user>
    <name>eloga</name>
    <password encoding="SHA256">vnpfrWa8wmxFsLFjlY/poXdz3wh6RLt9BT.D1O52Xl9</password>
    <full_name>Mariusz Stakowski</full_name>
    <last_logout>0</last_logout>
    <last_activity>Wed Nov 24 13:13:43 2010</last_activity>
    <email>Mariusz.Stakowski@asseco.pl</email>
    <email_notify/>
  </user>
</list>

And here is what I found in elogd.log file:

24-Nov-2010 13:50:06 [] Server listening on port 8080 ...
24-Nov-2010 13:50:53 [eloga@xx.xx.xx.xx] {Demo} LOGIN user "eloga" (attempt)

Could somebody help me please ?

Best regards

Mariusz Stakowski

Version 2.5.0 of ELOG has been released yesterday. The main new feature is 
the automatic mirroring of logbooks between different elog servers. 

This is useful if one wants to synchronize logbooks between a desktop PC 
and a laptop, for example. During synchronization, new or modified entries 
on both sides are merged intelligently. Another application is if several 
companies or institutes want to keep a ELOG database locally, but have the 
databases synchronized periodically with each other. Periodic mirroring 
can be set up with a built in cron-like facility. 

Although the synchronization has been tested extensively, I still consider 
this part in beta state. Before using it, one should make a backup of 
existing logbooks. The flag "Mirror simulate" can be used to test the 
mirroring without actually overwriting or deleting anything. If problems 
arise with mirroring, they should be reported to the author.

Localization files have been updated, so if anybody volunteers to update 
or make a new translation, please contact the author.

Is it possible to include an option in the next release to have the Options list reference a text file of attributes rather than explicity listing the attributes in the Config file directly?

This would make it much easier to maintain a particular list that is referenced in several log books.