Entries disappear after editing, posted by Peter K on Sat Jan 27 03:37:11 2018
|
Dear elog community,
We have a problem with elog V3.1.2-bd75964.
Sometimes entries disappear from the list after editing. |
BSOD, posted by Ales Novak on Fri Feb 23 21:27:12 2018 
|
Hi,
I have been using elog for a few years and it is a wonderfull software and has been one that I can't go without. So thank you very much for
making it. |
|
"Slow script" problem posting/editing from Safari -- browser hangs, times out, posted by Michael Kelsey on Wed Apr 11 18:14:35 2018
|
Hello! The CDMS collaboration is using e-Log as one of it's issue tracking systems. In the last few months, I have noticed a problem
when either creating or editing entries from my usual Safari browser (currently 11.1 on MacOSX 10.13.4): The [Submit] button triggers
a spinning beach ball, with no connection to our e-Log server, and after several minutes, Safari complains the the page had to be reloaded, discarding |
|
Elog ID entry bug at >99999 entries, posted by Joseph McKenna on Fri May 4 14:43:35 2018
|
We have a possible bug with elog that the ID for an elog entry at over 99,999 entires reads as 10,000...
68792/1 Illistrates the problem, we use this ID often to cross reference from out datalog...
Is this a know bug we can find a fix for? We are using: elogd 2.9.2 built Jul 14 2015, 18:58:06 revision |
|
elogd service crashes after windows update, posted by Tom Roberts on Fri May 18 00:57:33 2018
|
We have been using elog on Windows 10 for a long time. Today, after a Windows update, the elogd service started crashing (error 1067, unexpected termination).
It ran fine just before the Windows update (which took > 1 hour, so it was a major one). Uninstalling and re-installing did not help, including replacing
my elogd.cfg with the default. Installing on another PC (that also has this update) fails in the same way. I have a good backup of my logbook. |
|
Problem with eloglang.german_UTF8, posted by Andreas Luedeke on Tue Aug 7 10:53:45 2018
|
I had a problem with restarting ELOG since about a year, and finally I found the culprit. I just want to share it here, to prevent anyone else to make
the same mistake,
Apparently the files resources/eloglang.* are rather sensitive to the syntax. But it doesn't tell you: no warning or error message comes |
|
Compile issues on Fedora withe current elog source, posted by Allen Tuttle on Tue Sep 11 19:46:40 2018
|
Tried compiling on FC27 and 28, both result in binaries but with serious issues; writing data larger than then allowed.
Example output:
make
gcc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -Wno-deprecated-declarations |
|
messy code for chinese charactor, posted by Wenhao Huang on Fri Oct 26 08:56:59 2018
|
| The Chinese character appears messy code. The encoding way is the default utf-8. How can I solve this problem? |