Let the user decide which columns should be displayed, posted by Sarah Kuckuk on Thu Jan 18 13:56:59 2024
|
Hello
I was wondering if there is any possibility to let the user decide which columns to show/download in the search results? We have quite a lot of fields and it would help the usefulness of our elog a lot.
(If there is an obvious possibility that I missed I'm sorry).
Thanks a lot! |
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
Sarah Kuckuk wrote: |
Hello
I was wondering if there is any possibility to let the user decide which columns to show/download in the search results? We have quite a lot of fields and it would help the usefulness of our elog a lot.
(If there is an obvious possibility that I missed I'm sorry).
Thanks a lot!
|
|
HTTP headers should be parsed case insensitive, posted by André on Mon Jul 22 16:17:55 2024
|
I'm trying to run elog behind haproxy, but get the error "Invalid Content-Length in header" on posting.
As stated in the manual, haproxy rewrites all headers to lower case.
elogd parses the content-length header case sensitive which is against the HTTP RFC. This might also apply to other headers that get parsed.
For now I'm using the workaround from the manual:
global
h1-case-adjust content-length Content-Length
h1-case-adjust content-type Content-Type
backend elog
option h1-case-adjust-bogus-server
server elog 127.0.0.1:8080
But as the manual states, this should not be used as a permanent solution. |
Re: HTTP headers should be parsed case insensitive, posted by Stefan Ritt on Wed Jul 31 14:21:21 2024
|
I changed elog to interprete the content-length header case in-sensitive and committed the change. Can you try again?
Stefan
André wrote: |
I'm trying to run elog behind haproxy, but get the error "Invalid Content-Length in header" on posting.
As stated in the manual, haproxy rewrites all headers to lower case.
elogd parses the content-length header case sensitive which is against the HTTP RFC. This might also apply to other headers that get parsed.
For now I'm using the workaround from the manual:
global
h1-case-adjust content-length Content-Length
h1-case-adjust content-type Content-Type
backend elog
option h1-case-adjust-bogus-server
server elog 127.0.0.1:8080
But as the manual states, this should not be used as a permanent solution.
|
|
Can Elog make a table?, posted by Walter Reviol on Wed Aug 7 22:54:03 2024
|
Hi!
I like to format an Elog "directory" such that all entries make/occur as a table. Say: 5 columns and a large number of rows. In a sense, make an excel spreadsheet in Elog. Is this possible? How can this be done? Is there perhaps a template?
Thanks in advance.
Walter Reviol
reviol@anl.gov |
Re: Can Elog make a table?, posted by Stefan Ritt on Thu Aug 8 09:07:45 2024
|
I'm not exactly sure what you want to do, but there are two options in elog:
1) Insert directly a table like this one:
Index |
Value |
first |
123 |
second |
432 |
2) Use one ELOG entry as a row in a table. You can try this by clicking on "List" here in the Forum should you not already see the list display, then on "Summary" which give you a spreadsheet like display, where you can specify in the config file which columns of the ELOG entries you want to see. See also the demo here: https://elog.psi.ch/elogs/Linux+Demo/
Best,
Stefan |
choosing the default font ? , posted by Pavel Murat on Wed Nov 13 18:12:34 2024
|
Dear All,
is there a way to choose the default "style" for the HTML encoding ? - I'd like to set it to "Typewriter" but couldn't find the corresponding option in the available docs/ sample config files...
-- many thanks, regards, Pasha |
Re: choosing the default font ? , posted by Stefan Ritt on Fri Nov 15 09:55:11 2024
|
Check elog/themes/default/elog.css and look for font-family.
If you just want the elog entries in monospaced font, you can swith to "plain" encoding at the bottom of the entry form. You can also make this a default (check the docu).
Stefan
Pavel Murat wrote: |
Dear All,
is there a way to choose the default "style" for the HTML encoding ? - I'd like to set it to "Typewriter" but couldn't find the corresponding option in the available docs/ sample config files...
-- many thanks, regards, Pasha
|
|