[global] config still editable by admin of top group, posted by Damian Goeldi on Mon Sep 15 13:16:58 2025
|
The ETH physics department is running an ELOG behind an Apache reverse proxy:
ProxyPass / http://localhost:$port/ retry=0
ProxyPassReverse / http://localhost:$port/ |
Re: [global] config still editable by admin of top group, posted by Stefan Ritt on Mon Sep 15 15:11:41 2025
|
You can have authentication via the Webserver or the ELOG internal one, but this is on a global level for all logbooks. You cannot mix this between logbooks.
For that, you would have to run two instances of ELOG at two different ports.
Stefan |
collapse does not seem to work as expected, posted by Harry Martin on Thu Jul 17 23:43:25 2025
|
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. |
|
Re: collapse does not seem to work as expected, posted by Harry Martin on Fri Jul 18 22:42:02 2025
|
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 |
|
Re: collapse does not seem to work as expected, posted by Harry Martin on Fri Jul 18 23:10:33 2025
|
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 |
|
Re: collapse does not seem to work as expected, posted by Harry Martin on Sat Jul 19 00:02:45 2025
|
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 |
|
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. |
|
3-level conditional not working, posted by Harry Martin on Thu Mar 20 07:34:24 2025
|
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] |
|
Re: 3-level conditional not working, posted by Harry Martin on Sun Jul 20 23:20:02 2025
|
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 |
|
[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 |
show attributes directive does not work?, posted by Harry Martin on Sat Aug 16 02:48:42 2025 
|
Follows a very simple logbook definition:
[simple]
Comment = test show attributes directive |
|
[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."
|
|
once a week we are having elogd segault?, posted by mathew goebel on Fri Jul 18 17:46:43 2025
|
Jul 17 20:36:21 elog kernel: elogd[179095]: segfault at 7ffda4d82000 ip 00007f97033a1406 sp 00007ffda4d58c38 error 6 in libc-2.28.so[7f9703374000+1cd000]
Elog version ELOG V3.1.5-30ada1df |
|
Re: once a week we are having elogd segault?, posted by mathew goebel on Wed Aug 6 17:08:46 2025
|
We have since discovered that the security team is scanning the box in question once a week when the service crashes, with nexpose.
So if you see something similar then you might want to explore that.
mathew |
|
Re: once a week we are having elogd segault?, posted by Stefan Ritt on Thu Aug 7 11:04:39 2025
|
Probably some very strange URL form nexpose to trigger a potential buffer overflow. If I get the precise URL which crashes elogd, I can reproduce and
fix it.
Otherwise my usual advice: Run elogd behind an Apache proxy and do the authentication there. This way nexpose does not get to elogd, it will |
|
passing %s to $shell interpreted differently in preset vs preset on reply, posted by Harry Martin on Wed Jun 18 01:20:47 2025
|
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: |
WYSIWYG Editor Not Showing in HTML Mode, posted by Pawel Nita on Mon May 5 11:39:17 2025
|
Hi all,
I'm experiencing an issue on Kubuntu 24.04 where the WYSIWYG editor (in HTML mode) doesn't appear at all. This happens across multiple
browsers (tested with Firefox and Chromium). The editor area is simply blank, without any visible toolbar or editable content area. |
|
Re: Custom input forms implementation , posted by Marcel Zauner-Wieczorek on Mon Apr 28 11:50:25 2025
|
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 |