Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 721 of 796  Not logged in ELOG logo
ID Date Icon Author Author Email Category OSup ELOG Version Subject Text Attachments
  68071   Tue Aug 4 15:36:48 2015 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows v3.1.0.3Re: Problem with elog and Internet Explorer when saving an entryThis issue should have been fixed in the
new version 3.1.1. If the problem still persists,
try to clear your browser's cache, since
  
  68072   Wed Aug 5 02:59:50 2015 Question William Wongwilliam.wong@fortisbc.comQuestionWindows3.0ELOG 3.0 plus and MS Windows issues.Greetings
all.  A few ELOG users have posted issues
with ELOG 3.0 and newer not working with
  
  68073   Wed Aug 5 12:09:47 2015 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows3.0Re: ELOG 3.0 plus and MS Windows issues.I recompiled the executables according
to

https://msdn.microsoft.com/en-us/library/jj851139.aspx
  
  68074   Wed Aug 5 23:36:29 2015 Reply William Wongwilliam.wong@fortisbc.comQuestionWindows3.0Re: ELOG 3.0 plus and MS Windows issues.Thank you for recompiling ELOG.  Unfortunately,
there is no change in all the test machines
I ran the newly compiled ELOG 3.1.1-1
  
  Draft   Fri Aug 7 16:13:09 2015 Reply Richard Stamperrichard.stamper@stfc.ac.ukQuestionWindows3.0Re: ELOG 3.0 plus and MS Windows issues. 




  
  68076   Mon Aug 10 12:02:27 2015 Reply TorstenJtorsten.jakob@jet-services.comQuestionWindows v3.1.0.3Re: Problem with elog and Internet Explorer when saving an entryHello Stefan,

thanks for you reply. I tried an
ujpdate today to my old installation, but
  
  68077   Wed Aug 12 10:54:27 2015 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows v3.1.0.3Re: Problem with elog and Internet Explorer when saving an entryDo you have the problem on this Forum as
well?

If not, then something is wrong
  
  68096   Tue Aug 18 14:23:29 2015 Reply Daniel Sajdykdaniel.sajdyk@gmail.comQuestionWindowsELOG V3.1.0-3c6Re: "Resolve host names" does not resolve host namesI'm sorry... it was my mistake. I put
Resolve host names in logbook
config instead global.
  
ELOG V3.1.5-2eba886