ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
67282
|
Wed May 16 21:05:11 2012 |
| NOCinator | tgeis01@gmail.com | Question | Windows | 2.9.0 | ELOG 'Dashboard' |
First, I really appreciate this software. Thank you.
Next, I have question - am wanting to have a 'dashboard' of sorts that shows all entries that are 'open'. That part is easy enough. But, then I want to color the time (or some other field) if the ELOG has not been updated/created for more than X hours. This will help us keep track of events that need status updates.
Doable?
Thanks! |
67283
|
Fri May 18 13:10:59 2012 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.9.0 | Re: ELOG 'Dashboard' |
NOCinator wrote: |
First, I really appreciate this software. Thank you.
Next, I have question - am wanting to have a 'dashboard' of sorts that shows all entries that are 'open'. That part is easy enough. But, then I want to color the time (or some other field) if the ELOG has not been updated/created for more than X hours. This will help us keep track of events that need status updates.
Doable?
Thanks!
|
Unfortunately not. What I would do is to define a quick filter, so with one click all 'open' entries are shown. Then you can look at the date column and see how long they have been open (actually when they have been submitted, so the difference you must calculate in your head!). |
67285
|
Wed May 23 05:29:35 2012 |
| Tim Thiel | tt2005@thieleng.com | Question | All | 2.9.0 | How does SVN info get placed in source? |
In the elogd.c file nearly at the very top is the following line:
char svn_revision[] = "$Id: elogd.c 2411 2011-04-01 14:39:35Z ritt $";
How does this information get into the source file? Is it a script used when the svn changes are committed, or perhaps when they are checked out? Any details or pointers to info on the web would be greatly appreciated.
Thanks.
|
67286
|
Thu May 31 11:40:15 2012 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | All | 2.9.0 | Re: How does SVN info get placed in source? |
Tim Thiel wrote: |
In the elogd.c file nearly at the very top is the following line:
char svn_revision[] = "$Id: elogd.c 2411 2011-04-01 14:39:35Z ritt $";
How does this information get into the source file? Is it a script used when the svn changes are committed, or perhaps when they are checked out? Any details or pointers to info on the web would be greatly appreciated.
|
This gets handled automatically by SVN. All you have to do is to put an "$Id$" in your text somewhere and enable the keyword ID. See for example
http://svnbook.red-bean.com/en/1.4/svn.advanced.props.special.keywords.html |
67407
|
Thu Dec 20 17:08:51 2012 |
| Devin Bougie | devin.bougie@cornell.edu | Question | Linux | 2.9.0 | number of attachments limit |
Hello,
Is there still a limit of 50 attachments per topic? If so, is there or could there be a parameter to change this setting?
Thanks,
Devin |
67416
|
Mon Jan 7 16:46:54 2013 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.9.0 | Re: number of attachments limit |
Devin Bougie wrote: |
Hello,
Is there still a limit of 50 attachments per topic? If so, is there or could there be a parameter to change this setting?
Thanks,
Devin
|
The limit is defined in elogd.h:
#define MAX_ATTACHMENTS 50
I never thought that someone wants to have more than 50 attachments, since it will take forever to upload them. You can change the value on your own risk and recompile elogd. At some point you will run out of stack space, in which case elogd will crash, but you could increase the heap memory with a linker option. Just google for it.
Best,
Stefan
|
67723
|
Mon Nov 24 18:29:34 2014 |
| harish amin | harish.amin@holiday.co.om | Bug report | Windows | 2.9. | Error report while submitting the entry |
Dear Stefan,
I am having a log book with the 5 logbooks. All other books are working fine except only one, every time while submitting the entry I am getting a error message.
I have attached the screen shot along with the error log file.
Please help me in solving this bug.
Regards
Harish Amin |
Attachment 1: Elog_error.JPG
|
|
Attachment 2: error.txt
|
24-Nov-2014 21:17:01 [harish@127.0.0.1] {ADVERSE EVENT FORM} NEW entry #0
24-Nov-2014 21:17:01 [harish@127.0.0.1] {ADVERSE EVENT FORM} Email from <harish.amin@holiday.co.om> to harish_jamin@yahoo.com,harish.amin@holiday.co.om, SMTP host smtp.omantel.net.om
24-Nov-2014 21:17:02 [harish@127.0.0.1] {ADVERSE EVENT FORM} 220 fmgw1.omantel.net.om ESMTP Smtpd; Mon, 24 Nov 2014 21:15:09 +0400
24-Nov-2014 21:17:02 [harish@127.0.0.1] {ADVERSE EVENT FORM}
24-Nov-2014 21:17:02 [harish@127.0.0.1] {ADVERSE EVENT FORM} EHLO localhost
24-Nov-2014 21:17:02 [harish@127.0.0.1] {ADVERSE EVENT FORM} 250-fmgw1.omantel.net.om Hello [188.66.222.72], pleased to meet you
24-Nov-2014 21:17:02 [harish@127.0.0.1] {ADVERSE EVENT FORM} 250-ENHANCEDSTATUSCODES
24-Nov-2014 21:17:02 [harish@127.0.0.1] {ADVERSE EVENT FORM} 250-PIPELINING
24-Nov-2014 21:17:02 [harish@127.0.0.1] {ADVERSE EVENT FORM} 250-8BITMIME
24-Nov-2014 21:17:02 [harish@127.0.0.1] {ADVERSE EVENT FORM} 250-SIZE 32235520
24-Nov-2014 21:17:02 [harish@127.0.0.1] {ADVERSE EVENT FORM} 250-DSN
24-Nov-2014 21:17:02 [harish@127.0.0.1] {ADVERSE EVENT FORM} 250-AUTH LOGIN PLAIN
24-Nov-2014 21:17:02 [harish@127.0.0.1] {ADVERSE EVENT FORM} 250-STARTTLS
24-Nov-2014 21:17:02 [harish@127.0.0.1] {ADVERSE EVENT FORM} 250-DELIVERBY
24-Nov-2014 21:17:02 [harish@127.0.0.1] {ADVERSE EVENT FORM} 250 HELP
24-Nov-2014 21:17:02 [harish@127.0.0.1] {ADVERSE EVENT FORM} AUTH LOGIN
24-Nov-2014 21:17:02 [harish@127.0.0.1] {ADVERSE EVENT FORM} Username
24-Nov-2014 21:17:02 [harish@127.0.0.1] {ADVERSE EVENT FORM} harish.amin@holiday.co.om
24-Nov-2014 21:17:03 [harish@127.0.0.1] {ADVERSE EVENT FORM} Password
24-Nov-2014 21:17:03 [harish@127.0.0.1] {ADVERSE EVENT FORM} ****
24-Nov-2014 21:17:03 [harish@127.0.0.1] {ADVERSE EVENT FORM} 235 2.0.0 OK Authenticated
24-Nov-2014 21:17:03 [harish@127.0.0.1] {ADVERSE EVENT FORM} MAIL FROM: <harish.amin@holiday.co.om>
24-Nov-2014 21:17:03 [harish@127.0.0.1] {ADVERSE EVENT FORM} 250 2.1.0 <harish.amin@holiday.co.om>... Sender ok
24-Nov-2014 21:17:03 [harish@127.0.0.1] {ADVERSE EVENT FORM} RCPT TO: <harish_jamin@yahoo.com>
24-Nov-2014 21:17:04 [harish@127.0.0.1] {ADVERSE EVENT FORM} 250 2.1.5 <harish_jamin@yahoo.com>... Recipient ok
24-Nov-2014 21:17:04 [harish@127.0.0.1] {ADVERSE EVENT FORM} RCPT TO: <harish.amin@holiday.co.om>
24-Nov-2014 21:17:04 [harish@127.0.0.1] {ADVERSE EVENT FORM} 250 2.1.5 <harish.amin@holiday.co.om>... Recipient ok
24-Nov-2014 21:17:04 [harish@127.0.0.1] {ADVERSE EVENT FORM} DATA
24-Nov-2014 21:17:04 [harish@127.0.0.1] {ADVERSE EVENT FORM} 354 Enter mail, end with "." on a line by itself
24-Nov-2014 21:17:04 [harish@127.0.0.1] {ADVERSE EVENT FORM} Date: Mon, 24 Nov 2014 21:17:01 +0400
To: harish_jamin@yahoo.com,
"Harish" <harish.amin@holiday.co.om>
From: Harish <harish.amin@holiday.co.om>
User-Agent: Elog Version 2.9.2
MIME-Version: 1.0
Subject: New ELOG entry
Message-ID: <ADVERSE+EVENT+FORM-1@holiday.co.om>
X-Elog-URL: http://localhost:8080/ADVERSE+EVENT+FORM/1
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>
<title></title>
</head>
<body>
<h3>
A new entry has been submitted on localhost:</h3>
<table border="3" cellpadding="4">
<tr><td bgcolor="#CCCCFF">Logbook</td><td bgcolor="#DDEEBB">ADVERSE EVENT FORM</td></tr>
<tr><td bgcolor="#CCCCFF">SUBJECT INITIALS</td><td bgcolor="#DDEEBB"></td></tr>
<tr><td bgcolor="#CCCCFF">SUBJECT ID</td><td bgcolor="#DDEEBB"></td></tr>
<tr><td bgcolor="#CCCCFF">ADVERSE EVENT FORM-1</td><td bgcolor="#DDEEBB"></td></tr>
<tr><td bgcolor="#CCCCFF">Adverse Event Description</td><td bgcolor="#DDEEBB"></td></tr>
<tr><td bgcolor="#CCCCFF">Date of Onset</td><td bgcolor="#DDEEBB"></td></tr>
<tr><td bgcolor="#CCCCFF">Time of Onset</td><td bgcolor="#DDEEBB"></td></tr>
<tr><td bgcolor="#CCCCFF">Frequency of Episode</td><td bgcolor="#DDEEBB"></td></tr>
<tr><td bgcolor="#CCCCFF">Was treatment given for AE</td><td bgcolor="#DDEEBB"></td></tr>
<tr><td bgcolor="#CCCCFF">If Yes</td><td bgcolor="#DDEEBB"></td></tr>
<tr><td bgcolor="#CCCCFF">any follow up visit required</td><td bgcolor="#DDEEBB"></td></tr>
<tr><td bgcolor="#CCCCFF">Follow up date</td><td bgcolor="#DDEEBB"></td></tr>
<tr><td bgcolor="#CCCCFF">Comments</td><td bgcolor="#DDEEBB"></td></tr>
<tr><td bgcolor="#CCCCFF">ADVERSE EVENT FORM-2</td><td bgcolor="#DDEEBB"></td></tr>
<tr><td bgcolor="#CCCCFF">Adverse Event Description</td><td bgcolor="#DDEEBB"></td></tr>
<tr><td bgcolor="#CCCCFF">Date of Onset</td><td bgcolor="#DDEEBB"></td></tr>
<tr><td bgcolor="#CCCCFF">Time of Onset</td><td bgcolor="#DDEEBB"></td></tr>
<tr><td bgcolor="#CCCCFF">Frequency of Episode</td><td bgcolor="#DDEEBB"></td></tr>
<tr><td bgcolor="#CCCCFF">Was treatment given for AE</td><td bgcolor="#DDEEBB"></td></tr>
<tr><td bgcolor="#CCCCFF">If Yes</td><td bgcolor="#DDEEBB"></td></tr>
<tr><td bgcolor="#CCCCFF">any follow up visit required</td><td bgcolor="#DDEEBB"></td></tr>
<tr><td bgcolor="#CCCCFF">Follow up date</td><td bgcolor="#DDEEBB"></td></tr>
<tr><td bgcolor="#CCCCFF">Comments</td><td bgcolor="#DDEEBB"></td></tr>
<tr><td bgcolor="#CCCCFF">Logbook URL</td><td bgcolor="#DDEEBB"><a href="http://localhost:8080/ADVERSE+EVENT+FORM/1">http://localhost:8080/ADVERSE+EVENT+FORM/1</a></td></tr>
</table>
</html></body>
.
24-Nov-2014 21:17:05 [harish@127.0.0.1] {ADVERSE EVENT FORM} 250 2.0.0 sAOHF99g021280-sAOHF99h021280 Message accepted for delivery
24-Nov-2014 21:17:05 [harish@127.0.0.1] {ADVERSE EVENT FORM} QUIT
24-Nov-2014 21:17:05 [harish@127.0.0.1] {ADVERSE EVENT FORM} 221 2.0.0 fmgw1.omantel.net.om closing connection
24-Nov-2014 21:17:53 [harish@127.0.0.1] {ENROLLMENT VISIT} NEW entry #0
|
67724
|
Tue Nov 25 12:36:47 2014 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Windows | 2.9. | Re: Error report while submitting the entry |
harish amin wrote: |
Dear Stefan,
I am having a log book with the 5 logbooks. All other books are working fine except only one, every time while submitting the entry I am getting a error message.
I have attached the screen shot along with the error log file.
Please help me in solving this bug.
Regards
Harish Amin
|
It's hard to guess from the information you sent what is wrong. The program just crashes, after the email notification has been sent successfully. Can you check if the one logbook which is not working is using some path for the logbook directory which it cannot write to due to access limitations? Just a guess.
-Stefan |