Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 139 of 807  Not logged in ELOG logo
ID Date Icon Author Author Email Category OS ELOG Version Subject Text Attachments
  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
  
  68732   Thu Feb 1 14:55:24 2018 Reply Peter Kpkravt@gmail.comBug reportLinuxV3.1.2-bd75964Re: Entries disappear after editing + UTF16 problemDear Stefan,

Thanks for quick reply.
I checked List drafts
  
  68731   Thu Feb 1 10:34:42 2018 Reply Stefan Rittstefan.ritt@psi.chBug reportLinuxV3.1.2-bd75964Re: Entries disappear after editing + UTF16 problemThe message is not lost, but becomes a
"draft". This works similar in
most email systems. When you edit an email
  
  68730   Thu Feb 1 10:14:55 2018 Reply Andreas Luedekeandreas.luedeke@psi.chQuestionWindows2.9.2->3.1.3 Re: v3.1.3 does not work with logbooks from v2.9.2?Hi Yves,

just my two pence,
maybe they help you to figure out what's
going on:

versions 2.* had
  
  68729   Thu Feb 1 03:12:03 2018 Question Yvesvanhaarlemyves@gmail.comQuestionWindows2.9.2->3.1.3 v3.1.3 does not work with logbooks from v2.9.2?I have just upgraded elog from 2.9.2 ->
3.1.3.

3.1.3 runs fine with new logbooks.
 test1.pngtest2.png 
ELOG V3.1.5-3fb85fa6