[CLOSED] Re: show attributes directive does not work? -- It does, if you use show attributes edit, posted by Harry Martin on Sat Aug 16 14:31:49 2025
|
Well, it DOES work.... but only if you use the "Show Attributes Edit" directive. "Show Attributes" is only for the single entry pages, whereas "Show Attributes Edit" is for the "entry pages."
I should have read the docs more carefully, sorry. But isn't this a bit inconsistent with the way other directives work? Usually one uses "<Directive>" for new entries, "<Directive Edit>" for editing existing entries, and "<Directive Reply>" for replies. So I am guessing that "Show Attributes Edit" will be used for new and edit?
Harry Martin wrote: |
Follows a very simple logbook definition:
[simple]
Comment = test show attributes directive
Attributes = a, b, c
Show Attributes = a
(Assume that all attributes are used farther down. This is for illustration only.)
To see what I see when I run this tiny elogd.cfg, see attachment.
"Show attributes" does not seem to be working because all of the attributes are shown, not just those specified in the directive. Or do I misunderstand/forget something?
|
|
[CLOSED] Re: 3-level conditional not working, posted by Harry Martin on Sat Aug 16 22:19:03 2025
|
Closed. This "problem" was due to the same lack of document eyesight as https://elog.psi.ch/elogs/Forum/69889. Sorry for all the noise. New eyeglasses are forthcoming...
Harry Martin wrote: |
Tried a variant, this time for NEW entries (not EDIT), which I meant to do to begin with; sorry if that was confusing.
[cond_test]
attributes = region, manufacturer, model
options region = american{us}, japanese{jp}, european{eu}
show attributes = region
{us} options manufacturer = ford, chrysler, gm
{jp} options manufacturer = toyota{toy}, nissan{nis}, mitsubishi{mit}
{eu} options manufacturer = audi, mercedes, bmw, volvo, fiat
{us} show attributes = region, manufacturer
{jp} show attributes = region, manufacturer
{eu} show attributes = region, manufacturer
{toy} options model = corolla, prius, miata
{nis} options model = sentra, murano
{mit} options model = starion, outlander, mirage
{toy,nis,mit} show attributes = region, manufacturer, model
I'm not sure if my multi-character conditional names are allowed or not, but they do seem to work... somewhat. Note that I even tried a couple different ways of specifying which attributes to show (single versus multiple OR conditionals). The problem now is that all of the attributes are always shown, seeming to ignore the conditionals entirely.
Harry Martin wrote: |
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:
[cond_test]
attributes = region, manufacturer, model
show attributes edit = region
options region = american{1}, japanese{2}, european{3}
{1} options manufacturer = ford, chrysler, gm
{2} options manufacturer = toyota{4}, nissan{5}, mitsubishi{6}
{3} options manufacturer = audi, mercedes, bmw, volvo, fiat
{1,2,3} show attributes edit = region, manufacturer
{4} options model = corolla, prius, miata
{5} options model = sentra, murano
{6} options model = starion, outlander, mirage
{4,5,6} show attributes edit = region, manufacturer, model
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.
|
|
|
Re: collapse does not seem to work as expected, posted by Harry Martin on Mon Aug 18 03:14:51 2025
|
I am not sure if either "Sort Attributes" or the Quick Filter are the main issue, though they could be. I have implemented a work-around for now, but it really would be nice if this worked as expected. Or perhaps someone can provide an example of a logbook with working "collapse" functionality. Thank you for this nifty program; everything else aside, this tool helps keep my work in order.
Harry Martin wrote: |
I also notice that collapse does not work properly if I have anything selected in the quick filter.
Harry Martin wrote: |
Figured it out: I had "Sort Attributes" set on the logbooks that were failing to collapse correctly. At least, I think that is the distinction.
I think I can live with "Sort Attributes" disabled; I don't recall why I chose to set the "Sort Attributes" in the first place. But I still think this is an issue.
Harry Martin wrote: |
I should add that this does not happen in every logbook. I'm looking into what the distinction is that causes this in certain logbooks and not in others.
Harry Martin wrote: |
When I click on "collapse," even several times, I still see all the replies in each thread rather than just one entry representing each entire thread.
I am running elogd 3.1.5 on devuan chimaera (bullseye) which I built from source. I had the same results with 3.1.4 and 3.1.3.
I tried to disable the quick filter just to see if that impacted the behavior, but it didn't.
If there are any other tests I can use to narrow the problem, please suggest them. Without a working collapse feature, I cannot get a quick birdseye view of, say, all open threads.
|
|
|
|
|
5.5.4 cannot decode AUTH parameter, posted by harish amin on Fri Nov 21 12:38:07 2014
|
Dear Team,
I am having a log book and would like to activate the email notification. I have made the changes as per the guidelines but I am getting the error message while submitting the entry - Error sending Email via "smtp.omantel.net.om": 5.5.4 cannot decode AUTH parameter
The details are as below : (Please note I have replaced the password with the * marks)
21-Nov-2014 16:58:28 [harish@127.0.0.1] {SCREENING VISIT} NEW entry #0
21-Nov-2014 16:58:28 [harish@127.0.0.1] {SCREENING VISIT} Email from <harish.amin@holiday.co.om> to harish.amin@holiday.co.om, SMTP host smtp.omantel.net.om
21-Nov-2014 16:58:28 [harish@127.0.0.1] {SCREENING VISIT} 220 fmgw1.omantel.net.om ESMTP Smtpd; Fri, 21 Nov 2014 15:32:52 +0400
21-Nov-2014 16:58:28 [harish@127.0.0.1] {SCREENING VISIT}
21-Nov-2014 16:58:28 [harish@127.0.0.1] {SCREENING VISIT} EHLO localhost
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-fmgw1.omantel.net.om Hello [188.66.222.72], pleased to meet you
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-ENHANCEDSTATUSCODES
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-PIPELINING
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-8BITMIME
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-SIZE 32235520
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-DSN
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-AUTH LOGIN PLAIN
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-STARTTLS
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-DELIVERBY
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250 HELP
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} AUTH LOGIN
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} Username
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} harish.amin@holiday.co.om
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} Password
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} ******
21-Nov-2014 16:58:30 [harish@127.0.0.1] {SCREENING VISIT} 501 5.5.4 cannot decode AUTH parameter ******
Please help me to resolve this issue.
Thank you
Harish Amin |
Re: 5.5.4 cannot decode AUTH parameter, posted by harish amin on Fri Nov 21 17:00:09 2014
|
Stefan Ritt wrote: |
harish amin wrote: |
Dear Team,
I am having a log book and would like to activate the email notification. I have made the changes as per the guidelines but I am getting the error message while submitting the entry - Error sending Email via "smtp.omantel.net.om": 5.5.4 cannot decode AUTH parameter
The details are as below : (Please note I have replaced the password with the * marks)
21-Nov-2014 16:58:28 [harish@127.0.0.1] {SCREENING VISIT} NEW entry #0
21-Nov-2014 16:58:28 [harish@127.0.0.1] {SCREENING VISIT} Email from <harish.amin@holiday.co.om> to harish.amin@holiday.co.om, SMTP host smtp.omantel.net.om
21-Nov-2014 16:58:28 [harish@127.0.0.1] {SCREENING VISIT} 220 fmgw1.omantel.net.om ESMTP Smtpd; Fri, 21 Nov 2014 15:32:52 +0400
21-Nov-2014 16:58:28 [harish@127.0.0.1] {SCREENING VISIT}
21-Nov-2014 16:58:28 [harish@127.0.0.1] {SCREENING VISIT} EHLO localhost
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-fmgw1.omantel.net.om Hello [188.66.222.72], pleased to meet you
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-ENHANCEDSTATUSCODES
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-PIPELINING
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-8BITMIME
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-SIZE 32235520
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-DSN
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-AUTH LOGIN PLAIN
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-STARTTLS
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-DELIVERBY
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250 HELP
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} AUTH LOGIN
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} Username
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} harish.amin@holiday.co.om
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} Password
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} ******
21-Nov-2014 16:58:30 [harish@127.0.0.1] {SCREENING VISIT} 501 5.5.4 cannot decode AUTH parameter ******
Please help me to resolve this issue.
Thank you
Harish Amin
|
For the login to your email sever, the password is encoded in base64 form (actually not really secure). Somehow your server does not support this. Unfortunately I cannot test this without access to your server. But you can try yourself by doing a telnet to your mail server like:
$ telnet <server.domanin> 25
...
$ AUTH PLAIN
With the "plain" method, you should be able to enter your password in plain text (not base64 encoded), and see if that works. If you are successful, I can add this option to elog.
Best,
Stefan
|
Dear Stefan
Thank you for your reply. Please check is my entry correct?
port = 8080
Admin user = harish
url = http://localhost:8080
;Find Menu commands = Logout, New, Find, Select, Config, Last day, Last 10, Help
;Guest Menu commands = Login, Back, Find, Last day, Last 10, Help, Logout
;Guest Find Menu commands = Login, Back, Find, Last day, Last 10, Help
SMTP host = smtp.omantel.net.om
SMTP port = 25
$telnet smtp.omantel.net.om 25
$AUTH PLAIN
SMTP username = harish.amin@holiday.co.om
SMTP Password = ********
Subst Email = $user_email
Logfile = errorh.log
Email Encoding = 4
Entries per page = 50
;Logfile = harish.log
;Logging level = 2 |
Re: 5.5.4 cannot decode AUTH parameter, posted by harish amin on Sat Nov 22 14:50:35 2014
|
harish amin wrote: |
Stefan Ritt wrote: |
harish amin wrote: |
Dear Team,
I am having a log book and would like to activate the email notification. I have made the changes as per the guidelines but I am getting the error message while submitting the entry - Error sending Email via "smtp.omantel.net.om": 5.5.4 cannot decode AUTH parameter
The details are as below : (Please note I have replaced the password with the * marks)
21-Nov-2014 16:58:28 [harish@127.0.0.1] {SCREENING VISIT} NEW entry #0
21-Nov-2014 16:58:28 [harish@127.0.0.1] {SCREENING VISIT} Email from <harish.amin@holiday.co.om> to harish.amin@holiday.co.om, SMTP host smtp.omantel.net.om
21-Nov-2014 16:58:28 [harish@127.0.0.1] {SCREENING VISIT} 220 fmgw1.omantel.net.om ESMTP Smtpd; Fri, 21 Nov 2014 15:32:52 +0400
21-Nov-2014 16:58:28 [harish@127.0.0.1] {SCREENING VISIT}
21-Nov-2014 16:58:28 [harish@127.0.0.1] {SCREENING VISIT} EHLO localhost
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-fmgw1.omantel.net.om Hello [188.66.222.72], pleased to meet you
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-ENHANCEDSTATUSCODES
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-PIPELINING
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-8BITMIME
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-SIZE 32235520
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-DSN
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-AUTH LOGIN PLAIN
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-STARTTLS
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-DELIVERBY
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250 HELP
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} AUTH LOGIN
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} Username
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} harish.amin@holiday.co.om
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} Password
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} ******
21-Nov-2014 16:58:30 [harish@127.0.0.1] {SCREENING VISIT} 501 5.5.4 cannot decode AUTH parameter ******
Please help me to resolve this issue.
Thank you
Harish Amin
|
For the login to your email sever, the password is encoded in base64 form (actually not really secure). Somehow your server does not support this. Unfortunately I cannot test this without access to your server. But you can try yourself by doing a telnet to your mail server like:
$ telnet <server.domanin> 25
...
$ AUTH PLAIN
With the "plain" method, you should be able to enter your password in plain text (not base64 encoded), and see if that works. If you are successful, I can add this option to elog.
Best,
Stefan
|
Dear Stefan
Thank you for your reply. Please check is my entry correct?
port = 8080
Admin user = harish
url = http://localhost:8080
;Find Menu commands = Logout, New, Find, Select, Config, Last day, Last 10, Help
;Guest Menu commands = Login, Back, Find, Last day, Last 10, Help, Logout
;Guest Find Menu commands = Login, Back, Find, Last day, Last 10, Help
SMTP host = smtp.omantel.net.om
SMTP port = 25
$telnet smtp.omantel.net.om 25
$AUTH PLAIN
SMTP username = harish.amin@holiday.co.om
SMTP Password = ********
Subst Email = $user_email
Logfile = errorh.log
Email Encoding = 4
Entries per page = 50
;Logfile = harish.log
;Logging level = 2
|
Dear Stefen,
Please help me & reply on my request. Is my global config correct? |
Error report while submitting the entry, posted by harish amin on Mon Nov 24 18:29:34 2014 
|
Dear Stefan,
I am having a log book with the 5 logbooks. All other books are working fine except only one, every time while submitting the entry I am getting a error message.
I have attached the screen shot along with the error log file.
Please help me in solving this bug.
Regards
Harish Amin |
Re: Error report while submitting the entry, posted by harish amin on Wed Nov 26 12:49:12 2014
|
Stefan Ritt wrote: |
harish amin wrote: |
Dear Stefan,
I am having a log book with the 5 logbooks. All other books are working fine except only one, every time while submitting the entry I am getting a error message.
I have attached the screen shot along with the error log file.
Please help me in solving this bug.
Regards
Harish Amin
|
It's hard to guess from the information you sent what is wrong. The program just crashes, after the email notification has been sent successfully. Can you check if the one logbook which is not working is using some path for the logbook directory which it cannot write to due to access limitations? Just a guess.
-Stefan
|
Dear Stefen,
I am attaching the config file details of the the logbook which crashes. Please check and reply.
Admin user = harish
password File = eng.pwd
;self register = 1
;Login expiration = 0.18
Theme = default
Comment = Lifesciences Pvt.Ltd.
Menu commands = List, New, Reply, Find, Logout, Help
Attributes = SUBJECT INITIALS, SUBJECT ID, SUBJECT DATE, ASSESSMENT OF VITALS:(To be transcribed from Source Note)Time, Pulse Rate(Per minute), Blood Pressure(mm Hg), CAFFEINE HISTORY:Coffee-Intake(No.of servings), Reasons, Tea-Intake(No.of servings), Reasons, Cocoa-Intake(No.of servings), Reasons, Chocolates-Intake(No.of servings), Reasons, Soft Drinks-Intake(No.of servings), Reasons, Comments(If any), STANDARDIZED MEAL:Start Time, End Time, Comments(If any), EPWORTHS SLEEPING SCALE:Date, Start Time, End Time, Sitting and Reading-score, Watching Tv-score, Sitting inactive in public place(e.g.a theatre or meeting)-score, As a passenger in the car/bus for an without break-score, Lying down to rest in the afternoon when circumstances permit-score, Sitting and talking to someone-score, Sitting quietly after lunch without alcohal-score, In a car/bus while stopped for a few minutes in traffic-score, Total Score, ANT PERFORMANCE:Pre IP Administration Date, Start time, End Time, Media Response Time(ms)-score, Alerting Effect(ms)-score, Orienting effect(ms)-score, Executive Attention(ms)-score, C-VAMS ASSESSMENTS:Pre IP Administration Date, Start Time, End Time, Lethargic to vigorous-score, Muddled to Clear Headed-score, Tired to Energetic-score, Unimaginative to Imaginative-score, Listless to Full of go-score, Inefficient to Efficient-score, Total, IP DISPENSING TIME, Lag Phase End Time, SUBJECT DIARY CHECKED AND DISPENSED, ANT PERFORMANCE:1 Hour 10 Minutes Post IP Administration Date, Start time, End Time, Media Response Time(ms)-score, Alerting Effect(ms)-score, Orienting Effect(ms)-score, Executive Attention(ms)-score, C-VAMS ASSESSMENTS:1 Hour 10 Minutes Post IP Administration Date, Start Time, End Time, Lethargic to vigorous-score, Muddled to Clear Headed-score, Tired to Energetic-score, Unimaginative to Imaginative-score, Listless to Full of go-score, Inefficient to Efficient-score, Total, ASSESSMENT OF VITALS:(1 Hour 10 Minutes) Time, Pulse Rate(Per minute), Blood Pressure(mm Hg), ANT PERFORMANCE:3 Hour 10 Minutes Post IP Administration Date, Start time, End Time, Media Response Time(ms)-score, Alerting Effect(ms)-score, Orienting Effect(ms)-score, Executive Attention(ms)-score, C-VAMS ASSESSMENTS:3 Hour 10 Minutes Post IP Administration Date, Start Time, End Time, Lethargic to vigorous-score, Muddled to Clear Headed-score, Tired to Energetic-score, Unimaginative to Imaginative-score, Listless to Full of go-score, Inefficient to Efficient-score, Total, ASSESSMENT OF VITALS:(3 Hour 10 Minutes)Time, Pulse Rate(Per minute), Blood Pressure(mm Hg), ANT PERFORMANCE:5 Hour 10 Minutes Post IP Administration Date, Start time, End Time, Media Response Time(ms)-score, Alerting Effect(ms)-score, Orienting Effect(ms)-score, Executive Attention(ms)-score, C-VAMS ASSESSMENTS:5 Hour 10 Minutes Post IP Administration Date, Start Time, End Time, Lethargic to vigorous-score, Muddled to Clear headed-score, Tired to Energetic-score, Unimaginative to Imaginative-score, Listless to Full of go-score, Inefficient to Efficient-score, Total, ASSESSMENT OF VITALS:(5 Hour 10 Minutes)Time, Pulse Rate(Per minute), Blood Pressure(mm Hg)
Options Reasons = Habitual, Urge for caffeine, Facing withdrawl, Others;Specify
Options SUBJECT DIARY CHECKED AND DISPENSED = Yes, No
Page Title = ELOG - $subject
Reverse sort = 1 |
|