ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
66917
|
Fri Oct 8 09:19:13 2010 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.8.0-2331 | Re: how to set text column width |
phichitpon wrote: |
hello
how to set text column width in Elog
thank you
|
There is currently no easy possibility to change this except manually changing the CSS file. But that requires some CSS and HTML knowledge. You would have to change the CSS class "listtitle2" and "summary". |
66916
|
Fri Oct 8 04:53:50 2010 |
| phichitpon | chee_ake@yahoo.com | Question | Windows | 2.8.0-2331 | how to set text column width |
hello
how to set text column width in Elog
thank you |
66915
|
Thu Sep 23 17:22:43 2010 |
| Bill Pier | bpier@clove.org | Question | Windows | 2.7.6-2230 | Re: SQL Database |
What about using something like MySQLfs to get a db backend transparently to ELOG? I use ENCFS, (a FUSE backend), currently to achieve encrypted logbooks and it works fine -- ELOG never knows anything other than reading and writing to logbook files. From what I've read, the MySQLfs backend would work the same, and you likely would gain some of the caching benefits of MySQL, which might help with your read/search times, given the memory requirements of the database of course.
Bill
lance wrote:
|
We have been running elog for a few years now and its solid. The only thing is we are getting to 140k entries over a few books and its starting to slow down whist searching. My questions is can we go to an SQL type database rather than a flat file? Is it worth it? Is anyone running this type of configuration?
|
|
66914
|
Wed Sep 22 14:37:10 2010 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Windows | 2.8 | Re: Elogd service crashes on "reply" with percent character in subject line |
Mike Zuber wrote: |
My logbook kept crashing whenever I tried to reply to an existing entry. I found that the percent sign "%", when used in the subject line, will crash the elogd service when you try to reply to the entry. This appears to only happen with windows installations. I tested this on your Linux logbook and it didn't crash.
Here is the message taken from the Windows event viewer after the crash:
An unhandled win32 exception occurred in elogd.exe [5224].
Thank you for Elog, you have done a good job with it. It is a great logbook.
Mike
|
I could not reproduce your problem. I tried the very simple config file:
[Demo]
Attributes = Author, Subject
and the problem did not occur (see attachment). Can you try the most recent version (elog280-4.exe) with this simple configuration. Maybe you have a more complicated configuration which causes the problem. In that case please send it to me, so that I can reproduce the problem. |
Attachment 1: Capture.png
|
|
66913
|
Wed Sep 22 14:30:53 2010 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | V2.8.0-231 | Re: Error Message in "Demo of database-like elog" |
Robert Heine wrote: |
Stefan Ritt wrote: |
mike cianci wrote: |
I attempted to remove the text editor (like you did in "Demo of database-like elog") using "Show text = 0".
In both your Demo and my logbook when you hit "New" - Explorer generates the folowing error message
Error: The Textarea with id or name set to "text" was not found.
Is there a solution or do we just live with it.
Thanks, Mike
|
Thanks for reporting that bug. I fixed it in SVN revision 2188, and the fix will be contained in the next release.
|
I am getting the same message in the current version (V2.8.0-2312), if the "Preset text" text body contains the equal sign '='. Then this message pops up and the HTML-editor dosn't show its menu bars, with the elog- or plain text editor this does not happen. It happens as well with firefox as with internet explorer.
best regards
Robert
|
I found a bug there, but am not 100% sure if it fixed your problem. Can you please try the current SVN version 2331? I made a new intermediate release elog280-4.exe for you. |
66912
|
Wed Sep 22 14:21:50 2010 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 2.8.0 | Re: elog 2.8.0 as daemon crashes when editing selected threaded list |
Mark Bergman wrote: |
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, and then edit it, to change the status field for all posts in the thread to "closed".
Now, as soon as the "edit" button is clicked, elog crashes. This happens on every thread and logbook that I've tried. The elog logfile itself doesn't show anything useful.
However, if eLog is run with "-v" in place of "-D", it does not crash.
Environment:
CentOS 5.4
eLog 2.8.0 built Aug 5 2010, 12:24:11
|
I tried to reproduce your problem with following simple configuration file:
[Bergman]
Attributes = Author, Status
Options Status = open, closed
Preset Author = $long_name
The result was that it worked fine (see attachments). Maybe there is another setting in your configuration file which causes the problem. Can you try the simple configuration and see if it still crashes? |
Attachment 1: open.png
|
|
Attachment 2: closed.png
|
|
66911
|
Mon Sep 20 14:54:21 2010 |
| Stefan Ritt | stefan.ritt@psi.ch | Info | Linux | 2.8.0 | Re: Cannot bind to port 8080 |
marco meneghelli wrote: |
good morning,
I have installed elog 2.8.0 from terminal but when I type
elogd -p 80
or simply
elogd
the system tells me
Cannot bind to port 8080
Can someone help me?
Thanks
Marco M
|
Under linux, only the "root" user can start programs on ports below 1024. If you get problems binding to ports above 1024 (such as 8080) it means that some other program uses already that port. You can check what is running usually with
netstat -l -p
|
66910
|
Fri Sep 17 14:54:51 2010 |
| marco meneghelli | marco.meneghelli@bo.infn.it | Info | Linux | 2.8.0 | Cannot bind to port 8080 |
good morning,
I have installed elog 2.8.0 from terminal but when I type
elogd -p 80
or simply
elogd
the system tells me
Cannot bind to port 8080
Can someone help me?
Thanks
Marco M |