Re: Maximum number of attributes, posted by David Pilgram on Mon Jan 8 15:56:40 2024
|
In my case, I had a number of attributes which had a varied prefix. For example, "progressed" , which could have no prefix, or prefix
"I", "To be", "Strongly", "Seriously"... and that was true (the same prefixes, or at least many of them) for a
number of attributes. Splitting them into two groups, the prefixes and the action, allowed me to gain more actual attributes without having to recompile. |
|
Re: Maximum number of attributes, posted by Dr Marta Divall on Mon Jan 8 16:18:45 2024
|
To explain the problem, we have silicon chip designs, which we log with an indentifyier, which is the attribute for easy search, as we want to follow
their progress from design thorugh fabrication to testing, involving many people. They are called D_001; D_099...you get it. We have reached the 100, but
maybe it is the est just to create an archive after each 100 design and make a new tab/logbook. Any other suggestions are of course welcome. |
|
Re: Maximum number of attributes, posted by Stefan Ritt on Mon Jan 8 16:25:05 2024
|
Why don't you simply create a single attribute "identifier", which then gets a value D_001, ..., D_xxx. You can still use the D_xxx in
full text search.
Stefan |
|
Re: Maximum number of attributes, posted by David Pilgram on Mon Jan 8 17:30:42 2024
|
Or what about the "ticket number" feature? Every new entry thread (sorry, confusing terminology on my part) would
increment the ticket number by one, and there is no limit as far as I am aware. This is all explained in the elogd configuration documentation.
Stefan |
|
Re: Maximum number of attributes, posted by David Pilgram on Mon Jan 8 21:08:43 2024
|
As for my suggestion earlier, now I'm at my computer with working elog. I think that the following four lines (three I guess already there but need
alteration for this) need to appear in your elogd.conf file. The first three should also include any other thing you need to display etc. I've
cut this down to the bear bones, and ... means anything else you want to add. |
|
Re: Let the user decide which columns should be displayed, posted by Stefan Ritt on Mon Jan 22 12:15:26 2024
|
There is a general display option "List display", but that applies for all users. For the download, you can load the CSV file into a spreadsheet
program and then delete some columns.
Stefan |
|
Re: How to not expose elog port when running under a reverse proxy, posted by Frank Heyroth on Mon Jan 22 20:50:50 2024
|
Hi,
as I understand right you can do this in the elogd.cfg via
Interface = 127.0.0.1 |
|
Re: user change under webserver authentication not recognized, posted by Frank Heyroth on Wed Jan 24 14:50:21 2024
|
I found the reason of the bug:
In line 27441 of elogd.cxx the http_user is overwritten by the user saved in the sid_ array as a sideeffect of the sid_check
function: |