Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 669 of 808  Not logged in ELOG logo
ID Date Icon Author Author Email Category OS ELOG Versiondown Subject
  703   Wed Sep 15 07:42:23 2004 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.5.4Re: too many <table> tags
> > > Couldn't one include the extra <table> tag only when there is really more than
> > > one attribute per line.  All other lines could then be aligned properly.

I added that code in revision 1.471.
  708   Fri Sep 24 19:17:52 2004 Idea Steve Jonessteve.jones@freescale.comRequestAll2.5.4Enhanced "eLog Version" Variable
Stefan, would it be ok to add the "minor" revision level to the VERSION
constant?  I've been doing this after I download source just so I can keep
things straight, you keep cranking out versions ;->

EX: 
#define VERSION "2.5.4-4"
BECOMES
#define VERSION "2.5.4-4-1.483" or something like that?

Just a thought.

Thanks
  709   Fri Sep 24 22:37:01 2004 Reply Stefan Rittstefan.ritt@psi.chRequestAll2.5.4Re: Enhanced "eLog Version" Variable
Sorry for that. The idea is that the -4 is the minor number between releases
(mainly for bug fixes and impatient users (;-) ). I accidently overwrote the
-4 version several times when testing a new RPM building scheme, but I promise
to take more care in the future (:-)))

Having the CVS revision in the executable is however a good idea and I will
put it in.

> Stefan, would it be ok to add the "minor" revision level to the VERSION
> constant?  I've been doing this after I download source just so I can keep
> things straight, you keep cranking out versions ;->
> 
> EX: 
> #define VERSION "2.5.4-4"
> BECOMES
> #define VERSION "2.5.4-4-1.483" or something like that?
> 
> Just a thought.
> 
> Thanks
  713   Wed Oct 6 06:14:36 2004 Agree Steve Jonessteve.jones@freescale.comCommentAll2.5.4Re: Enhanced "eLog Version" Variable
No big deal - I looked at the code and you did a much more thorough job than I
would have done. Appreciate all of the hard work -- this product is masterful!

> Sorry for that. The idea is that the -4 is the minor number between releases
> (mainly for bug fixes and impatient users (;-) ). I accidently overwrote the
> -4 version several times when testing a new RPM building scheme, but I promise
> to take more care in the future (:-)))
> 
> Having the CVS revision in the executable is however a good idea and I will
> put it in.
> 
> > Stefan, would it be ok to add the "minor" revision level to the VERSION
> > constant?  I've been doing this after I download source just so I can keep
> > things straight, you keep cranking out versions ;->
> > 
> > EX: 
> > #define VERSION "2.5.4-4"
> > BECOMES
> > #define VERSION "2.5.4-4-1.483" or something like that?
> > 
> > Just a thought.
> > 
> > Thanks
  761   Tue Nov 2 02:51:09 2004 Question Kristinn B. Gylfasonelog@askur.orgQuestionLinux2.5.4Can the elog client submit an entry with a html body?
I'm running a Debian package of elog with verision number 2.5.4+r1480-1. 
The revision of the elog client in this package is 1.21. 

I'm using the elog client to send entries generated by a script to my
logbook.  I want to format the body text of the entry using HTML, to include
links and images.  When I submit the entry with the elog client it is
submited as text and not HTML.  

The man page for the elog client does not mention any commandline options to
specify the formating of the entry and I have not found any info in this
forum on the issue.

Is it possible to submit an entry with a html body using the elog client?
  762   Tue Nov 2 17:47:43 2004 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.5.4Re: Can the elog client submit an entry with a html body?
> Is it possible to submit an entry with a html body using the elog client?

I added a "-H" flag for that. New version of elog.c under CVS and in the next
release.
  763   Tue Nov 2 18:15:09 2004 Reply Kristinn B. Gylfasonelog@askur.orgQuestionLinux2.5.4Re: Can the elog client submit an entry with a html body?
> > Is it possible to submit an entry with a html body using the elog client?
> 
> I added a "-H" flag for that. New version of elog.c under CVS and in the next
> release.

Great!  Thanks.

Kristinn
  1449   Wed Oct 12 23:59:13 2005 Question Matt Kimballmatthew.j.kimball@state.or.us Windows2.5.4Trying to remove "mailto:" from the email address
We are using ver 2.5.4. As users enter new requests into the system, they would like email notifications. I have added the $user_email into a "notifications" section that we created. The email address that gets entered is "mailto:user@domain.com". Is there a way to remove the "mailto:"? Attached is my config file.

Thanks
Matt
Attachment 1: elogconfig.txt
#### Open Problems

Theme = default
Comment = HIV Client Services Requests
Subdir = hivclien
Time format = %B %d, %Y 
Use Lock = 0
Reverse sort = 1
Entries per page = 999
Page Title = Work Requests

### Menu Commands

## Use this line normally 
Menu Commands = Back, List, New, Edit, Find, Last Day, Last 10, Logout, Help, Move to, Config
Find Menu Commands = Back, List, New, Find, Select, Logout, Help, Move to, Config

Allow Delete = rpeterso, pmeyer, mattkimball
Allow Config = rpeterso, pmeyer, mattkimball

Move to = Completed Work Requests
Menu text = work_requests_menu.txt
Use Email Subject = $Title
Use Email Heading = The OIS Tracking system has just received a work request. 
Use Email Heading Edit = A work request in the OIS Tracking system has just been changed. 
Email All = $Notifications, "$Also Notify (email address)", patrick.j.meyer@state.or.us
Message comment = Please describe what you need here.
Attachment comment = Please attach screenshots or auxiliary documents here.
Display mode = summary

# Can add an edit column by putting Edit in the list, but it works a little cheesy, also, need to put edit.gif in the gif directory
List display = ID, Date, System, Title, Priority, Date Needed, Status, Work Order, Percent Complete, Expected Delivery, Estimated Hrs
Summary lines = 7
ID display = $message id

## Filter options
Quick filter = System, Priority, Status, Date, Work Order, Assigned To

##### The Good Stuff #########

### Attributes we are tracking
Attributes = Requestor, System, Subsystem, Title, Priority, Date Needed, Type, Also Notify (email address), Status, Assigned To, Percent Complete, Estimated Hrs, Actual Hrs, Date Added, Expected Delivery, Date Completed, Notifications, Requestor_Email, Completed 


### System Picking
Options System = CAREAssist{sy03}, CAREWare{sy04}, 


Options Requestor = Sharon Arnett, Annick Benson, Ryan Deibert, Vic Fox{rac}, Lisa McAuliffe, John McDaniel, Jill Snyder, Denise Skrykar, Carolyn Underwood, Other...{rzz}

### Priority -- changed from radio to regular to permit use in e-mail rules
Options Priority = A-Emergency{p1}, B-Critical{p2}, C-Other {p3}
Preset Priority = C-Other

### When it is needed (if there is a defined date)
Type Date Needed = date

### Type 
ROptions Type = Ad-hoc Query, Bug (Brk/Fix), Enhancement, Inquiry, Support, Other

### Also Notify - Just a blank field holds e-mail addresses of 
Comment Also Notify (email address) = <BR><b>Below for OIS staff only.</b>

### Status -- changed from radio to regular to permit use in e-mail, prefill, reply and lock rules 
Options Status = 1-Requested{s1}, 2-Need More Detail{s2}, 3-Estimated{s3}, 4-Assigned{s4}, 5-Delivered {s5}, 6-Closed (No Info/Dup/Not Approved){s6}
Preset Status = 1-Requested

### Work Order
ROptions Work Order = 1, 2, 3, 4, 5, 6+

### Actual Effort
Type Actual Effort = numeric
Comment Actual Effort = (in man-hours)

### Specify the day this was added
Type Date Added = date
Preset Date Added = $date

### Specify the expected delivery date
Type Expected Delivery = date

### When was the work request completed?
Type Date Completed = date

### Percent Complete
ROptions Percent Complete = 0%, 5%, 10%, 25%, 50%, 75%, 90%, 100%
## Preset Percent Complete = 0%

Options Completed = Yes, No
Preset Completed = No

### Don't even know if this stuff works...
Format Assigned To = 0, attribname, attribvalue, 30, 30
Format Estimated = 1, attribname, attribvalue, 3, 3
Format Actual = 1, attribname, attribvalue, 3, 3

preset Requestor_Email = $user_email
###locked attributes = Requestor_Email


######################
## The Status Specific Stuff
############################
{s1} Subst Completed = No
{s1 s3 s3 s3a s4 s5 s6 s7a s7b} Subst Completed = No
{s8a s8b s8c} Subst Completed = Yes

############################
### The System Specific Stuff
#############################

## CareAssist aka ADAP
{sy03} Options Subsystem = SpendDown, Reporting, ED!, Other
{sy03} Options Assigned To = Reginald Liggins, James Soult, 
{sy03 & s1} Preset Assigned To = James Soult
{sy03 & s1} Preset Notifications = reginald.liggins@state.or.us, james.soult@state.or.us, victor.j.fox@state.or.us, matthew.j.kimball@state.or.us, $user_email
{sy03 & s2} Preset Notifications = reginald.liggins@state.or.us, james.soult@state.or.us,  victor.j.fox@state.or.us, matthew.j.kimball@state.or.us
{sy03 & s3} Preset Notifications = reginald.liggins@state.or.us, james.soult@state.or.us,  victor.j.fox@state.or.us, matthew.j.kimball@state.or.us
{sy03 & s3a} Preset Notifications = reginald.liggins@state.or.us, james.soult@state.or.us,  victor.j.fox@state.or.us, matthew.j.kimball@state.or.us
{sy03 & s4} Preset Notifications = reginald.liggins@state.or.us, james.soult@state.or.us, matthew.j.kimball@state.or.us
{sy03 & s5} Preset Notifications = reginald.liggins@state.or.us, james.soult@state.or.us, matthew.j.kimball@state.or.us 
{sy03 & s6} Preset Notifications = reginald.liggins@state.or.us, james.soult@state.or.us,  victor.j.fox@state.or.us, matthew.j.kimball@state.or.us
{sy03 & s7a} Preset Notifications = reginald.liggins@state.or.us, james.soult@state.or.us,  victor.j.fox@state.or.us, matthew.j.kimball@state.or.us
{sy03 & s7b} Preset Notifications = reginald.liggins@state.or.us, james.soult@state.or.us,  victor.j.fox@state.or.us, matthew.j.kimball@state.or.us
{sy03 & s8a} Preset Notifications = reginald.liggins@state.or.us, james.soult@state.or.us,  victor.j.fox@state.or.us, matthew.j.kimball@state.or.us
{sy03 & s8b} Preset Notifications = reginald.liggins@state.or.us, james.soult@state.or.us,  victor.j.fox@state.or.us, matthew.j.kimball@state.or.us
{sy03 & s8c} Preset Notifications = reginald.liggins@state.or.us, james.soult@state.or.us,  victor.j.fox@state.or.us, matthew.j.kimball@state.or.us

## CAREWare
{sy04} Options Subsystem = Old, New, Other
{sy04} Options Assigned = Robin Peterson
{sy04} Preset Assigned To = Robin Peterson
Email System CareWare = robin.h.peterson@state.or.us, matthew.j.kimball@state.or.us, $user_email

## Cashfile
{sy05} Options Subsystem = Old, New, Other, Other
{sy05} Options Assigned To = Bob Winfield, Tony Sukonik, Robin Peterson
{sy05} Preset Assigned To = Robin Peterson
{sy05} Email System Cashfile = robin.h.peterson@state.or.us, john.mcadams@state.or.us, bob.e.winfield@state.or.us




#####################################################################################################
#####################################################################################################
ELOG V3.1.5-3fb85fa6