Re: Elog crashes with null Username, posted by Stefan Ritt on Fri Apr 21 10:57:07 2017
|
I made a new release for you 3.1.3
Xuan
Wu wrote:
No, We are using the released version 3.1.2 |
|
Re: Limiting search data, posted by Stefan Ritt on Fri Apr 28 08:15:56 2017
|
I don't get your point. If you go on the list page of this forum, you see -- all entries -- in the period quick filter, but you only see one page
of entries, which is rather quick. This can be changed wiht "Entries per page", which defaults to 20. Do you have a different set-up?
Alan |
|
Re: Limiting search data, posted by Stefan Ritt on Fri Apr 28 12:33:55 2017
|
Ok, got it. Will put it on the to-do list.
Andreas
Luedeke wrote:
I think I understand the question (although I have no answer): |
|
Re: Is it possible to generate a table of contents based on h1/h2/h3 HTML tags?, posted by Stefan Ritt on Mon Jun 19 08:33:07 2017
|
This is not possible.
Stefan
Niklas |
|
Re: my elogd crashes when editing the configuration, posted by Stefan Ritt on Thu Jun 22 20:55:36 2017
|
Might be some bad data in your elogd.cfg file. Have a look at that file with a text editor to see if there's anything wrong. Start with a pristine config
file from the
|
|
Re: Server dropping SSL connection while uploading large files, posted by Stefan Ritt on Thu Jun 29 08:36:03 2017
|
One possibility is to run elog in non-SSL mode and put an Apache server in front of it. The Apache server can then do the SSL communication, and forward
all requests to elog in plain text (non-SSL). This has been proven to work with large attachments, actually that's the way I use it.
I didn't find time to debug the SSL problem. If anybody is interested in doing so, the relevant code is in function server_loop() around |
|
Re: Virus in latest elog?, posted by Stefan Ritt on Fri Jul 14 16:58:48 2017
|
Hi Daniel,
you're the first one reporting about this virus. We have different virus checkers here at our lab and none of them triggered. So I guess
it is a false alarm. |
|
Re: elogd hangs, posted by Stefan Ritt on Fri Aug 18 08:59:08 2017
|
I have to figure out where elog hangs. I guess it must be some kind of endless loop, triggered by some corrupt data in one of the elog entries. Under
linux this is fairly simple (just run elogd under the gdb debugger, wait until it hangs, then press ctrl-c and enter "where" to see a full stack
dump where elogd is currently executing). Under Windows this is more difficult, since you need Visual C++ from Microsoft to do the debugging. One thing |