elog 2.8.0 as daemon crashes when editing selected threaded list, posted by Mark Bergman on Tue Sep 14 01:15:22 2010
|
I recently upgraded elog from 2.7.8 to 2.8.0 (and moved servers, removed unused logbooks, etc.). I'm now having a problem where elog consistently crashes
when attempting to edit multiple entries. This is a very common use case, as we use a "status" field, set to "open" or "closed"
to track problems. When a problem is resolved, we will go to the "list" display, set it to "threaded", "select" the thread, |
Re: elog 2.8.0 as daemon crashes when editing selected threaded list, posted by Stefan Ritt on Wed Sep 22 14:21:50 2010 
|
Mark Bergman wrote:
I recently upgraded elog from 2.7.8 to 2.8.0 (and moved servers, removed unused logbooks, etc.). I'm |
|
Re: Elogd service crashes on "reply" with percent character in subject line, posted by Stefan Ritt on Wed Sep 22 14:37:10 2010
|
Mike Zuber wrote:
My logbook kept crashing whenever I tried to reply to an existing entry. I found that the percent sign |
|
Re: Elogd service crashes on "reply" with percent character in subject line, posted by Mike Zuber on Thu Oct 14 17:50:56 2010
|
Stefan Ritt wrote:
|
|
Re: Elogd service crashes on "reply" with percent character in subject line, posted by Stefan Ritt on Tue Nov 16 15:56:53 2010
|
Mike Zuber wrote:
|
|
Found some spelling errors in eloglang.german, posted by Andreas Luedeke on Thu Jan 13 10:07:17 2011
|
| corrected file is attached |
New entries are not visible from other logbooks based on the same logbook dir through Subdir, posted by JacekK on Fri Jan 14 00:07:01 2011
|
Hi,
I have two logbooks based on the same data directory through "Subdir" option and when I add new
entry in one logbook, then that
entry is not visible in other logbook. |
|
elog command creates always UTF-8 encoded entries, posted by Andreas Luedeke on Wed Jan 19 13:30:48 2011
|
If I create an entry via the web-interface, the defined encoding of the browser is used.
If I create an entry via "elog", it is always stored in UTF-8 encoding.
For the text I can overcome that with HTML encoding, but for attribute values the encoding does not show properly.
|