Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 137 of 806  Not logged in ELOG logo
ID Date Icon Author Author Email Category OS ELOG Version Subject Text Attachments
  68740   Thu Feb 8 15:09:42 2018 Reply Peter Kpkravt@gmail.comBug reportLinuxV3.1.2-bd75964Re: Entries disappear after editing + UTF16 problemDear Stefan and Andreas,

We have updated our elog to 
  
  68739   Wed Feb 7 15:28:47 2018 Reply Andreas Luedekeandreas.luedeke@psi.chBug reportLinuxV3.1.2-bd75964Re: Entries disappear after editing + UTF16 problemHi Stefan,

I think there
is a misunderstanding: there is an ELOG commit
with the GIT ID bd75964.

It
  
  68738   Wed Feb 7 14:26:01 2018 Reply Stefan Rittstefan.ritt@psi.chBug reportLinuxV3.1.2-bd75964Re: Entries disappear after editing + UTF16 problemTell me your current seven digit number
and I can check if your version is too old.

  
  68737   Wed Feb 7 14:22:23 2018 Reply Peter Kpkravt@gmail.comBug reportLinuxV3.1.2-bd75964Re: Entries disappear after editing + UTF16 problemyes, that is exactly where I got this V3.1.2-bd75964
version!

Do you recommend to download it
  
  68736   Tue Feb 6 10:23:26 2018 Reply Stefan Rittstefan.ritt@psi.chBug reportLinuxV3.1.2-bd75964Re: Entries disappear after editing + UTF16 problemThe -bd... number must be from the .apk
package, which I don't have control over.
You have to check the elog git hash code.
  
  68735   Tue Feb 6 10:15:29 2018 Reply Peter Kpkravt@gmail.comBug reportLinuxV3.1.2-bd75964Re: Entries disappear after editing + UTF16 problemWe installed our elog from .apk in November
2017.

Version V3.1.2-bd75964
  
  68734   Fri Feb 2 08:31:35 2018 Reply Stefan Rittstefan.ritt@psi.chBug reportLinuxV3.1.2-bd75964Re: Entries disappear after editing + UTF16 problemYou might have to update to the current
elog version. This feature was implemented
in Dec. 2016. 
  
  68733   Fri Feb 2 00:02:54 2018 Reply Yvesvanhaarlemyves@gmail.comQuestionWindows2.9.2->3.1.3 Re: v3.1.3 does not work with logbooks from v2.9.2? - solvedHi Andreas,

Thanks - you pointed me in the
right direction. It appears that my logbooks
  
ELOG V3.1.5-3fb85fa6