ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
1463
|
Fri Oct 14 11:28:28 2005 |
| Alex H | alex@synergie-inf.com | Question | Windows | 2.6.0beta1 | Re: Next ELOG Release ? |
> > Hello Stefan,
> > Did you have a release Date for Elog V2.6.0 ?
> > Thanks in Advance.
>
> There is still some unfinished code in the HTML email notification. I guess it will take me still some weeks to
> finish that, since I'm pretty busy these days...
Ok ! Thanks for the rapid answer! |
1488
|
Fri Oct 28 10:42:44 2005 |
| Yoshio Imai | imai@kph.uni-mainz.de | Bug report | Linux | 2.6.0beta5 | Re: Preset text overriden after preview |
Stefan Ritt wrote: |
Thanks for reporting this bug. It's fixed in revision 1534.
- Stefan |
I just tested it, it works. Thanks! |
1521
|
Sat Nov 19 11:57:49 2005 |
| Ulrich Trüssel | ulrich.truessel@familienhund.ch | Question | Windows | 2.6.0beta5 | Re: Changing width in entry mode |
Stefan Ritt wrote: |
Ulrich Trüssel wrote: | Problem: see pic "Eingabe.jpg", if thre are more MOptions to select in entry mode, I have to scroll from right to left all the time. Ti s isn't really comfortable. |
I had a nowrap statement in the MOptions check boxes, which should not be there. I removed that and now the options are wrapped nicely:

The problem is that in HTML, the check boxes and the associated text are sometimes ripped apart, i.e. the box appears at the right corner and the text at the next line. That's why I had the nowrap statement there.
This fix will be contained in the next release of elog. |
Thank you Stefan!!! 
Just as an idea: Some People may find it usefull to have the norap statement in the code. If it's possible for a future release it may be nice to have a flag for this feature! |
1521
|
Sat Nov 19 11:57:49 2005 |
| Ulrich Trüssel | ulrich.truessel@familienhund.ch | Question | Windows | 2.6.0beta5 | Re: Changing width in entry mode |
Stefan Ritt wrote: |
Ulrich Trüssel wrote: | Problem: see pic "Eingabe.jpg", if thre are more MOptions to select in entry mode, I have to scroll from right to left all the time. Ti s isn't really comfortable. |
I had a nowrap statement in the MOptions check boxes, which should not be there. I removed that and now the options are wrapped nicely:

The problem is that in HTML, the check boxes and the associated text are sometimes ripped apart, i.e. the box appears at the right corner and the text at the next line. That's why I had the nowrap statement there.
This fix will be contained in the next release of elog. |
Thank you Stefan!!! 
Just as an idea: Some People may find it usefull to have the norap statement in the code. If it's possible for a future release it may be nice to have a flag for this feature! |
1522
|
Mon Nov 21 10:41:46 2005 |
| Carlos Mateo | cmateo@indra.es | Question | Windows | 2.6.0beta5 | Re: Automatic creation of new entry in another logbook |
Stefan Ritt wrote: |
Carlos Mateo wrote: | I am trying to create an entry in logbook2 when I submit a new entry in logbook1. The automatically created entry in logbook2 will have a reference to the entry that created it. |
Please tell me for what purpose you need two identical logbooks. Maybe what you want can be achieved in a simpler way.
They are not identical. They just share some information
Carlos Mateo wrote: | 1.- Using the "Execute new" I call elog to create the second entry. As the server is single-process, it locks: elog is waiting for elogd to be ready and elogd is waiting for elog to finish to accept new requests. As my server is on a Windows machine I can´t execute elog on background. |
Have you tried to start your elog with the start command under Widnows, like start elog .... This is the equivalent of starting a process in the background under linux.
Thank you. It works with start!
Carlos Mateo wrote: | 2.- I tried to run 2 servers on different ports using the same elogd.cfd file, calling the second server from elog. This "almost" works: the logbook files are updated, but the original server must be restarted to "see" the changes. |
This is because you use the same data directory for both servers. If one server writes a new entry to a file, the other server does not realize this. Only when you restart it, it rescans the whole data directory and gets aware of the new entry. Try using separate data directories for the two servers.
Carlos Mateo wrote: | 3.- Using the "Menu text" option, I create a link to create the new entry. The problem is that attributes are not parsed: a link like this <a href="/logbook2/?cmd=New&pAttr=Value $ID">Test</a> won´t substitute $ID |
Parsing attributes is not implemented and therefore will not work. |
Thank you for your help |
1532
|
Tue Nov 22 17:38:24 2005 |
| Michael Husbyn | michaelh@online.no | Question | | 2.6.0-beta | Thread sort / display order |
Is there a way to choose the display order in threaded mode.
Eg:
1 Test
2 Version 2.0 Testing 1
3 Version 2.5 Testing 2
4 Version 2.3 Testing 3
But the preferred sort order (not the ID) is something like this:
1 Test
2 Version 2.0 Testing 1
4 Version 2.3 Testing 3
3 Version 2.5 Testing 2
Example of parameter perhaps:
Thread order = Field1, $id
Or is this something too difficult to implement? Or already there?
Best regards
Michael Husbyn |
1567
|
Thu Dec 22 15:39:23 2005 |
| Mike | mlmoore@pella.com | Question | | 2.6.0 | Re: Maximum number of LogBooks? Bug? |
Stefan Ritt wrote: |
You're really pushing to the limit 
The maximum number of logbooks is indeed 120. If you have too many logbooks, they are also hard to handle (too many check boxes in the config page etc.). What if you make not one logbook per server, but have a single logbook and use the server as an attribute, like
Attributes = ..., Server, ...
Options Server = Server1, Server2, ...
Now you can ask: How many options are possible for an attribute, and the answer is 100, which is even less than the number of logbooks. But you can make three logbooks, each covering 100 servers, and that covers your 294 servers. |
Thanks for the quick reply and suggestion. I will give that a try.
You might want to consider adding a check that there aren't over 120 logbooks. I manually created the elog.cfg with 294 logbooks. Everything works, except for running into this problem.
Thanks again |
1615
|
Fri Jan 20 02:53:40 2006 |
| Chris Warner | christopher_warner@dcd.uscourts.gov | Comment | Linux | 2.6 | Re: Buffer Overflow? |
Stefan Ritt wrote: |
Chris Warner wrote: | Users can access root level directories by using a modified URL. I saw on some security web sites that this was a problem in previous versions. Was it not fixed in 2.6?
To recreate enter http://yourhost.yourdomain.com/../../../../etc/passwd
view your password file in the browser.
If this was previously reported, is there a fix?
Chris Warner |
Thanks for telling me, I didn't know. I was able to reproduce your problem under certain conditions, and I just released version 2.6.1 to fix it. However it has nothing to do with an old buffer overflow (see elog:941).
I would strongly advise everybody to upgrade as soon as possible. |
Thanks for the quick response! |