Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 177 of 807  Not logged in ELOG logo
New entries since:Thu Jan 1 01:00:00 1970
ID Date Icon Authordown Author Email Category OS ELOG Version Subject
  931   Sat Feb 12 17:08:32 2005 Warning Stefan Rittstefan.ritt@psi.chRequestLinux2.5.6Re: images attached shown as inline
> the following should do the job:
> 
> <div style="width: 200px">
> <img src="IMG_3133.jpg" style="width: 100%" />
> </div>
> 
> the configurable parameter should be with obviously :-)

Unfortunately not. Please find attached the screen dump from such a try, together with the HTML code.
As you can see, the little elog icon is stretched to the same width as the upper (large) picture.
Attachment 1: scaling.gif
scaling.gif
  932   Sat Feb 12 17:31:46 2005 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.5.6Re: erroneus encoding
> elog sends wrong HTTP headers, charset is empty and not separed from the
> next one "Connection: Keep-Alive ... this bug tells the browser that the
> encoding is "connection:" ... that is wrong.

This has to do with the "%S" vs. "%s" bug described elsewhere in this forum. 
I fixed that. The validator link above now also reports error free.
  933   Sat Feb 12 17:40:55 2005 Reply Stefan Rittstefan.ritt@psi.chBug reportAll2.5.6Re: HTML 4.1 transitional validation fails
I added ths missing tags. The validator at least does not complain any more.
  934   Sat Feb 12 17:45:39 2005 Reply Stefan Rittstefan.ritt@psi.chBug fixAll2.5.6 cvsRe: [patch]: fixed wrong extention check
> current version uses strstr() to check if the file has the expected ascii
> text extension ... this is buggy becouse this way a file named
> ".txt_hidden_file" or "foo.config.dat" are both seen as .txt files.

I added your routine chkext() to the code, but actually use it differently. I
display now ASCII files not by their extension, but the code checks for each file
to contain non-printable characters. If it contains all printable letters, and does
not have the extension PDF, PS or EPS, it's shown inline.
  935   Sat Feb 12 17:48:51 2005 Reply Stefan Rittstefan.ritt@psi.chCommentLinux2.5.6 cvs[patch] Re: images attached shown as inline
Are you sure that this does not stretch small images? Please see elog:931

> two new elog.conf parameters are defined:
> Attached image width          ; width of full view image attached
> Attached image width entry    ; width of attached image in the entry list view

I would rather go with a new class in the CSS file to contain this options, since I 
want to keep the number of options as small as possible.
  936   Sat Feb 12 18:00:48 2005 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.5.6-1Re: MIME encoding of mail?
What you can try is to debug the communication between elogd and the SMTP
server. Just turn on logging via

Logfile = log.txt
Logging level = 3

After sending email, you see the conversation in log.txt. Maybe this gives you
some hints.
  937   Sat Feb 12 20:11:48 2005 Question Stefan Rittstefan.ritt@psi.chQuestionLinux Re: Help with configuration newbie
> 1. When replying to another reply in a thread, the author_name attribute is
> not substitued (as desired). Since this is a mandatory field, we are not
> able to send the reply message. However, reply to the originial message
> works fine.

Preset on reply Author = $long_name

Do not use "Remove on reply".

> 2. "Use Email From = string" prepends an additional "" to the "From"
> field in the e-mails.

This has been fixed recently, please update.

> 3. "Fixed Attributes Reply = Subject" fixes the subject line while replying.
> However when we add "Category" attribute to this list, it breaks.

I tried to use your config file and add

Fixed attributes reply = Subject, Category

and it worked as expected. What kind of "break" did you observe?
  939   Sun Feb 13 16:43:05 2005 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux Re: Help with configuration newbie
> For me, when I put the Category in the fixed attributes for reply, I see the
> Category but when I actually try to send the message - it says Category not
> entered. I am sure I am doing something very stupid. Please help.

No, it was a bug, which I could reproduce now. I fixed it in revision 1.554. It will
be contained in the next release.
ELOG V3.1.5-3fb85fa6