Not sure if this is a bug or not; if it is not, kindly reclassify the category.

Following is a small example of what I will dub a 3-level, conditional logbook:

This example is hardly complete, but it is sufficient to demonstrate the issue I am running into.  This works until I select from the 2nd level (manufacturer); it won't display the dropdown for the model (I think my show attribute edit is supposed to display that).  Is there a restriction on how many levels of conditional I can have?  If there is, it would be disappointing because I am trying to do something similar to this example.

I hope there is something very simple I can do to correct this, or perhaps a completely different approach that accomplishes the same thing.  I'd like to stick with the multi-level selection process as I have done here.

I am running elog 3.1.5 on Devuan Chimaera (approx. Debian Bullseye, sans systemd) in a Virtualbox VM.

Please excuse my double-posting. But my first entry was not displayed on the forum and I haven't received feedback yet. I think this is because I responded to an entry that was still in draft mode, whereas my entry was a "normal" entry. My initial entry has the Message ID: 69870 and was in reply to: 68348

***

Dear Andreas and Stefan,

First of all thank you for the template for a checklist. I have created my own version of it and the HTML looks fine. For comparison, I temporarily also included the shiftcheck template provided by Stefan to my ELOG.

However, I have the same problem as JD. After submitting the data in shiftcheck, I receive the error "Cannot open file passwords.pwd: No such file or directory" and the URL is http://localhost:8085/ShiftCheck/?cmd=Submit&suppress=1&unm=&upwd=&Author=Marcel+Zauner-Wieczorek&edit_id=&D=1&M=4&Shift=Morning&a4=&h2=&a5=&a6=&c1=&c2=&c3=&c4=&c5=&bb1=&cr1=&cr9=&cr18=&cr20=&cr21=&cr23=&cr24="

I have tried to include the path of the password file in the cfg file (using "", <>, <"">, and only the path name), but then the elogd.exe won't start at all unless I change it back to the simple "Password file = passwords.pwd".

Here is an excerpt of my config file:

    ****

    [global]
    port = 8085
     

    Password file = passwords.pwd
    Login expiration = 1
    Admin user = Marcel
    Login user = Marcel

    Self register = 1

    Group General = ShiftCheck
    Group Gas phase instruments = Checklist_MARGA

    Restrict edit time = 1
    Admin restrict edit time = 0
    Autosave = 60

    [ShiftCheck]
    Comment = Shift Check List

    Attributes = Author, D, M, Y, Shift, a1, a2, a3, a4, a5, h1, h2, h3, h4, h5, c1, c2, c3, c4, c5, c6, c7, bb1, cr1, cr2, cr3, cr4, cr5, cr6, cr7, cr8, cr9, cr10, cr11, cr12, cr13, cr14, cr15, cr16, cr17, cr18, cr19, cr20, cr21, cr22, cr23, cr24, cr25, cr26, sw1, sw2, sw3, sw4, sw5
    Quick filter = Shift, Author
    Options Shift = Morning, Evening, Night

    Enable attachments = 0
    Show text = 0
    Custom new form = shiftcheck.html
    Custom edit form = shiftcheck.html
    Custom display form = shiftcheck.html
    List after submit = 1

    [Checklist_MARGA]
    Comment = Check List for MARGA

    Date Format = %d.%m.%Y
    Time Format = %d.%m.%Y %H:%M:%S

    Reverse sort = 1

    Attributes = Author, D, M, Y, On, DP2h, T_SJAC, T_heat, EC_An, EC_Cat, IonBal, IS_Cat_Ae, IS_An_Ae, IS_Cat_Ga, IS_An_Ga, P1, P2, Err, Com

    Quick filter = Author

    Enable attachments = 0
    Show text = 0
    Custom new form = checklist_MARGA.html
    Custom edit form = checklist_MARGA.html
    Custom display form = checklist_MARGA.html
    List after submit = 1
    ***

I am actually confused about the passwords.pwd file. I have successfully created several users with passwords and I can use their credentials to log into the different labbooks. However, none of these users (let along their (encrypted) passwords) turn up in the passwords.pwd file. I don't know where ELOG saves these information, but it's apparently not the passwords.pwd file that is defined in the cfg file and that I have access to.

I hope that someone can help me with this issue. Otherwise, I would omit the password function within ELOG and find an external solution for a password protection.

Cheers,

Marcel

> Hello,
>     If you delete a message from the middle of a logbook that contains a 
> bunch of messages, the message numbers do not get updated properly.  For 
> instance, if you have 20 messages in the logbook, and delete number 15, 
> entry numbers 16 through 20 all do not get subtracted by one; their numbers 
> stay the same with #15 just missing in the middle.  
> 
> Mo

That's how it's supposed to be. Once a unique message ID is attached to a 
message, it stays there forever. Think of links to message like

http://midas.psi.ch/elogdemo/Forum/68

If you have such a link in a message or as a bookmark in your browser, and 
the ID gets changed from 68 to 67, then your link would be off.

> Anyone seen similar problems? 
Probably not if you read the config file, 'cause I didn't. Shame on me...

But what this shows (Stefan: correct me if I'm wrong) is that if you set 
the port number in the [global] section of the config file, the command-line
option '-p' is ignored. FYI...

Joeri

Version 2.0.5 of elog has been released today. Among various bugfixes, the 
display speed for threaded lists has been improved significantly. Display 
all messages of this forum and press the reload button to see the 
difference.

> Just compiled elog-2.0.5 under Solaris 8 and 9  without any warnings/errors
> but the elogd binary just core dumps:
> 
> # /opt/ELOG/bin/elogd -c /opt/ELOG/elogd.cfg 
> Indexing logbook "demo"...
> Bus Error (core dumped)
> 
> .. tracing elogd shows:
> 
> [ lines snipped ]
> 2964:   brk(0x005B8A68)                                 = 0
> 2964:   ioctl(1, TCGETA, 0xFFBEE6BC)                    = 0
> Indexing logbook "demo"...
> 2964:   write(1, " I n d e x i n g   l o g".., 27)      = 27
> 2964:       Incurred fault #5, FLTACCESS  %pc = 0x000164C0
> 2964:         siginfo: SIGBUS BUS_ADRALN addr=0x2F757372
> 2964:       Received signal #10, SIGBUS [default]
> 2964:         siginfo: SIGBUS BUS_ADRALN addr=0x2F757372
> 2964:           *** process killed ***
> #
> 
> ... any glue ?

Hmmm - stupid me used a broken patch  used to get rid of alphasort under 2.0.4
this entry and it's predecessor should be DELETED - sorry for the confusion :-(

Hi,

I added many features to ELOG recently, but before making a new release, I 
would like some beta testing. In addition to the current modes of 
operation, a logbook can be configured to require a user to be logged in to 
submit new messages. If not logged it, one can only read messages. To 
obtain a new account, one can do a self-registering. In this process, one 
can also enter the email address which is then filled in automatically on 
new logbook entries.

So please go to the forum logbook, create a new account for yourself and 
try things out. If there is any problem, please let me know.

Many thanks in advance, Stefan Ritt.

Just since some people asked for: Here is the elogd.cfg for this demo 
logbooks:

========= cut here ===================

[global]
logbook tabs = 1
SMTP host = mailsend.psi.ch
URL = http://midas.psi.ch/elogdemo/
user = midas
group = midas

[Linux]
Theme = default
Comment = General linux Tips & Tricks
Data dir = /usr/local/elogdemo/logbooks/Linux
Attributes = Author, Type, Icon, Category, Subject
Options Type = Routine, Software Installation, Problem Fixed, 
Configuration, Tips & Tricks, Info, Other
IOptions Icon = icon1.gif, icon3.gif, icon4.gif, icon5.gif, icon6.gif, 
icon7.gif, icon8.gif, icon12.gif, icon13.gif, icon14.gif
Options Category = General, Hardware, Software, Network, Applications, 
Shell, Account, Packages, Daemons, Other
Required Attributes = Author
Subst Author = $author
Summary on default = 1
Summary lines = 0
Email all = stefan.ritt@psi.ch
Email message body = 1

[Database]
Theme = default
Comment = Demo of database-like elog
Data dir = /usr/local/elogdemo/logbooks/database
Attributes = Type, Operating system, Location, Status, Comment
Required Attributes = Type, Operating system, Location, Status
Options Type = PC, Router, Bridge
Options Operating system = Linux, Windows NT, Windows 2000, Windows XP, 
Windows ME, Embedded
Options Location = Building1, Building2, Building3
Options Status = working, defect, in repair
Show text = 0
Start page = ?cmd=Search&mode=summary
Display search = #, Type, Location, Status
Summary lines = 0
Find menu commands = New, Find, Last
Menu commands = Back, New, Edit, Delete, Find, Config, Help
Number Attachments = 0
Suppress default = 2
Entries per page = 10

[Forum]
; general options
Password file = /usr/local/elogdemo/logbooks/forum/passwd
Admin user = stefan
Self register = 2
Theme = default
Comment = Discussion forum about ELOG
Data dir = /usr/local/elogdemo/logbooks/forum
Display mode = threaded
Start page = ?cmd=Search&mode=threaded
Menu commands = Back, New, Edit, Reply, Find, Last day, Last 10, Admin, 
Config, Logout, Help
Find menu commands = New, Find, Last x, Admin, Config, Logout, Help
Guest menu commands = Back, Find, Login, Help
Guest find menu commands = Find, Login, Help
Number Attachments = 1
Message comment = <img src=icons/icon6.gif> Please enter only serious 
messages here, for testing use the <b>Linux</b> Logbook:
Filtered browsing = 0
Entries per page = 8
Reverse sort = 1
Restrict edit = 1

; Attributes
Attributes = Icon, Author, Author Email, Category, Subject
IOptions Icon = icon1.gif, icon2.gif, icon3.gif, icon4.gif, icon5.gif, 
Options Category = Info, Bug report, Bug fix, Question, Request, Comment, 
Other
icon6.gif, icon7.gif, icon8.gif, icon12.gif, icon13.gif, icon14.gif
Required Attributes = Author, Author Email, Subject, Icon
Subst on reply subject = Re: $subject
Thread display = $subject, posted by $author on $Entry date
Thread icon = Icon
Remove on reply = Author, Author Email
Date format = %B %d, %Y
Preset Author = $long_name
Preset Author Email = $user_email
Locked Attributes = Author

; Email notification
Email message body = 1
Display Email recipients = 0