Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 795 of 796  Not logged in ELOG logo
ID Date Icondown Author Author Email Category OS ELOG Version Subject
  Draft   Mon Dec 5 13:06:21 2016  Tim Schelfhouttim.schelfhout@fixbrussel.be    

Hello,

I am using ELOG V2.9.2-2475.  I added some groups and restarted ELOG and all of a sudden it 

  1   Fri Mar 25 00:16:13 107        
  1   Fri Mar 25 00:16:13 107        
  Draft   Wed Mar 24 16:11:04 2021  Dominic Schneiderdschneider@mein.gmxQuestionLinux3.1.3-1-1Pre-fill

Hi all together,

I struggle a lot with the following problem:
I try to prefill certain attributes with the value of exactly the same attribute in the last entry made in the same logbook.

I know I have to go with Preset, tried a view hours and searched the forum but i didn't find a thing. Am I overlooking a flag, an option or whatever, or is there just not such a functionality (which I dont believe)?

I thought about:
Preset Test_Attribute = $Test_attribute
Preset Test_Attribute = Re:$Test_attribute
Preset Test_Attribute = $shell(Command to somehow get last entry and this attributes value)
Not succesful though.

I would be very thankful for help, thanks in advance.

  Draft   Fri Apr 23 18:53:16 2021  Vinzenz Bildsteinvbildste@uoguelph.caQuestionLinuxa0924c1cd54913b 
  Draft   Thu Oct 21 14:57:14 2021  Chris Körnerchris.koerner@physik.uni-halle.deBug reportLinux3.14wrong server HTTP status code when login failed

Hi,

I am trying to access elog through a python client (https://github.com/paulscherrerinstitute/py_elog) and found a strage strange behavior which may be related server side problem. The python script generates get/post messages via the python requests library. This works fine so far and I can view and post messages. However, if a wrong user/password is provided, the server still returns HTTP status code "200 OK", although login failed. Instead, it should return something like "401 Unauthorized". This behavior later causes problems since the python client thinks login was successful. After experimenting around I think this could be caused by a server side misconfiguration. Any ideas?

I am not sure if this imformation is important: We use LDAP as user/password provider for elog.

  Draft   Mon Jul 4 12:32:01 2022  Vasiovasio.william@gmail.comInfoWindows Paid version

Good day all ,

does Elog has a paid version that is not open soureced 

 

regards


William Vasio 

  Draft   Fri Sep 9 20:01:15 2022  Paul Paquetteppaquette@hamptonnh.govQuestion ELOG V3.1.4-a04Elog with out SMTP
ELOG V3.1.5-fe60aaf