Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 537 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
  67967   Mon Jun 8 12:02:30 2015 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux3.1.0-2Re: ckeditor "Insert Timestamp" bug (was: Three problems with elogd 3.1.0-2)Indeed the "str" variable at
the gettimedate function had the wrong string
size, so that all date strings got truncated
  
  67969   Tue Jun 9 12:11:19 2015 Reply Stefan Rittstefan.ritt@psi.chCommentLinuxELOG V3.1.0-ac7Re: Emails generated by ElogI fixed both issues in the current GIT
version. Please double check it.

  
  67971   Tue Jun 9 12:51:07 2015 Reply Stefan Rittstefan.ritt@psi.chQuestionLinuxV3.1.0-241Re: subject line bug on resumit elog entries as new?I fixed both issues, now resubmitting an
entry or submitting a new entry both yields
"New LEOG entry".
  
  67978   Tue Jun 9 16:17:06 2015 Reply David PilgramDavid.Pilgram@epost.org.ukQuestionLinuxV3.1.1-2c4f838Re: subject line bug on resumit elog entries as new?Hi Stefan,

I see that you've updated the
elog running this forum today, 5 versions
  
  67979   Tue Jun 9 16:46:48 2015 Reply Stefan Rittstefan.ritt@psi.chQuestionLinuxV3.1.1-2c4f838Re: subject line bug on resumit elog entries as new?Any better now?




  
  67980   Tue Jun 9 16:51:55 2015 Reply David PilgramDavid.Pilgram@epost.org.ukQuestionLinuxV3.1.1-2c4f838Re: subject line bug on resumit elog entries as new?Hi Stefan,

The email sent from here had he
expected (correct) message "A new ELOG
  
  67983   Tue Jun 9 17:09:22 2015 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux3.1.0-2ELOG Forum: drafts cannot be deleted> Another strange thing: the draft got submitted
when I hit the "Back" button after reopening
it.
  
  67984   Tue Jun 9 17:17:11 2015  David PilgramDavid.Pilgram@epost.org.ukBug reportLinuxV3.1.1-22022e6Problem with a draft messageHi Stefan,

I had started to write a completely
different bug report, but then realised I
  
ELOG V3.1.5-3fb85fa6