>       Error: Command "config" is not allowed for user ""

Could it be related to the error messages thrown by "activate user"? see
https://elog.psi.ch/elogs/Forum/69479

K.O.

> elogd binary from EPEL

thank you for bringing this up to our attention. we recently went through this with debian and ubuntu. the elog package was severely out of date and 
did not include the security patches that went it right before covid started in the Winter of 2020.

the elogd package in EPEL7 is insecure and should not be used. (I see it is removed from EPEL8, EPEL9 and current Fedora).

I will have to contact EPEL maintainers to have it removed from EPEL7 (or at least to have it marked as "insecure, do not use").

https://dl.fedoraproject.org/pub/epel/7/SRPMS/Packages/e/elog-3.1.4-1.20190113git283534d97d5a.el7.src.rpm

https://packages.fedoraproject.org/pkgs/elog/elog/
https://packages.fedoraproject.org/pkgs/elog/elog/fedora-35.html
https://packages.fedoraproject.org/pkgs/elog/elog/epel-7.html

note in the changelog "Update to post-release snapshot of 3.1.4. - Fix several security issues."

K.O.

- rsprintf("<textarea rows=%d cols=%d wrap=hard name=\"Text\">\n", height, width);
+ rsprintf("<textarea rows=%d cols=%d name=\"Text\">\n", height, width);

my vote is to remove "wrap=hard":

1) I try to read the specs and my head explodes: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/textarea
2) textarea should just accept input typed by user, should not try to "neatify" it. if user wants long lines, we should let them.
3) this bug (introduced in recent safari, the best I can tell)

K.O.

The elog downloads page is slightly out of date, https://elog.psi.ch/elog/download.html

1) the "git clone" instructions work (but there is no git tags corresponding to different releases, I suggest adding test: "elog developers 
recommend always using latest version from elog git repository").

2) "elog source code", recommends downloading tar file, but latest tar file is from February 2023, probably out of date. people who can compile elog 
from sources can do "git clone", is the "tar" method still relevant?

3) windows binaries, latest available is from 2018, before the famous security fixes, probably no longer safe for running on the open internet. I 
suggest we remove this section and say "sorry, windows binaries no longer available".

4) linux binaries, all links are dead, and we have requested removal of elog packages from red hat, debian and ubuntu. (and they have been removed).

K.O.

> wget https://elog.psi.ch/elog/download/RPMS/elog-latest.el7.x86_64.rpm

I confirm, both wget and curl do not work, not happy with https certificate. (current macos)

I confirm download using web browser works (current google-chrome).

But the el7 binary RPM will not work on el8 or el9.

Simplest way to proceed is to build elog from git sources, per https://elog.psi.ch/elog/download.html

mkdir -p $HOME/packages
git clone https://bitbucket.org/ritt/elog --recursive
cd elog
make
(make install is not needed, you can run elog from the git clone and build directory).

This is how we build and run elog at TRIUMF, including the MIDAS Forum elog.

K.O.

> EPEL retired the ELOG package for security reason

no, this is not what happened, we (I) requested removal of elog packages from epel, debian and ubuntu because they had obsolete pre-cve (insecure) 
versions that should not be used. they were very pleasant, quick and efficient dealing with this. (but obviously they could not retroactively 
remove elog from old versions of ubuntu and debian).

we opted to not reclaim ownership of these packages (original person who created these packages had drifted away) because
none of us know how to create debian packages and all of us (speaking for myself) know how much PITA is building RPM packages.
plus I do not know if Stefan has access to el8 and el9 machines (I do not, we are moving to ubuntu/debian wholesale).

I recommend building elog from git sources. it is simple, two commands (git clone + make) vs one command (rpm install),
it ensures you always have the latest version available, it is easy to update (git pull + make) and you do not
get any surprise updates (from nightly apt update/upgrade).

K.O.

I think what you want already exists, for example, when I reply to this message, there is this "Category" selection box with predefined answers 
"Info", "Bug report", etc. For your case, replace "Category" with "Wafer type ID", replace "Info" with "1", "Bug report" with "2", etc. You numeric 
values will be strings containing numbers "1", "2", etc. That works for you? K.O.

> This is a nice idea, but currently no text substations in templates are implemented. It only works in attributes right now.

but can it be done by javascript injection? load a custom .js or .html file, in this file run javascript code to root down the DOM tree until you 
find the right place, replace .innerHTML with current date?

K.O.