Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 465 of 808  Not logged in ELOG logo
New entries since:Thu Jan 1 01:00:00 1970
ID Date Icon Author Author Email Category OS ELOG Version Subject
  66098   Sat Dec 6 22:30:56 2008 Question mike ciancimike2.cianci@comcast.netQuestion  Change background color

I copied the following line from the ELOG documentation file to my config file (with the appropriate changes to the attribute and value fields) and nothing happens. Am I missing something?

Style importance severe = background-color:red

Thanks for all your help.


  66097   Fri Dec 5 16:14:19 2008 Reply Steve WilliamsonStephenWilliamson@Barnsley.gov.ukBug reportLinux2.7.5Re: Auto-increment attributes

Steve Williamson wrote:

We have an auto-incrementing reference attribute defined as:

# RFC

Format RFC = 0,narrowattribname,narrowattribvalue,60,60
Preset RFC = RFC-######
Preset On Duplicate RFC = RFC-######
Tooltip RFC = A unique reference will be generated for this Request For Change

We also have a "Created by/when" attribute.  Looking at the values this seems to be set when the user clicks "New" whereas the time stamp that appears on the line after the  $@MID@$ seems to be set when the user clicks "Submit".

# Created

Format Created = 0,attribname,attribvalue,70,100
Preset Created = $long_name ($short_name) on $date
Preset On Duplicate Created = $long_name ($short_name) on $date

Every once in a while the incrementing stops working and the number 'sticks' or misses some out.  It looks as if it might be because multiple people are adding entries concurrently.  Could the occasion where there is a gap in the sequence (171-174) be where people abandoned changes (clicked on "Back") after having numbers allocated?  Here is a list showing the discrepancies.

Date        Item     Time Stamp (from the line after $@MID@$)  "Created" attribute time stamp

22/09/08    124      16:15:10                                   11:58

22/09/08    125      16:33:54                                   16:24

 

22/09/08    125      16:35:37                                   16:33              Should be 126

...

10/10/08    146      10:39:09                                   10:30                    Correct

10/10/08    146      10:46:57                                   10:35              Should be 147

10/10/08    147      13:04:03                                   13:02              Should be 148

10/10/08    148      15:11:38                                   15:00              Should be 149

...

17/11/08    171      10:21                                      10:17              Correct

17/11/08    174      14:30                                      13:47              Should be 172

17/11/08    175      16:14                                      16:04              Should be 173

17/11/08    176      16:49                                      16:38              Should be 174

...

25/11/08    187      15:49:58                                   15:47              Correct

25/11/08    187      15:52:39                                   15:48              Should be 188

25/11/08    188      16:49:56                                   16:44              Should be 189

25/11/08    188      16:52:40                                   16:40              Should be 190

25/11/08    188      16:55:17                                   16:43              Should be 191

Let me know if you need any more information.

regards

Steve


 Hi

This is to let you know that the increment problem has just happened again.

Item 206 has timestamp (from the line after $@MID@$) of 11:59:45 and "created" attribute timestamp of 11:29

overlapping with this, a second item 206 has timestamp of 12:04:02 and "created" attribute of 11:53

So, both users were entering information between 11:53 and 11:59:45 and both picked up the same increment number.

There's no easy solution tho, is there? If you pick up the increment number at the start so it can be displayed on screen and ensure uniqueness then, if a user cancels a new entry you end up with "holes" in the sequence.  If you pick it up at the end then you can't display it until the user presses submit.

regards

Steve

  66096   Wed Dec 3 22:57:13 2008 Cool mike ciancimike2.cianci@comcast.netCommentWindows Re: Multi attribute email notification

Your suggestion worked GREAT (like always)


Stefan Ritt wrote:

 

mike cianci wrote:

What I would like to do is:

If attribute "A" and attribute  "B" - send email to person #1

If attribute "A" and attribute  "C" - send email to person #2

(I apologize if this in the documentation. I have looked at the "Email" section and have either missed it or don't understand it. Thank you for the help)

 

This is not implemented, you only can test on a single attribute. There might be a possibility with conditional attributes, but I have never tried this out.

 

  66095   Wed Dec 3 15:55:52 2008 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows Re: Multi attribute email notification

 

mike cianci wrote:

What I would like to do is:

If attribute "A" and attribute  "B" - send email to person #1

If attribute "A" and attribute  "C" - send email to person #2

(I apologize if this in the documentation. I have looked at the "Email" section and have either missed it or don't understand it. Thank you for the help)

 

This is not implemented, you only can test on a single attribute. There might be a possibility with conditional attributes, but I have never tried this out.

  66094   Tue Dec 2 23:23:34 2008 Question mike ciancimike2.cianci@comcast.netQuestionWindows Multi attribute email notification

What I would like to do is:

If attribute "A" and attribute  "B" - send email to person #1

If attribute "A" and attribute  "C" - send email to person #2

(I apologize if this in the documentation. I have looked at the "Email" section and have either missed it or don't understand it. Thank you for the help)

  66093   Tue Dec 2 17:18:10 2008 Reply weiluolwsy711@gmail.comQuestionLinux Re: How to attach screen shot in elog

Stefan Ritt wrote:

 

weiluo wrote:

 

Stefan Ritt wrote:

 

weiluo wrote:

I want to know if there were some way to insert a screen shot directly into the log book instead of going through the "save-attach" procedure. i.e. add some plug in button to do this under Linux?

Or, can I just make a plain log file "xxxx.log" and put it into the directory? Will that work?

Thanks

 

You cannot directly paste a screen shot into an elog entry. Use HoverSnap (Windows) or ksnapshot (linux) to produce directly an image file, then you need only two mouse clicks (browse and select file). There is also an Add-On for FireFox called "dragdropupload" which can be used for drag-and-drop a file into the attachment file selector. 

 

 I see. But what I want to do now is writing a script to make a elog entry, is that possible? I mean, I don't know if the log entry I generated could be recognized by elog.  e.g. the following text is generated by me, no through elog, is there a way to let them shown on elog?

Date: Mon, 01 Dec 2008 18:45:21 -0500
Author: Anonymous
Author Email: $user_email
Category: Shift summary
Subject: test
Attachment: 081201_184113_bigcal_014.jpg
Encoding: HTML
========================================
test

 

 For what you need you can use the "elog" utility, as described in https://midas.psi.ch/elog/userguide.html at the bottom. Using the "-f" option you can add attachments there.

 Got it! This is exactly what I need, thanks a lot!

  66092   Tue Dec 2 17:15:36 2008 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux Re: How to attach screen shot in elog

 

weiluo wrote:

 

Stefan Ritt wrote:

 

weiluo wrote:

I want to know if there were some way to insert a screen shot directly into the log book instead of going through the "save-attach" procedure. i.e. add some plug in button to do this under Linux?

Or, can I just make a plain log file "xxxx.log" and put it into the directory? Will that work?

Thanks

 

You cannot directly paste a screen shot into an elog entry. Use HoverSnap (Windows) or ksnapshot (linux) to produce directly an image file, then you need only two mouse clicks (browse and select file). There is also an Add-On for FireFox called "dragdropupload" which can be used for drag-and-drop a file into the attachment file selector. 

 

 I see. But what I want to do now is writing a script to make a elog entry, is that possible? I mean, I don't know if the log entry I generated could be recognized by elog.  e.g. the following text is generated by me, no through elog, is there a way to let them shown on elog?

Date: Mon, 01 Dec 2008 18:45:21 -0500
Author: Anonymous
Author Email: $user_email
Category: Shift summary
Subject: test
Attachment: 081201_184113_bigcal_014.jpg
Encoding: HTML
========================================
test

 

 For what you need you can use the "elog" utility, as described in https://midas.psi.ch/elog/userguide.html at the bottom. Using the "-f" option you can add attachments there.

  66091   Tue Dec 2 17:10:05 2008 Reply weiluolwsy711@gmail.comQuestionLinux Re: How to attach screen shot in elog

Stefan Ritt wrote:

weiluo wrote:

I want to know if there were some way to insert a screen shot directly into the log book instead of going through the "save-attach" procedure. i.e. add some plug in button to do this under Linux?

Or, can I just make a plain log file "xxxx.log" and put it into the directory? Will that work?

Thanks

You cannot directly paste a screen shot into an elog entry. Use HoverSnap (Windows) or ksnapshot (linux) to produce directly an image file, then you need only two mouse clicks (browse and select file). There is also an Add-On for FireFox called "dragdropupload" which can be used for drag-and-drop a file into the attachment file selector. 

 I see. But what I want to do now is writing a script to make a elog entry, is that possible? I mean, I don't know if the log entry I generated could be recognized by elog.  e.g. the following text is generated by me, no through elog, is there a way to let them shown on elog?

Date: Mon, 01 Dec 2008 18:45:21 -0500
Author: Anonymous
Author Email: $user_email
Category: Shift summary
Subject: test
Attachment: 081201_184113_bigcal_014.jpg
Encoding: HTML
========================================
test
 

 

ELOG V3.1.5-3fb85fa6