Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 229 of 796  Not logged in ELOG logo
IDup Date Icon Author Author Email Category OS ELOG Version Subject
  1878   Fri Jul 14 20:29:21 2006 Agree Elaine Cristina Franchini dos Anjoselaine@ccuec.unicamp.brCommentLinux2.6.1-1681Re: Inserting images via Internet Explorer

Stefan Ritt wrote:

Elaine Cristina Franchini dos Anjos wrote:
I observed that there is a difference between IE and others browsers.
When I use "insert image" button in Netscape, for instance,
it creates automatically a tag like
[IMG]elog:1/1[/IMG]
and
includes an attachment in the ELOG entry.

When a try to do the same action in Internet Explorer, only
the attachment is created without the tag
[IMG]elog:1/1[/IMG]
.


This is a problem of the JavaScript implementation of Internet Explorer. After some externsive research I found now a way to convince IE to do the right thing. The fix is contains in SVN revision 1701 and will be released with 2.6.2-2 soon.



Great job !
I tried the SVN revision 1701, and it works perfectly.
Thank you for all your effort.

Regards,

Elaine
  1879   Fri Jul 14 21:47:14 2006 Entry Elaine Cristina Franchini dos Anjoselaine@ccuec.unicamp.brBug reportLinux2.6.2-1702astonished icon
Hi Stefan,

I've been trying to use the astonished icon, but the preview or entry
display shows only a broken image.

I found in the elogd.c at line 5556 :
{"8o", "<img src=\"%sicons/eek.png\">"}

I copied the "astonished.png" to "eek.png" and it worked.

Is it the reason of the problem ? ?)

Thanks a lot.

Regards,
Elaine
  1880   Sat Jul 15 17:58:46 2006 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.6.2-1702Re: astonished icon

Elaine Cristina Franchini dos Anjos wrote:
Hi Stefan,

I've been trying to use the astonished icon, but the preview or entry
display shows only a broken image.

I found in the elogd.c at line 5556 :
{"8o", "<img src=\"%sicons/eek.png\">"}

I copied the "astonished.png" to "eek.png" and it worked.

Is it the reason of the problem ? ?)


Actually the C code should be "astonished.png" instead of "eek.png". I changed that in revision 1704. BTW, thanks for the Brazilian translation. Astonished
  1881   Mon Jul 17 13:20:07 2006 Reply Gerald Ebberinkg.h.p.ebberink@nclr.nlQuestionLinux2.6.1Re: restrict access

Stefan Ritt wrote:

Gerald Ebberink wrote:
As you can see, I have implemented a temporary fix in the way of allowing only certain hosts access. But where does this Internal error come from.


I only can identify this error if you send me your current ("de-sensified") elogd.cfg.


I have just installed the svn version of elog, and the problem has been fixed.

Thank you very much!
  1882   Mon Jul 17 13:44:37 2006 Question Gerald Ebberinkg.h.p.ebberink@nclr.nlCommentLinux2.6.2-1706Duplicate of a reply should be a reply
Hello everybody

This weekend I found that if I duplicate a reply it does not become a reply it self.
Is this on purpouse?
I have been through the source a little (not much time for that) and I can not find a reason where the "in reply to" value is dropped.

Could anyone give me an pointer?
  1883   Mon Jul 17 13:49:37 2006 Reply Stefan Rittstefan.ritt@psi.chCommentLinux2.6.2-1706Re: Duplicate of a reply should be a reply

Gerald Ebberink wrote:
Hello everybody

This weekend I found that if I duplicate a reply it does not become a reply it self.
Is this on purpouse?
I have been through the source a little (not much time for that) and I can not find a reason where the "in reply to" value is dropped.

Could anyone give me an pointer?


This is on purpuse. The Duplicate functionality is ment to "clone" an existing entry, to save some typing work if an existing entry contains most of what one wants in a new entry. If one duplicates a reply, it is detached from the original thread, so there is not entry to attach the duplicate to. I guess you want to make a new reply to an existing entry, and then have another existing reply as a template for that, but this is not possible. If I would not drop the "in reply to" value, the duplicate would point to the wrong entry.
  1884   Wed Jul 19 12:20:34 2006 Question Dimitrios Tsirigkasdimitrios.tsirigkas@cern.chQuestionLinux Use Email From = <string>
Hi all,

My users have complained about the multiple "I'm away from xxx until xxx" automated replies that they get when they post an entry and notifications are sent with their email in the "From" field. I would therefore like to always use the address specified in the Use Email From line of the configuration file and never the user's address. Reading from the documentation:

The option Use Email From = <string> is used for the "From:" field in the email. Since more and more email servers do not accept invalid "From:" addresses in order to reduce spam mail, it might be important that a "real" email address is used in the "From:" field. By default, the email address of the currently logged in user is used for the "From:" field. If no user is logged in, or the current user has not specified a email address in the password database, the setting of the option Use Email From is used for the "From:" field.

Is there a way to override that default and always use the setting of the option Use Email From?

Thanks,
Dimitris
  1885   Wed Jul 19 12:35:16 2006 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux Re: Use Email From = <string>

Dimitrios Tsirigkas wrote:
My users have complained about the multiple "I'm away from xxx until xxx" automated replies that they get when they post an entry and notifications are sent with their email in the "From" field.


Yes, I had the same problem with this forum.


Dimitrios Tsirigkas wrote:
Is there a way to override that default and always use the setting of the option Use Email From?


Sure. You override the default by setting the Use Email From. In the forum I set it now to Use Email From = noreply@psi.ch which is a nonexisting address. While now this is ok, our former email server did not accept this because the user noreply does not exist at our institute. So you have to figure out if this works at CERN.
ELOG V3.1.5-2eba886