ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
415
|
Sat Jul 26 20:11:01 2003 |
| eric wooten | wootene@verizon.net | Question | Windows | 2.3.9 | using = or <> or AND as part of a filter ?? |
Is this possible? If so, could you provide an example:
I'm trying to find a way that when you do a search, that you can filter
entries using ( = , <>, AND) on one or more attributes.
ex: Find all workstations for this subnet, but exclude a particular one.
Thats the basic idea.
Can it be done? If so, how?
Thanks,
Eric |
1252
|
Mon Jul 11 09:52:52 2005 |
| Emiliano Gabrielli | AlberT@SuperAlberT.it | Request | All | | userlist multiple select |
Here I am again
My goal is to put a "Co-Authors" Attribute in my logbook, giving the possibility to other people in the control room to have credits about an entry... I added a "Co-Author" attribute, but It shold permit a "multliple" selection (a checkbox is not good) ... the perfect solution would be to add the attribute "multiple" to the <select> tag, and filling the elog Attribute value with a comma separated list of the selections ...
tnx in advance |
69721
|
Fri Jan 19 15:49:13 2024 |
| Frank Heyroth | heyroth(at)cmat.uni-halle.de | Bug report | Linux | 3.1.4 | user change under webserver authentication not recognized |
Hi all,
I am using the Apache webserver authentication and redirection over http (not https). I have configured it 1:1 as described in the Adminguide. In the elog.cfg I set Authentication = Webserver .
All works fine; the webserver requests an authentication and elog recognizes me correctly.
However, when I close and reopen the browser and log in as a different user, elog does not change the user (tested with Firefox and Edge).
I can only change the user if I use a different browser or restart the elogd (reload is not enough).
The X-Forwarded-User header is set to the correct username - I have checked it with a CustomLog in Apache.
Best regards,
Frank |
69754
|
Fri Mar 8 13:09:31 2024 |
| scott | Usershiva.ps@stfc.ac.uk | Question | Linux | Other | 3.1.5 | use LDAP and elog.pwd file |
Hi Members,
I have compiled and installed ELOG in Ubuntu 22.04. My ELOG version is 3.1.5 revision fc6679b. I would like to use both the password file (../logbooks/elog.pwd) and the LDAP for authentication purpose. In addition to this, new users should be able to register and existing users should be able to reset their password.
Anyone could shed some light on how to do this in the configuration file?
Thanks,
Scott |
161
|
Wed Nov 20 17:55:07 2002 |
| tony summerfelt | snowzone25@yahoo.com | | | | upgrading |
this is happened before, and it just happened upgrading from 2.2.2 to 2.2.3
the link at the bottom of the page shows a previously installed version.
i don't install to the elog directory, i install to a ram disk and copy over the new executables, the source, readme and help html.
the link showed 2.1.2 until i upgraded to 2.2.2 (i didn't do anything different than the above. now i'm at 2.2.3 and the link is showing 2.2.2...not that it's a big deal, i'm just wondering what i did wrong |
68287
|
Tue Mar 15 19:53:55 2016 |
| Tim Schelfhout | tim.schelfhout@fixbrussel.be | Question | Windows | ELOG V2.9.2-247 | upgrade problem |
Hello there,
After several years of great ELOG usage I decided to upgrade our ELOG server. I am using it to keep
a logbook of my students.
ELOG runs as a windows service but since I cannot access or change windows services (only have access to the
ELOG directory) I upgraded by installing the executable to my laptop then copying the new ELOG version over the server installation.
Tried this first on my laptop going from V2.9.2-2475 to the last version 3.1.1 and this worked without a problem.
When I tried to reproduce this on the server all the data is there but ELOG displays it as if no theme was installed. (using the default
by the way) No colors, no formatting
... at first I thougt this was because the copy was not complete but a second try reproduced the same result???
Tried going back to the old version but then ALL data was gone (structure and all logbooks still there, but data in logbooks gone) ....
Used -v switch to debug and the logging displayed an MD5 hash mismatch, so the logbooks could not be opened. A restore fixed this ....
I guess upgrading means changing the logbook structure?
Anyway does anyone have any idea why the upgrade loses formatting ?? Tips are welcome |
69693
|
Fri Sep 15 21:42:38 2023 |
| Konstantin Olchanski | olchansk@triumf.ca | Bug report | Other | latest | update elog downloads page |
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. |
68026
|
Wed Jun 17 10:52:16 2015 |
| Hanno Perrey | hanno.perrey@nuclear.lu.se | Bug report | Linux | V3.1.1-5eada05 | unknown user name in "Admin user" line invalidates all entries |
Hej,
I just noted that when having an unknown (or presumably misspelled) user name in the "Admin user" line in the
config file, that the other users are no longer treated as admins and do not see the corresponding link to the
admin page e.g. on the list page. In my specific situation, I in fact have only one user registered (new
password file) but two users still on the admin list (old config file). The one user is only treated as admin
after removing the offending name from the list of admins.
I understand that this might be the intended behavior -- but I wonder if this could lead to a situation where
one locks oneself out, e.g. when adding a misspelled user name to the list.
Thanks and cheers,
Hanno |