Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 730 of 808  Not logged in ELOG logo
New entries since:Thu Jan 1 01:00:00 1970
ID Date Icon Author Author Email Category OSdown ELOG Version Subject Text Attachments
  69633   Fri Jan 27 22:25:18 2023 Reply Andreas Luedekeandreas.luedeke@psi.chRequestAll-Re: Wikipedia Article deletedIt appears to me that this is a really
stupid problem: the article provides many
links to sources, but they are just links,
  
  69634   Sat Jan 28 08:11:05 2023 Reply John Kellyjohn@secondcomingtechnologies.comRequestAll-Re: Wikipedia Article deletedWikipedia
has been an unreliable source for a very
long time, just for the reasons that we are
  
  69635   Sat Jan 28 14:26:07 2023 Reply David PilgramDavid.Pilgram@epost.org.ukRequestAll-Re: Wikipedia Article deletedI am rather with John on this.

I deliberately stopped contributing
to Wikipedia years ago after I added an observation
  
  69674   Sat Jun 17 22:13:01 2023 Idea Andreas Luedekeandreas.luedeke@psi.chQuestionAll3.1.3Re: Nested commands in logbookAtrributes can only be defined once in
a logbook.
But you can select which attributes
  
  69720   Thu Jan 18 13:56:59 2024 Question Sarah Kuckuksarah.kuckuk@uni-tuebingen.deQuestionAllV3.1.3-7933898Let the user decide which columns should be displayedHello

I was wondering if there is any
possibility to let the user decide which
  
  69723   Mon Jan 22 12:15:26 2024 Reply Stefan Rittstefan.ritt@psi.chQuestionAllV3.1.3-7933898Re: Let the user decide which columns should be displayedThere is a general display option "List
display", but that applies for all users.
For the download, you can load the CSV file
  
  69807   Mon Jul 22 16:17:55 2024 Entry Andréandre.althaus@tu-dortmund.deBug reportAll3.1.5HTTP headers should be parsed case insensitiveI'm trying to run elog behind haproxy,
but get the error "Invalid Content-Length
in header" on posting.
  
  69817   Wed Jul 31 14:21:21 2024 Reply Stefan RittI cstefan.ritt@psi.chBug reportAll3.1.5Re: HTTP headers should be parsed case insensitiveI changed elog to interprete the content-length
header case in-sensitive and committed the
change. Can you try again?
  
ELOG V3.1.5-3fb85fa6