Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 221 of 796  Not logged in ELOG logo
ID Date Icondown Author Author Email Category OS ELOG Version Subject
  65769   Thu Mar 6 14:12:28 2008 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.7.3Re: German language

Salvatore wrote:

Wen es interessiert:

der Eintrag "eloglang = german" gehoert in das Verzeichnis "usr/lib/elog/resources". Dort wird er von elogd ausgelesen.

 

Wie bitte ist der dorhin gekommen? Normalerweise wird elogd.cfg unter /usr/local/elog gespeichert. Wenn man natuerlich diese Datei von Hand irgendwo andershin kopiert, muss man sie auch dort veraendern, sonst schiesst man sich selbst in's Bein.

  65770   Thu Mar 6 15:06:35 2008 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.7.3-2058Re: Quick filter by ID
> Hi,
> 
> I've just upgraded from 2.6.2 to 2.7.3.
> 
> In my config file, I have
> 
> Quick filter: Date, ID.
> 
> When starting 2.7.3, across the top I now get 
> 
> "Error: Attribute "ID" for quick filter not found"
> followed by an entry box.
> 
> If an ID is typed into that box, it sort of finds the right entry (+/- a few on occasion).
> 
> I cannot see any documented change that would affect how the Quick filter works.  Any clues?  Thanks.

Actually it is nowhere written the 'ID' for a quick filter should work. After investigating, I realize that it
worked previously "by accident". I added in meantime some test so there is a warning for quick filter attributes
which do not exist, and that's what you got. I loosened this test for 'ID' now in the current SVN version, so it
can be used. It does however not display the single entry you want, but a page containing that entry (which then
is displayed in bold). If you want exactly one entry, just add it's ID to the URL, like

https://midas.psi.ch/elogs/Forum/65767

for your previous entry.
  65772   Fri Mar 7 08:01:44 2008 Reply Stefan Rittstefan.ritt@psi.chRequestLinux | All2.7.3Re: #include statements and attachment visibility

Yoshio Imai wrote:
However, it does not seem to work in list mode (with attach=1 option): elog still shows all the lines of attached text files there.

I also noticed that the images referenced inline are also shown in the attachment list in list mode, although this post gave me the impression that in list mode, too, inline images should only be displayed inside the elog entry and not in addition as attachment.


I fixed both issues in revision #2072.
  65776   Fri Mar 7 14:09:40 2008 Reply Bill Whitingtextux@bellsouth.netQuestionLinux2.7Re: email subject

Bill Whiting wrote:

Can I control the content of the Subject on an email notification?

i.e. Can I copy the subject from the elog entry into the email subject?

 

Thanks,

//Bill

I found the answer in the docs.

In the config file add

Use Email Subject = Added Text: $subject

This results in the e-mail subject being set to "Added Text: elogentry subject line"

Thanks for a great tool!

  65777   Fri Mar 7 14:29:00 2008 Reply Stefan Rittstefan.ritt@psi.chInfoWindowsELOG V2.7.Re: Message ID and trouble ticketing system

Stefan Ritt wrote:

Richard Ecclestone wrote:

 

I tried the 'Preset ticket = TCK-#####' method to create unique numbers for our application. This worked very nicely until we replied to a earlier message, if we then create a new message the system creates a sequential number after the last message number we replied to. For example if we have 10 messages. If someone replies to message number #2 then when a new record is created it is then assigned number #3 not #11, thus making a duplicate entry for #3.

 Any ideas?


Yes. If you want this feature to work also for replies, you have to put following into your config file:

Preset ticket = TCK-#####
Preset on reply ticket = TCK-#####

When I was browsing this forum about my previous problem, I found 
this thread. A ticket number that applies to all entries in a 
thread, but is unique to that thread.

But I have the same problem as Richard Ecclestone reported, and the
"Preset on reply ticket" line from your reply has not had any effect.

It appears that on starting a new thread (which is to have that
ticket number), the ticket number is just incremented by one from
that of the previous (as in previous ID number) entry.  This is
fine if each thread is completed before a new one started, but if
there are more than one active thread, which can be progressed
further in any order, new threads are likely to be issued with a
ticket number which has already been issued (see Richards's example).

An alternative source of unique numbers would be the Entry number (as
in "696 Entries", top right of the midas.psi.ch/elogs/Forum page),
which would be the seed for the ticket number on new entry.  Not sure
of the syntax for that, or for the replies to have *that* number for
the config file.  I know there is a problem if you move a number of
threads away, but the only alternative (that I can think of) is to
store the seed number somewhere, and increment it every time a new
thread is started.

Or have I got something wrong here? 
Thanks.

Regards,

David.

  65778   Fri Mar 7 14:45:02 2008 Reply Stefan Rittstefan.ritt@psi.chInfoWindowsELOG V2.7.Re: Message ID and trouble ticketing system

David wrote:

When I was browsing this forum about my previous problem, I found this thread. A ticket number that applies to all entries in a thread, but is unique to that thread. But I have the same problem as Richard Ecclestone reported, and the "Preset on reply ticket" line from your reply has not had any effect. It appears that on starting a new thread (which is to have that ticket number), the ticket number is just incremented by one from that of the previous (as in previous ID number) entry. This is fine if each thread is completed before a new one started, but if there are more than one active thread, which can be progressed further in any order, new threads are likely to be issued with a ticket number which has already been issued (see Richards's example).

An alternative source of unique numbers would be the Entry number (as in "696 Entries", top right of the midas.psi.ch/elogs/Forum page), which would be the seed for the ticket number on new entry. Not sure of the syntax for that, or for the replies to have *that* number for the config file. I know there is a problem if you move a number of threads away, but the only alternative (that I can think of) is to store the seed number somewhere, and increment it every time a new thread is started.

Or have I got something wrong here? Thanks. Regards, David.

I cannot reproduce your problem. Assume we have following config file:

[demo]
Theme = default
Attributes = Ticket, Author, Subject
Preset Ticket = TCK-####

The the first entry gets TCK-0001. Any reply to that stays with TCK-0001. Then I do another "new" entry, which gets TCK-0002. Even if I then do another reply to the first thread, that will just stay with TCK-0001. So avoid using 'Preset on reply Ticket". The post from Richard was different, he wanted a new number also for replies (if I understand correctly).

  65779   Fri Mar 7 20:42:39 2008 Reply Stefan Rittstefan.ritt@psi.chInfoWindowsELOG V2.7.Re: Message ID and trouble ticketing system

Ok, now I got the point, also Richard had the same problem. Assume we have 10 threads, and thus ticket numbers 1-10. Now we get a reply to #2, which then pops up to the top of the list. A new message increments the top entry of all entries, and then wrongly gives a new #3, instead of #11.

I fixed this in SVN revision 2073, where elogd searches all logbook entries for the largest index, then increments this one by one. The fix will be contained in the next release.

  65783   Mon Mar 10 15:19:06 2008 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows2.7.3Re: still having email problems

The transcript below looks all ok to me, so it's most likely that the email went to your Spam folder.

mike cianci wrote:

I no longer get an error message when I try to send an email (I get the "email sent" message) but the email never arrives.

Thank you (in advance) for any help.

My elog.log looks like:

10-Mar-2008 07:05:31 [127.0.0.1] {Centaur} NEW entry #0
10-Mar-2008 07:05:31 [127.0.0.1] {Centaur} Email from ELog@desktoppc to mike2.cianci@comcast.net, SMTP host desktoppc
10-Mar-2008 07:05:31 [127.0.0.1] {Centaur} 220 smtp.comcast.net Microsoft ESMTP MAIL Service, Version: 6.0.2600.2180 ready at  Mon, 10 Mar 2008 07:05:31 -0800
10-Mar-2008 07:05:32 [127.0.0.1] {Centaur}
10-Mar-2008 07:05:32 [127.0.0.1] {Centaur} HELO desktoppc
10-Mar-2008 07:05:32 [127.0.0.1] {Centaur} 250 smtp.comcast.net Hello [192.168.1.101]
10-Mar-2008 07:05:32 [127.0.0.1] {Centaur} MAIL FROM: ELog@desktoppc
10-Mar-2008 07:05:32 [127.0.0.1] {Centaur} 250 2.1.0 ELog@desktoppc....Sender OK
10-Mar-2008 07:05:32 [127.0.0.1] {Centaur} RCPT TO: <mike2.cianci@comcast.net>
10-Mar-2008 07:05:32 [127.0.0.1] {Centaur} 250 2.1.5 mike2.cianci@comcast.net
10-Mar-2008 07:05:32 [127.0.0.1] {Centaur} DATA
10-Mar-2008 07:05:32 [127.0.0.1] {Centaur} 354 Start mail input; end with <CRLF>.<CRLF>
10-Mar-2008 07:05:32 [127.0.0.1] {Centaur} Date: Mon, 10 Mar 2008 07:05:31 -0800
To: mike2.cianci@comcast.net
From: ELog <ELog@desktoppc>
User-Agent: Elog Version 2.7.3
Subject: New ELOG entry
Message-ID: <Centaur-23@desktoppc>
X-Elog-URL: http://localhost:8080/Centaur/23
X-Elog-submit-type: web|elog
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html><head>
<META NAME="ROBOTS" CONTENT="NOINDEX, NOFOLLOW">
<title>ELOG - Test</title>
<link rel="stylesheet" type="text/css" href="http://localhost:8080/Centaur/default.css">
<link rel="shortcut icon" href="favicon.ico" />
<link rel="icon" href="favicon.png" type="image/png" />
</head>
<body>
<table class="frame" cellpadding="0" cellspacing="0">
<tr><td><table class="listframe" width="100%" cellspacing="0" cellpadding="0">
<tr><td class="title1">
A new ELOG entry has been submitted:</td></tr>
<tr><td class="attribhead">
<input type=hidden name="Author" value="mike">
<input type=hidden name="Instrument" value="Ginger">
<input type=hidden name="Category" value="Problem">
<input type=hidden name="Test" value="General">
<input type=hidden name="Subject" value="Test">
<input type=hidden name=browsing value=1>
Logbook:&nbsp;<b>Centaur</b>&nbsp;&nbsp;Message ID:&nbsp;<a href="http://localhost:8080/Centaur/23"><b>23</b></a>&nbsp;&nbsp;&nbsp;&nbsp;Entry time:&nbsp;<b>03/10/08 07:05:31</b>
</td></tr>
<tr><td><table width="100%" cellpadding="0" cellspacing="0"><tr><td nowrap class="attribname">Author:</td><td class="attribvalue">
mike&nbsp;</td>
</tr><tr><td nowrap class="attribname">Instrument:</td><td class="attribvalue">
Ginger&nbsp;</td>
</tr><tr><td nowrap class="attribname">Category:</td><td class="attribvalue">
Problem&nbsp;</td>
</tr><tr><td nowrap class="attribname">Test:</td><td class="attribvalue">
General&nbsp;</td>
</tr><tr><td nowrap class="attribname">Subject:</td><td class="attribvalue">
Test&nbsp;</td>
</tr></table></td></tr>
</table><!-- listframe -->
</td></tr>
<tr><td class="messageframe"><p>This is a Test</p></td></tr>

</table><!-- show_standard_title -->
<center><a class="bottomlink" title="Goto ELOG home page" href="https://midas.psi.ch/elog/">ELOG V2.7.3-2058</a></center></body></html>

.
10-Mar-2008 07:05:32 [127.0.0.1] {Centaur} 250 2.6.0  <Centaur-23@desktoppc> Queued mail for delivery
10-Mar-2008 07:05:32 [127.0.0.1] {Centaur} QUIT
10-Mar-2008 07:05:32 [127.0.0.1] {Centaur} 221 2.0.0 smtp.comcast.net Service closing transmission channel

ELOG V3.1.5-2eba886