Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 208 of 806  Not logged in ELOG logo
ID Date Icon Author Author Email Category OS ELOG Versiondown Subject Text Attachments
  68843   Wed Sep 12 15:57:31 2018 Reply Allen TuttleAllenEmail@wavecable.comBug reportLinux3.1.3Re: Compile issues on Fedora withe current elog sourceA quick test suggests I can't just
replace sprintf with snprintf.
Original error:
  
  68844   Wed Sep 12 20:52:22 2018 Reply Andreas Luedekeandreas.luedeke@psi.chBug reportLinux3.1.3Re: Compile issues on Fedora withe current elog sourceStefan said "code is commited":
that means you can download the latest version
from https://bitbucket.org/ritt/elog, as
  
  68845   Thu Sep 13 06:12:59 2018 Reply Allen TuttleAllenEmail@wavecable.comBug reportLinux3.1.3Re: Compile issues on Fedora withe current elog sourceLatest compile effort on Fedora 28 using
the bitbucket source downloaded at 21:12
PDT:
  
  68849   Fri Oct 19 08:38:06 2018 Question Sergio Navarretesergionavarrete+elog@gmail.comQuestionWindows3.1.3Logfile not registering entry numbers?I have configured a logbook with the logfile
on, but when a user replies to an entry
the line logged goes
  
  68850   Fri Oct 19 13:08:30 2018 Reply Andreas Luedekeandreas.luedeke@psi.chQuestionWindows3.1.3Re: Logfile not registering entry numbers?It looks like you've found a bug in
ELOG. I've checked my elog.log and see
that all NEW entry lines show "#0".
  
  68857   Mon Oct 29 14:26:28 2018 Reply David PilgramDavid.Pilgram@epost.org.ukQuestionWindows3.1.3Re: Logfile not registering entry numbers?As a regular elog (ab)user, I have seen
this behaviour from time to time.  So
far as I recall, the cause actually is that
  
  68880   Fri Dec 21 14:59:05 2018 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux3.1.3Re: inactive usersThanks for the fix, I merged it into the current
development branch.
  
  68884   Tue Feb 5 07:31:44 2019 Question Stefano Lacaprarastefano.lacaprara@pd.infn.itBug reportLinux3.1.3quick filter not working for attributes with special char Hi,
  I'm using elog 3.1.3 and I have an elogbook
with an attribute with name 
  
ELOG V3.1.5-3fb85fa6