| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
50
|
Thu Jul 4 16:52:59 2002 |
 | Heiko Scheit | h.scheit@mpi-hd.mpg.de | | | | elog submit problem |
If a message is submitted via the elog command then the reply string '> ' is only inserted in the first line if a reply is made.
This message was submitted with the following commandline:
elog -v -h midas.psi.ch -p 80 -s elogdemo -l Forum -a "Icon=icon4.gif" -a "Author=Heiko Scheit" -a "Author Email=h.scheit@mpi-hd.mpg.de" -a "Subject=elog submit problem" "...Message-text..."
Please press the reply button to see the problem. |
|
51
|
Thu Jul 4 17:05:03 2002 |
| Heiko Scheit | h.scheit@mpi-hd.mpg.de | Bug report | | | reverse sort and threaded mode does not display first entry |
When the option 'Reverse sort = 1' is used then the first entry
is not displayed (ID=1) when threaded mode is requested.
Probably you can see the problem using this link and switching
on reverse sort.
http://midas.psi.ch/elogdemo/Linux/last20?mode=threaded |
|
52
|
Thu Jul 4 17:09:09 2002 |
| Heiko Scheit | h.scheit@mpi-hd.mpg.de | Request | | | exit status of elog |
The exit status of elog is always 1. It should be zero for
a successful submission. |
|
231
|
Wed Feb 19 14:48:56 2003 |
| Heiko Scheit | h.scheit@mpi-hd.mpg.de | Comment | | | Re: Participation on development of ELOG |
> > We are interested in using your ELOG (which we consider to be a wonderful
> > application) even more. We would like to make a few adaptations in your
> > source code, above all to add some functionality that we are missing.
> >
> > I was wondering if there is a way we could coordinate the development
> > together. For instance, would it be of your interest to receive the code
> > adaptations we do and implement it in your future releases?
>
> Sure, I'm very interested in those and ready to merge it into the main
> development tree.
>
> - Stefan
I think it is very good to include this in elog, but,
since this is also a big security risk (especially if people are
running elogd as root) I would suggest a compile time option to
enable this, like: gcc... -DALLOW_SCRIPT ...
The default should be that it is disabled.
Maybe one should only allow it if the user running elogd is NOT root.
Heiko |
|
322
|
Wed May 7 16:04:45 2003 |
| Heiko Scheit | h.scheit@mpi-hd.mpg.de | Bug report | | | missing '.' in emails |
missing '.' in emails
-----------------------
A dot '.' at the beginning of a line is not transmitted via email.
It is stored in the entry properly though.
Test:
./There is a dot just before '/There...'
Greetings, Heiko
Well it seems here it is working fine...
. |
|
419
|
Thu Jul 31 16:02:41 2003 |
| Heiko Scheit | h.scheit@mpi-hd.mpg.de | Bug report | Linux | 2.3.9 | not proper HTML |
I just upgraded from 2.3.5 to 2.3.9.
There are some errors in the generated HTML. Most of the time
the browser renders everything correctly but sometimes not. Please
check especially (http://validator.w3.org/):
- http://midas.psi.ch/elogdemo/Database/7
There are too many <table> tags before the attribute list:
'Type', 'Operating system',... This should be just one table and
not each row a separate table. Also the first <table> tag lies
outside a <td> tag of the enclosing table.
- http://midas.psi.ch/elogdemo/forum/ |
|
420
|
Fri Aug 1 13:18:42 2003 |
| Heiko Scheit | h.scheit@mpi-hd.mpg.de | Bug fix | Linux | 2.3.9. | problem with boolean attributes |
Boolean attributes were not displayed correctly in version 2.3.9.
Patch is attached. |
| Attachment 1: elog.diff
|
--- elogd.c Fri Aug 1 13:13:09 2003
+++ elogd.c_ Fri Aug 1 13:12:59 2003
@@ -11275,10 +11275,10 @@
{
if (atoi(attrib[i]) == 1)
rsprintf("%s:</td><td class=\"%s\"><input type=checkbox checked disabled></td>\n",
- attr_list[i], class_value);
+ class_value, attr_list[i]);
else
rsprintf("%s:</td><td class=\"%s\"><input type=checkbox disabled></td>\n",
- attr_list[i], class_value);
+ class_value, attr_list[i]);
}
/* display image for icon */
else if (attr_flags[i] & AF_ICON)
|
|
421
|
Mon Aug 4 14:02:52 2003 |
| Heiko Scheit | h.scheit@mpi-hd.mpg.de | Bug fix | Linux | 2.3.9. | width of the textarea is too large (after reply) |
The width of the textarea after pressing reply is too large.
The problem is that the algorithm that searches for the longes line
looks for the next '\r' which it does not find and therefore takes the
number of characters in the text to be the width of the longest line.
To search for '\n' instead should solve the problem. Please find the
diff output below.
$ diff -c elogd.c elogd.c~
*** elogd.c Mon Aug 4 13:57:35 2003
--- elogd.c~ Fri Aug 1 13:13:09 2003
***************
*** 6028,6035 ****
p = text;
do
{
! /* pend = strchr(p, '\r'); */
! pend = strchr(p, '\n');
if (pend == NULL)
pend = p+strlen(p);
--- 6028,6034 ----
p = text;
do
{
! pend = strchr(p, '\r');
if (pend == NULL)
pend = p+strlen(p);
|