Duplicate entry suggestion, posted by Dennis Seitz on Tue Apr 1 02:04:35 2008
|
We have configured several logbooks to allow users to duplicate an entry in another logbook, which is very useful for entries which apply to more than one category.
However, once the entry is duplicated, subsequent revisions to the original entry are not copied to the duplicate entries.
I can see where implementing that would add a lot of code to ELOG. Rather than do that, would it be possible to add a configuration option to duplicate only the attributes, and place a link to the original entry in the body of the duplicated entry instead of the full text?
Thanks,
Dennis |
Re: Duplicate entry suggestion, posted by Stefan Ritt on Tue Apr 1 08:01:02 2008
|
Dennis Seitz wrote: |
We have configured several logbooks to allow users to duplicate an entry in another logbook, which is very useful for entries which apply to more than one category.
However, once the entry is duplicated, subsequent revisions to the original entry are not copied to the duplicate entries.
I can see where implementing that would add a lot of code to ELOG. Rather than do that, would it be possible to add a configuration option to duplicate only the attributes, and place a link to the original entry in the body of the duplicated entry instead of the full text?
|
I don't know if you are aware, but you can put links to other entries manually into the text. Just enter them in the form elog:65799. You can click on that link which takes you the entry you reference. Unfortunately there is at the moment no automatic way to generate this back link automatically. |
Re: Duplicate entry suggestion, posted by Dennis Seitz on Tue Apr 1 20:31:26 2008
|
Stefan Ritt wrote: |
Dennis Seitz wrote: |
We have configured several logbooks to allow users to duplicate an entry in another logbook, which is very useful for entries which apply to more than one category.
However, once the entry is duplicated, subsequent revisions to the original entry are not copied to the duplicate entries.
I can see where implementing that would add a lot of code to ELOG. Rather than do that, would it be possible to add a configuration option to duplicate only the attributes, and place a link to the original entry in the body of the duplicated entry instead of the full text?
|
I don't know if you are aware, but you can put links to other entries manually into the text. Just enter them in the form elog:65799. You can click on that link which takes you the entry you reference. Unfortunately there is at the moment no automatic way to generate this back link automatically.
|
Thanks, I was not aware of that - usually I have copied and pasted the entire path from my browser.
In any case, can you consider my request for possible future implementation? I think it's a useful function. For now, it's really no big deal to simply copy the url before selecting the Copy To: menu and then replacing the body text with the copied link. But I think it would be more useful to make this happen automatically, so I don't have to ask users to comply voluntarily.
Thank you.
|
change language, posted by svrmarty on Tue Mar 25 14:00:53 2008
|
i've installed the debian package on my system
there's only one config file, /etc/elog.conf
i've tried to change the language, in [global] with Language = german,
then restarting the daemon, but it doesn't work.
please help me, where can i change the default(all) language and which settings should i do.
thx a lot
|
Re: change language, posted by Stefan Ritt on Thu Mar 27 07:52:00 2008
|
svrmarty wrote: |
i've installed the debian package on my system
there's only one config file, /etc/elog.conf
i've tried to change the language, in [global] with Language = german,
then restarting the daemon, but it doesn't work.
please help me, where can i change the default(all) language and which settings should i do.
|
I'm not maintainer of the Debian package, you should direct your question to Recai <roktas@omu.edu.tr> (in principle he should read this forum). If you start elogd manually with the strace command like:
strace -r -o tmp.log -e trace=open /usr/local/elog/elogd
and check in tmp.log from where elogd opens its elogd.cfg. Then change the appropriate elogd.cfg (NOT elog.conf). After you change it, you have to restart elogd. |
Re: change language, posted by svrmarty on Thu Mar 27 09:23:25 2008
|
Stefan Ritt wrote: |
svrmarty wrote: |
i've installed the debian package on my system
there's only one config file, /etc/elog.conf
i've tried to change the language, in [global] with Language = german,
then restarting the daemon, but it doesn't work.
please help me, where can i change the default(all) language and which settings should i do.
|
I'm not maintainer of the Debian package, you should direct your question to Recai <roktas@omu.edu.tr> (in principle he should read this forum). If you start elogd manually with the strace command like:
strace -r -o tmp.log -e trace=open /usr/local/elog/elogd
and check in tmp.log from where elogd opens its elogd.cfg. Then change the appropriate elogd.cfg (NOT elog.conf). After you change it, you have to restart elogd.
|
in the trace is only one config file
0.000103 open("/etc/elog.conf", O_RDONLY) = 3
0.000047 open("/etc/elog.conf", O_RDONLY) = 3 |
Re: change language, posted by svrmarty on Thu Mar 27 09:30:03 2008
|
svrmarty wrote:
|
Stefan Ritt wrote: |
svrmarty wrote: |
i've installed the debian package on my system
there's only one config file, /etc/elog.conf
i've tried to change the language, in [global] with Language = german,
then restarting the daemon, but it doesn't work.
please help me, where can i change the default(all) language and which settings should i do.
|
I'm not maintainer of the Debian package, you should direct your question to Recai <roktas@omu.edu.tr> (in principle he should read this forum). If you start elogd manually with the strace command like:
strace -r -o tmp.log -e trace=open /usr/local/elog/elogd
and check in tmp.log from where elogd opens its elogd.cfg. Then change the appropriate elogd.cfg (NOT elog.conf). After you change it, you have to restart elogd.
|
in the trace is only one config file
0.000103 open("/etc/elog.conf", O_RDONLY) = 3
0.000047 open("/etc/elog.conf", O_RDONLY) = 3
there's a bug in the debian package
0.000033 open("resources/eloglang.german", O_RDONLY) = -1 ENOENT (No such file or directory)
0.000264 open("/usr/share/elog/resources/eloglang.german", O_RDONLY) = -1 ENOENT (No such file or directory)
it's searching for the files in the wrong directory.
i've solved it with
#/usr/share/elog$ ln -s . resources
|
|
how to sort entry, posted by jee on Thu Mar 27 05:58:40 2008
|
hi:
I have a problem with elog, if there are many entrys, and i want to find some useful entries which i preseted before ,like entries with , how can i configure the command ?
so i can find what i want with
please give me a help ,thx a lot! |
Re: how to sort entry, posted by Stefan Ritt on Thu Mar 27 06:18:05 2008
|
jee wrote: |
hi:
I have a problem with elog, if there are many entrys, and i want to find some useful entries which i preseted before ,like entries with , how can i configure the command ?
so i can find what i want with
please give me a help ,thx a lot!
|
Very simple: Click on "Find", select the icon, and click on "Search". Like if you do this for this Forum, it will produce an URL like:
https://midas.psi.ch/elogs/Forum/?Icon=icon14.gif |
Re: how to sort entry, posted by jee on Thu Mar 27 09:05:05 2008
|
Stefan Ritt wrote: |
jee wrote: |
hi:
I have a problem with elog, if there are many entrys, and i want to find some useful entries which i preseted before ,like entries with , how can i configure the command ?
so i can find what i want with
please give me a help ,thx a lot!
|
Very simple: Click on "Find", select the icon, and click on "Search". Like if you do this for this Forum, it will produce an URL like:
https://midas.psi.ch/elogs/Forum/?Icon=icon14.gif
|
i mean , is there a button that when i push it , then it only shows valuable enties which i preset before, the button may add in the "List | New | Edit | Reply | Duplicate | Find | Config | Logout | Help"
is that possible? pls show the command.
thank you for reply me! |
Re: how to sort entry, posted by Stefan Ritt on Thu Mar 27 09:10:46 2008
|
jee wrote: |
i mean , is there a button that when i push it , then it only shows valuable enties which i preset before, the button may add in the "List | New | Edit | Reply | Duplicate | Find | Config | Logout | Help"
is that possible? pls show the command.
thank you for reply me!
|
No, there is no button for that. |
German language, posted by Salvatore on Sat Mar 1 14:47:27 2008
|
In der Config-Datei habe ich den Eintrag "language = german" vorgenommen. Was unter Windows funktioniert, verweigert mir Linux: Die Umstellung des Logs auf Deutsch. Wer kann helfen?
Salvatore |
Re: German language, posted by Stefan Ritt on Sat Mar 1 14:53:16 2008
|
Salvatore wrote: |
In der Config-Datei habe ich den Eintrag "language = german" vorgenommen. Was unter Windows funktioniert, verweigert mir Linux: Die Umstellung des Logs auf Deutsch. Wer kann helfen?
Salvatore
|
Das kann drei Ursachen haben:
1) Die Installation under Linux ist nicht vollstaendig. Die Datei resources/eloglang.german muss vorhanden und von elogd lesbar sein
2) Der linux-daemon braucht ein Neustart nach jeder Aenderung der Sprache
3) Nochmal ueberpruefen, ob der Eintrag "language = german" auch wirklich vorhanden im richtigen config file ist. |
Re: German language, posted by Salvatore on Sat Mar 1 16:47:57 2008
|
Wen es interessiert:
der Eintrag "eloglang = german" gehoert in das Verzeichnis "usr/lib/elog/resources". Dort wird er von elogd ausgelesen.
ZStefan Ritt wrote: |
Salvatore wrote: |
In der Config-Datei habe ich den Eintrag "language = german" vorgenommen. Was unter Windows funktioniert, verweigert mir Linux: Die Umstellung des Logs auf Deutsch. Wer kann helfen?
Salvatore
|
Das kann drei Ursachen haben:
1) Die Installation under Linux ist nicht vollstaendig. Die Datei resources/eloglang.german muss vorhanden und von elogd lesbar sein
2) Der linux-daemon braucht ein Neustart nach jeder Aenderung der Sprache
3) Nochmal ueberpruefen, ob der Eintrag "language = german" auch wirklich vorhanden im richtigen config file ist.
|
|
Re: German language, posted by Stefan Ritt on Thu Mar 6 14:12:28 2008
|
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. |
Re: German language, posted by svrmarty on Thu Mar 20 23:46:42 2008
|
Stefan Ritt wrote: |
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.
|
Wie und wo funktioniert das mit dem debian package ?
hier gibt es nur /etc/elog.conf, egal in welchem teil ich es reinschreibe, groß, klein,
ich habe leider noch immer alles in englisch
|
still having email problems, posted by mike cianci on Mon Mar 10 15:09:56 2008
|
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: <b>Centaur</b> Message ID: <a href="http://localhost:8080/Centaur/23"><b>23</b></a> Entry time: <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 </td>
</tr><tr><td nowrap class="attribname">Instrument:</td><td class="attribvalue">
Ginger </td>
</tr><tr><td nowrap class="attribname">Category:</td><td class="attribvalue">
Problem </td>
</tr><tr><td nowrap class="attribname">Test:</td><td class="attribvalue">
General </td>
</tr><tr><td nowrap class="attribname">Subject:</td><td class="attribvalue">
Test </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 |
Re: still having email problems, posted by Stefan Ritt on Mon Mar 10 15:19:06 2008
|
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: <b>Centaur</b> Message ID: <a href="http://localhost:8080/Centaur/23"><b>23</b></a> Entry time: <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 </td>
</tr><tr><td nowrap class="attribname">Instrument:</td><td class="attribvalue">
Ginger </td>
</tr><tr><td nowrap class="attribname">Category:</td><td class="attribvalue">
Problem </td>
</tr><tr><td nowrap class="attribname">Test:</td><td class="attribvalue">
General </td>
</tr><tr><td nowrap class="attribname">Subject:</td><td class="attribvalue">
Test </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
|
|
Re: still having email problems, posted by mike cianci on Mon Mar 10 17:58:06 2008
|
Stefan Ritt wrote: |
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: <b>Centaur</b> Message ID: <a href="http://localhost:8080/Centaur/23"><b>23</b></a> Entry time: <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 </td>
</tr><tr><td nowrap class="attribname">Instrument:</td><td class="attribvalue">
Ginger </td>
</tr><tr><td nowrap class="attribname">Category:</td><td class="attribvalue">
Problem </td>
</tr><tr><td nowrap class="attribname">Test:</td><td class="attribvalue">
General </td>
</tr><tr><td nowrap class="attribname">Subject:</td><td class="attribvalue">
Test </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
|
|
I checked for a spam filter and found none. I have also tried this on three different computers (with different email accounts) and still no luck. |
Re: still having email problems, posted by An Thai on Mon Mar 10 18:31:58 2008
|
mike cianci wrote: |
Stefan Ritt wrote: |
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: <b>Centaur</b> Message ID: <a href="http://localhost:8080/Centaur/23"><b>23</b></a> Entry time: <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 </td>
</tr><tr><td nowrap class="attribname">Instrument:</td><td class="attribvalue">
Ginger </td>
</tr><tr><td nowrap class="attribname">Category:</td><td class="attribvalue">
Problem </td>
</tr><tr><td nowrap class="attribname">Test:</td><td class="attribvalue">
General </td>
</tr><tr><td nowrap class="attribname">Subject:</td><td class="attribvalue">
Test </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
|
|
I checked for a spam filter and found none. I have also tried this on three different computers (with different email accounts) and still no luck.
|
Please use a valid email address for sender. All free email provider don't accept an invalid address, because of security against Spam problem.
Use Email From = xx@xxx.xx
|
Message ID and trouble ticketing system, posted by lance on Sat Nov 24 03:16:46 2007
|
I am trying to create a trouble ticket system however when you do a reply you get a new message ID. I was hoping to use the message ID as a ticket number and just wanted to use the reply as an append to the orginal message id, however each reply creates a new message id. This would be a nightmare to track and if I closed the ticket I would have to close every log entry related to this.
Does anyone know how to either make the reply and appended reply (appended to the orignal message id) or how to create a field that automatically gives it a new trouble ticket number.
Has anyone configured a trouble ticket system that I could look at to get some ideas?
Thanks,
Lance |
Re: Message ID and trouble ticketing system, posted by Stefan Ritt on Mon Nov 26 14:33:59 2007
|
lance wrote: |
I am trying to create a trouble ticket system however when you do a reply you get a new message ID. I was hoping to use the message ID as a ticket number and just wanted to use the reply as an append to the orginal message id, however each reply creates a new message id. This would be a nightmare to track and if I closed the ticket I would have to close every log entry related to this.
Does anyone know how to either make the reply and appended reply (appended to the orignal message id) or how to create a field that automatically gives it a new trouble ticket number.
Has anyone configured a trouble ticket system that I could look at to get some ideas?
|
First of all, ELOG has been designed having shift logbooks in mind, so it probably will never be a perfect trouble ticket system. Nevertheless, there are some options which can help in that respect:
- Use attributes Ticket and Status
- Preset Ticket with a running ticket number via
Preset ticket = TCK-#####
This will increment the 5-digit ticket number whenever you create a new ticket, but will not update it when you do a reply
-
Use Status to determine the status of the whole trouble ticket chain (initial entry plus replies)
Options Status = open, closed
Preset Status = open
-
Once a ticked chain is closed, do the following:
- Go to the threaded list display
- Click on Select
- Select the trouble ticket chain
- Click on Edit
- Now change Status from "Open" to "Closed"
This will then modify the Status of the whole chain from "Open" to "Closed" |
Re: Message ID and trouble ticketing system, posted by lance on Mon Nov 26 16:58:26 2007
|
Stefan Ritt wrote: |
lance wrote: |
I am trying to create a trouble ticket system however when you do a reply you get a new message ID. I was hoping to use the message ID as a ticket number and just wanted to use the reply as an append to the orginal message id, however each reply creates a new message id. This would be a nightmare to track and if I closed the ticket I would have to close every log entry related to this.
Does anyone know how to either make the reply and appended reply (appended to the orignal message id) or how to create a field that automatically gives it a new trouble ticket number.
Has anyone configured a trouble ticket system that I could look at to get some ideas?
|
First of all, ELOG has been designed having shift logbooks in mind, so it probably will never be a perfect trouble ticket system. Nevertheless, there are some options which can help in that respect:
- Use attributes Ticket and Status
- Preset Ticket with a running ticket number via
Preset ticket = TCK-#####
This will increment the 5-digit ticket number whenever you create a new ticket, but will not update it when you do a reply
-
Use Status to determine the status of the whole trouble ticket chain (initial entry plus replies)
Options Status = open, closed
Preset Status = open
-
Once a ticked chain is closed, do the following:
- Go to the threaded list display
- Click on Select
- Select the trouble ticket chain
- Click on Edit
- Now change Status from "Open" to "Closed"
This will then modify the Status of the whole chain from "Open" to "Closed"
|
Stefan,
Thanks for this, I had already implemented the Preset Ticket Nr = TT-##### but I didnt use the threaded and Select to close the ticket, very nice tip thanks. I think this program can be have several uses, and working very well. The trouble ticketing will work for us.
Once again thanks for the very speedy support.
Lance |
Re: Message ID and trouble ticketing system, posted by Richard Ecclestone on Fri Feb 15 15:46:38 2008
|
lance wrote: |
Stefan Ritt wrote: |
lance wrote: |
I am trying to create a trouble ticket system however when you do a reply you get a new message ID. I was hoping to use the message ID as a ticket number and just wanted to use the reply as an append to the orginal message id, however each reply creates a new message id. This would be a nightmare to track and if I closed the ticket I would have to close every log entry related to this.
Does anyone know how to either make the reply and appended reply (appended to the orignal message id) or how to create a field that automatically gives it a new trouble ticket number.
Has anyone configured a trouble ticket system that I could look at to get some ideas?
|
First of all, ELOG has been designed having shift logbooks in mind, so it probably will never be a perfect trouble ticket system. Nevertheless, there are some options which can help in that respect:
- Use attributes Ticket and Status
- Preset Ticket with a running ticket number via
Preset ticket = TCK-#####
This will increment the 5-digit ticket number whenever you create a new ticket, but will not update it when you do a reply
-
Use Status to determine the status of the whole trouble ticket chain (initial entry plus replies)
Options Status = open, closed
Preset Status = open
-
Once a ticked chain is closed, do the following:
- Go to the threaded list display
- Click on Select
- Select the trouble ticket chain
- Click on Edit
- Now change Status from "Open" to "Closed"
This will then modify the Status of the whole chain from "Open" to "Closed"
|
Stefan,
Thanks for this, I had already implemented the Preset Ticket Nr = TT-##### but I didnt use the threaded and Select to close the ticket, very nice tip thanks. I think this program can be have several uses, and working very well. The trouble ticketing will work for us.
Once again thanks for the very speedy support.
Lance
|
Hi
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?
Cheers Richard |
Re: Message ID and trouble ticketing system, posted by Stefan Ritt on Thu Feb 21 08:04:50 2008
|
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-#####
|
Re: Message ID and trouble ticketing system, posted by Stefan Ritt on Fri Mar 7 14:29:00 2008
|
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.
|
Re: Message ID and trouble ticketing system, posted by Stefan Ritt on Fri Mar 7 14:45:02 2008
|
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). |
Re: Message ID and trouble ticketing system, posted by Stefan Ritt on Fri Mar 7 20:42:39 2008
|
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. |
Re: Message ID and trouble ticketing system, posted by David Pilgram on Fri Mar 7 21:26:18 2008
|
>Stefan Ritt wrote:
>
>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.
----
Great! Thanks Stefan, off to download right now!
Great program, by the way, but don't think you need to be told that yet again! |
Re: Message ID and trouble ticketing system, posted by David Pilgram on Fri Mar 7 21:53:28 2008
|
>>Stefan Ritt wrote:
>>
>>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.
>
>----
>
>Great! Thanks Stefan, off to download right now!
>
>Great program, by the way, but don't think you need to be told that yet again!
---
Oh ho!
I've tried this on an existing database, where most entries do not have a ticket #. The previous entry #
(previous in ID sense) is T00550, say. But when I start a new thread, the ticket # is T00001. Is it being put
out by no entry for ticket # in most of the database?
LATER UPDATE.
On a small database (12 entries, with 45 comments in total), this worked as expected if most or all entries have ticket numbers, even if the previous (by id #) had not had a ticket number. (I had to edit every entry to put in ticket numbers).
The only thing I can think of is the number of entries that don't have a ticket #, or a line in the .log file entry saying "Ticket: " but am looking further into this.
(BTW, am posting this way to get around the proxy server problem I have!) |
email subject, posted by Bill Whiting on Fri Mar 7 13:44:34 2008
|
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 |
Re: email subject, posted by Bill Whiting on Fri Mar 7 14:09:40 2008
|
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! |
Quick filter by ID, posted by David Pilgram on Tue Mar 4 14:03:00 2008
|
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. |
Re: Quick filter by ID, posted by Stefan Ritt on Thu Mar 6 15:06:35 2008
|
> 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. |
Re: Quick filter by ID, posted by David Pilgram on Fri Mar 7 13:12:37 2008
|
> > 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.
Thanks Stefan! |
|