Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 789 of 801  Not logged in ELOG logo
New entries since:Thu Jan 1 01:00:00 1970
ID Date Icon Authordown Author Email Category OS ELOG Version Subject Text Attachments
  68383   Thu Aug 11 16:40:47 2016 Reply Alan Grantagrant@winnipeg.caQuestionWindows3.1.1Re: Quick Filter not searching on EnterYes it works fine in this forum. I also
discovered my problem is resolved using
Chrome. I'll dig into browser and
  
  68384   Thu Aug 11 17:09:47 2016 Reply Alan Grantagrant@winnipeg.caQuestionWindows3.1.1Re: Quick Filter not searching on EnterFound the problem. I needed to turn on
Compatibility View in IE for the site. Regards.

  
  68443   Wed Oct 26 16:39:38 2016 Question Alan Grantagrant@winnipeg.caQuestionWindows3.1.2Datetime format with elog clientWhat is the input format expected by the
elog client for a required Datetime defined
field when inserting a record? (Eg: October
  
  68444   Wed Oct 26 21:41:42 2016 Reply Alan Grantagrant@winnipeg.caQuestionWindows3.1.2Re: Datetime format with elog clientUPDATE:

As I continue to test and troubleshoot
this problem I noticed something peculiar:
  
  68446   Thu Oct 27 04:16:10 2016 Reply Alan Grantagrant@winnipeg.caQuestionWindows3.1.2Re: Datetime format with elog clientI really appreciate your reply David.

There's only one Datetime defined
field that I'm working with so I'm
  
  68508   Thu Dec 15 15:42:06 2016 Reply Alan Grantagrant@winnipeg.caBug reportMac OSX3.1.2Re: elogd crash on sorting the entries by an datetime attributeHi Stefano.

This may or may not have anything
to do with your specific problem but I notice
  
  68513   Sun Dec 18 08:51:47 2016 Question Alan Grantagrant@winnipeg.caBug reportWindows3.1.2Elog crashes with null UsernameI haven't found any reporterd issues
in the forum similar yet, but it appears
there is a bug in Elog when logging into
  
  68515   Mon Dec 19 19:42:05 2016 Reply Alan Grantagrant@winnipeg.caBug reportWindows3.1.2Re: Elog crashes with null UsernameThanks for the speedy fix.

FYI, our other Elog instances which
are running ealrier versions do not exhibit
  
ELOG V3.1.5-3fb85fa6