Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 166 of 807  Not logged in ELOG logo
ID Date Icon Author Author Email Category OS ELOG Versiondown Subject
  69879   Wed Jun 18 01:20:47 2025 Warning Harry Martinharrymartin772@gmail.comBug reportLinux3.1.5passing %s to $shell interpreted differently in preset vs preset on reply

I am finding that '%s' passed to a $shell(...) command must be escaped when calling from Preset on reply, but not when calling Preset new.  Example:

[tickler]
Comment = Automated Tickler List Experiment
Attributes = Blurb, TickleDate
Type TickleDate = date
Required Attributes = Blurb
Preset TickleDate = $shell(date -d 'now + 30 days' '+%s')
Preset on reply TickleDate = $shell(date -d 'now + 30 days' '+%%s')
Date Format = %Y-%m-%d

Note that I have to escape the Preset on Reply's shell command argument with double percent signs, but not on Preset new.  The configuration I have provided here does work and correctly overrides the output per the Date Format spec.  This scenario should be easy to reproduce.

It could be I am doing something incorrectly, but it seems to me that there is no reason why the calls should need to be handled differently.  I can live with this for the moment, but I do hope it is fixed in a later release so that $shell calls have consistent syntax and semantics.

 

  69880   Thu Jul 17 23:43:25 2025 Warning Harry Martinharrymartin772@gmail.comBug reportLinux3.1.5collapse does not seem to work as expected

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.

  69882   Fri Jul 18 22:42:02 2025 Warning Harry Martinharrymartin772@gmail.comBug reportLinux3.1.5Re: collapse does not seem to work as expected

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.

 

  69883   Fri Jul 18 23:10:33 2025 Warning Harry Martinharrymartin772@gmail.comBug reportLinux3.1.5Re: collapse does not seem to work as expected

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.

 

 

  69884   Sat Jul 19 00:02:45 2025 Warning Harry Martinharrymartin772@gmail.comBug reportLinux3.1.5Re: collapse does not seem to work as expected

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.

 

 

 

  69885   Sun Jul 20 23:20:02 2025 Warning Harry Martinharrymartin772@gmail.comBug reportLinux3.1.5Re: 3-level conditional not working

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.

 

  69535   Sun Jun 26 01:47:02 2022 Question Andrea Capraacapra@triumf.caQuestionLinux3.1.4-bcd7b50Edit entry from command line and appending attachment

I would like to edit an existing entry by adding new attachments at each call of elog from the command line.

If I issue

elog -h localhost -p 8XXX -l test -f /path/to/file_0.pdf -e N -x

and then 

elog -h localhost -p 8XXX -l test -f /path/to/file_1.pdf -e N -x

file_1.pdf replaces file_0.pdf, while I'd like entry N to have both pdfs.

Is there a workaround?

 

 

  69234   Sun Oct 18 16:59:38 2020 Question Sergei Gavrilovs.gavrilov@gmail.comRequestWindows3.1.4-a04faf9fUp-to-date windows-version

Dear colleagues,
Can someone compile an up-to-date windows-version or write a manual how to do it in Windows without compiling errors?
Thank you.

ELOG V3.1.5-3fb85fa6