| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
1840
|
Thu May 25 19:41:51 2006 |
 | Mark Bergman | mark.bergman@uphs.upenn.edu | Request | Linux | 2.6.1 | add field type to automatically email CC | I've got logbooks where I'm submitting entries on behalf of other users, or where other people should be notified of the ticket. This isn't a fixed list of people, and shouldn't be hard-coded into a config file. I've got a field to enter the user's e-mail address, but there's no action associated with that data.
I'd like to see a new field type that allows the entry of e-mail addresses, where each addresses supplied with the logfile entry would be automatically "CC'ed" in the notification e-mail. Ideally, people on the CC list would be (optionally) CC'ed when there are replies or edits to the original elog entry.
For example (snippet of fictional elogd.cfg):
-------------------------------
[web site]
Welcome Title = Issues regarding the web site
MOptions Category = Add links, Change content, Broken Link, Other
CCMailTo = Notification List
Attributes = Author, Category, Severity, Subject, Entry ID, Status, User, Login
Extendable Attributes = Category, Severity, Subject, Status, User, Login, Notification List
Required Attributes = Category, Subject, Status, User
------------------------------- |
|
2236
|
Thu May 31 23:33:28 2007 |
 | Mark Bergman | mark.bergman@uphs.upenn.edu | Question | Linux | V2.6.5-186 | how to supress checkboxes of all logbooks at registration? | Is there a way to suppress the listing of all logbooks on the New User Registration page? We've got 100 logbooks (one for each server, cluster node, or major software package). The long list makes it difficult for users to find the bottom of the registration page, and no user needs to subscribe for automatic e-mail notification for every logbook.
Thanks,
Mark |
|
2237
|
Thu May 31 23:46:31 2007 |
| Mark Bergman | mark.bergman@uphs.upenn.edu | Question | Linux | V2.6.5 | config settings to ensure replies to author, thread contributors, admin? | I'm having some difficulty configuring elog to ensure that the original author of an entry, any contributors to the thread, and a desginated administrator get e-mail notification for any change to the thread.
Here's a subset of the current elogd.cfg:
Attributes = Author, Type, Category, Severity, Subject, Entry ID, Status, CC E-mail To
Display Email recipients = 1
Email All = $CC E-mail To
Email All = mark.bergman@uphs.upenn.edu
Email Format = 47
Suppress default = 0
Type CC E-mail To = museremail
The "Suppress default = 0" setting is used because many people mistakenly subscribe for automatic e-mail notification of all our logbooks when they self-register. I was hoping that the "Email All" directives would override the suppression of default mail.
This configuration works partially...in that if a user specifically selects addresses in the "CC E-mail To" field, those people do get mail.
The documentation states that there can be multiple "Email All" directives, so I thought they would be additive--causing the admin address and the author to always get mail.
Is there a setting to ensure that the original author of the thread is always notified upon any change?
Thanks,
Mark |
|
66898
|
Tue Sep 14 01:15:22 2010 |
 | Mark Bergman | mark.bergman@uphs.upenn.edu | Bug report | Linux | 2.8.0 | elog 2.8.0 as daemon crashes when editing selected threaded list | I recently upgraded elog from 2.7.8 to 2.8.0 (and moved servers, removed unused logbooks, etc.). I'm now having a problem where elog consistently crashes when attempting to edit multiple entries. This is a very common use case, as we use a "status" field, set to "open" or "closed" to track problems. When a problem is resolved, we will go to the "list" display, set it to "threaded", "select" the thread, and then edit it, to change the status field for all posts in the thread to "closed".
Now, as soon as the "edit" button is clicked, elog crashes. This happens on every thread and logbook that I've tried. The elog logfile itself doesn't show anything useful.
However, if eLog is run with "-v" in place of "-D", it does not crash.
Environment:
CentOS 5.4
eLog 2.8.0 built Aug 5 2010, 12:24:11
|
|
67052
|
Thu Apr 21 21:06:20 2011 |
| Mark Bergman | mark.bergman@uphs.upenn.edu | Bug report | Linux | 2.9.0 | Re: elog 2.8.0 as daemon crashes when editing selected threaded list |
| Mark Bergman wrote: |
|
I recently upgraded elog from 2.7.8 to 2.8.0 (and moved servers, removed unused logbooks, etc.). I'm now having a problem where elog consistently crashes when attempting to edit multiple entries. This is a very common use case, as we use a "status" field, set to "open" or "closed" to track problems. When a problem is resolved, we will go to the "list" display, set it to "threaded", "select" the thread, and then edit it, to change the status field for all posts in the thread to "closed".
Now, as soon as the "edit" button is clicked, elog crashes. This happens on every thread and logbook that I've tried. The elog logfile itself doesn't show anything useful.
However, if eLog is run with "-v" in place of "-D", it does not crash.
Environment:
CentOS 5.4
eLog 2.8.0 built Aug 5 2010, 12:24:11
|
I'm now running eLog 2.9.0 and seeing the same crashes. However, I've got some more information that may be helpful.
The crash seems to be directly related to the order of replies in the thread. For example, in this thread I am replying to the original entry. The original entry has 2 children (the entries are siblings) and no grandchildren.
In our installation, eLog crashes consistently under the following conditions:
go to the "list" display
set it to "threaded"
"select" a thread that has siblings at any generation of replies
choose "edit"
If the selected thread only has one entry at any generation, eLog does not crash.
Here's a horrible attempt at a display of two message threads. Note that in the first example, there are 2 replies at the same generation (siblings)--both the person who responded and the original submitter replied to the initial submission. After that, all replies were to successive generations.
-------------- Causes eLog to Crash ------------------
! Full Name (submitter) module failure
=> Full Name (submitter) Re: module failure
=> Full Name (replier) Re: module failure
=> Full Name (submitter) Re: Re: module failure
=> Full Name (submitter) Re: Re: Re: module failue
------------------------------------------------------
-------------- No eLog Problem ------------------
! Full Name (submitter) Labwide failure of mcc
=> Full Name (replier) Re: Labwide failure of mcc
=> Full Name (submitter) Re: Re: Labwide failure of mcc
=> Full Name (replier) Re: Re: Re: Labwide failure of mcc
------------------------------------------------------
|
|
67137
|
Fri Oct 21 01:09:54 2011 |
 | Mark Bergman | mark.bergman@uphs.upenn.edu | Question | Linux | 2.90 | error message "Command Config is not allowed" after registering | After registering, elog displays a page with the message:
Error: Command "Config" is not allowed for user ""
However, the registration is successful. This causes confusion, and results in users registering multiple times.
In the elogd.conf file, I have the directive:
Allow Config = bergman
Any suggestions? |
|
67199
|
Wed Feb 15 17:13:08 2012 |
 | Mark Bergman | mark.bergman@uphs.upenn.edu | Question | Linux | 2.90 | Re: error message "Command Config is not allowed" after registering |
| Mark Bergman wrote: |
|
After registering, elog displays a page with the message:
Error: Command "Config" is not allowed for user ""
However, the registration is successful. This causes confusion, and results in users registering multiple times.
In the elogd.conf file, I have the directive:
Allow Config = bergman
Any suggestions?
|
I loathe the idea of 'bumping' up one's own posting, but here I go...
Has anyone seen this issue, or have any solution? We've got people who register 8 or more times, since they see the "Error" message with each registration. |
|
67200
|
Wed Feb 15 17:17:27 2012 |
| Mark Bergman | mark.bergman@uphs.upenn.edu | Question | Linux | 2.90 | elog entry in email footer? | On our system, elog sends email to all people associated with an entry. Often, people will respond via email, not through elog. I'm in the process of setting up a handler for the inbound email. However, I'd like to have the outbound mail from eLog include a 'footer' to each message the details where to go to respond.
For example, the footer might read:
To respond to this message, please click the following link:
<http://www.example.com/elog/General/6153>
Any suggestions for how to implement that?
|
|