Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 90 of 238  Not logged in ELOG logo
icon1.gif   Dual Time display and entry times, posted by Bruce Weber on Mon Jan 14 03:05:41 2013 

ELog has been installed on our local server which runs on local time (UTC +8) and is working well, however, we work in two time zones.

Our PC's run in local time (IT requirement) but need to save and display one log in UTC and one log in local time - can this be done?

Appreciate anyones help!

Thanks

    icon2.gif   Re: Dual Time display and entry times, posted by Yoshio Imai on Mon Jan 14 13:33:19 2013 
Depending on whether I understand your requirement correctly, the following solution should work:
  • define an additional logbook attribute, say "UTC Date"
  • preset it on entry creation and submission with the UTC timestamp (cf. section "Attributes" of the ELog configuration guide):
    Preset UTC Date = $utcdate
    Subst UTC Date = $utcdate
  • prevent the attribute from being changed manually by adding it to the
    Locked Attributes = < ... >
    and
    Fixed Attributes Edit = < ... >
    lists, respectively.
    You may also have to add it to the
    Remove on reply = < ... >
    list if replies turn out to keep the "UTC Date" value of the original entry.

Regards,
icon5.gif   Main Logbook screen with Multi Grouped Logbooks with unique user permissions, posted by Hal Proctor on Tue Dec 18 23:03:57 2012 Main.jpgTabs.jpg

I have a couple questions on how to configure multiple logbooks with groups.

  1. How can I have a user have permissions to a single logbook that is within a group and jump to it using tabs?
    1. Launching from main/home screen may work, but using tabs from one group to another where the single workbook resides in a group of others, it errors out or asks for login to a logbook you may not have rights to.(always the first book in the group)
  2. How can I force a main login to direct you to the MAIN logbook selection screen?

 

Example: (use images for reference)  A user has permissions to "Punch" and "Maintenance".  Maintenance is a single logbook and Punch is within the group "Dry Room". 

While the user is in Maintenance and without having to jump back to the MAIN selection screen, how can the user select the Tab "Dry Room" as seen in image, without throwing up or redirecting you?

    icon2.gif   Re: Main Logbook screen with Multi Grouped Logbooks with unique user permissions, posted by Stefan Ritt on Thu Jan 10 10:52:11 2013 

Hal Proctor wrote:

I have a couple questions on how to configure multiple logbooks with groups.

  1. How can I have a user have permissions to a single logbook that is within a group and jump to it using tabs?
    1. Launching from main/home screen may work, but using tabs from one group to another where the single workbook resides in a group of others, it errors out or asks for login to a logbook you may not have rights to.(always the first book in the group)
  2. How can I force a main login to direct you to the MAIN logbook selection screen?

 

Example: (use images for reference)  A user has permissions to "Punch" and "Maintenance".  Maintenance is a single logbook and Punch is within the group "Dry Room". 

While the user is in Maintenance and without having to jump back to the MAIN selection screen, how can the user select the Tab "Dry Room" as seen in image, without throwing up or redirecting you?

There are several options:

  • Use a bookmark in your browser. Put a link directly "Punch" and "Maintenance" in the link list of your browser and you can directly jump to that logbook. Different users can define different bookmarks in their browsers.
  • Change the order of the logbooks in the group, like put "Punch" to be the first one in your group. But if you have different users with different permissions this will of course not work for all.
  • Give up groups and just keep a linear list of logbooks. 

2. is not possible. Even if you use "Protect selection page", you will always be redirected to the first logbook after logging in. Maybe I should change that.

 

icon5.gif   trouble ticket systems w/ elog?, posted by Miles Fidelman on Mon Jan 7 01:45:10 2013 

Updating my toolbox.  Starting to use elog as, well, a logbook.  Kind of liking the short, sweet, to the point capabilities.

Which leads me to wonder if anybody has opinions on trouble ticket systems that work well with elog?

Thanks!

Miles Fidelman

 

    icon2.gif   Re: trouble ticket systems w/ elog?, posted by David Pilgram on Wed Jan 9 11:19:50 2013 

Miles Fidelman wrote:

Updating my toolbox.  Starting to use elog as, well, a logbook.  Kind of liking the short, sweet, to the point capabilities.

Which leads me to wonder if anybody has opinions on trouble ticket systems that work well with elog?

Thanks!

Miles Fidelman

 

 I use elog's built-in ticketing system, and use the auto-generated ticket number to cross-reference with other matters/documents/files.  Much of the documentation for tickets is rather buried away under Subst <attribute> = <string>.

I've not found a way to link from an entry to a set of entries in another thread by their ticket number, particularly across more than one logbook.  [This is possible via their elog entry number, and which logbook it is in].  The former would be usefil to cross-reference an incident which you identify external to the elog system - "Oh, it's another one like [Ticket no] NOV12-001" possibily easier than "Oh it's another one like elog:archive12/67142 ".  Oh, the last bit should be highlighed as a (non-existant) link here, to show my point, nice of the ticket could be as well.

On the plus side, you can arrange the ticket number to show up in the thread display, quick search by ticket number, run different ticket colours (as it were) in different logbooks (i.e. different prefixes).  Just ensure you don't archive the latest entry, as that can lead to duplication of ticket numbers.

 

       icon2.gif   Re: trouble ticket systems w/ elog?, posted by Miles Fidelman on Wed Jan 9 18:20:41 2013 

David Pilgram wrote:

Miles Fidelman wrote:

Updating my toolbox.  Starting to use elog as, well, a logbook.  Kind of liking the short, sweet, to the point capabilities.

Which leads me to wonder if anybody has opinions on trouble ticket systems that work well with elog?

Thanks!

Miles Fidelman

 

 I use elog's built-in ticketing system, and use the auto-generated ticket number to cross-reference with other matters/documents/files.  Much of the documentation for tickets is rather buried away under Subst <attribute> = <string>.

I've not found a way to link from an entry to a set of entries in another thread by their ticket number, particularly across more than one logbook.  [This is possible via their elog entry number, and which logbook it is in].  The former would be usefil to cross-reference an incident which you identify external to the elog system - "Oh, it's another one like [Ticket no] NOV12-001" possibily easier than "Oh it's another one like elog:archive12/67142 ".  Oh, the last bit should be highlighed as a (non-existant) link here, to show my point, nice of the ticket could be as well.

On the plus side, you can arrange the ticket number to show up in the thread display, quick search by ticket number, run different ticket colours (as it were) in different logbooks (i.e. different prefixes).  Just ensure you don't archive the latest entry, as that can lead to duplication of ticket numbers.

 

 By "ticket number" are you referring to the Message ID, or is there some additional trouble ticket functionality buried away?  And... can you point me to the documentation that's "buried away under Subst <attribute> = <string>?  Thanks!

          icon2.gif   Re: trouble ticket systems w/ elog?, posted by David Pilgram on Wed Jan 9 21:07:53 2013 

Miles Fidelman wrote:

David Pilgram wrote:

Miles Fidelman wrote:

Updating my toolbox.  Starting to use elog as, well, a logbook.  Kind of liking the short, sweet, to the point capabilities.

Which leads me to wonder if anybody has opinions on trouble ticket systems that work well with elog?

Thanks!

Miles Fidelman

 

 I use elog's built-in ticketing system, and use the auto-generated ticket number to cross-reference with other matters/documents/files.  Much of the documentation for tickets is rather buried away under Subst <attribute> = <string>.

I've not found a way to link from an entry to a set of entries in another thread by their ticket number, particularly across more than one logbook.  [This is possible via their elog entry number, and which logbook it is in].  The former would be usefil to cross-reference an incident which you identify external to the elog system - "Oh, it's another one like [Ticket no] NOV12-001" possibily easier than "Oh it's another one like elog:archive12/67142 ".  Oh, the last bit should be highlighed as a (non-existant) link here, to show my point, nice of the ticket could be as well.

On the plus side, you can arrange the ticket number to show up in the thread display, quick search by ticket number, run different ticket colours (as it were) in different logbooks (i.e. different prefixes).  Just ensure you don't archive the latest entry, as that can lead to duplication of ticket numbers.

 

 By "ticket number" are you referring to the Message ID, or is there some additional trouble ticket functionality buried away?  And... can you point me to the documentation that's "buried away under Subst <attribute> = <string>?  Thanks!

Message ID is the internal numbering of each entry.  It is the number that is used internally for generating the threads, and which you can reference with the elog:[message ID] code within an entry to cross reference the entry with that message ID.

"Ticket" is the name of an attribute.  You define the attribute "Ticket", and can preload the attribute with the format  you require(*).  In the following extract of an elog.cfg file are the relivent lines to generate tickets, show the ticket number in the thread display, search for a particular ticket, and allow it to be edited when writing an entry - there are reasons.  The attribute "Organisation" here is an example of another attribute you would enter with the initial entry, of course there will be others specific to your requirements.

Attributes = Ticket, Organisation, ...

Preset ticket = T#####

Thread display = $Ticket: $Organisation, ...

Quick filter = Ticket, ID

 

When you start an new entry, the Ticket attribute is prepopulated with a number.  The first time will be T00001, subsequently it will be one higher than the currently existing highest ticket number in the logbook.

Why might you edit the ticket number?  You may wish to go back and edit an old (complete) entry's ticket number so it has some obvious name - perhaps the solution of what proves to be a stock problem, that has become known by a pet phrase, so it can be found by searching for that phrase in the quick fillter "Ticket".  That is a more advanced use of the ticket system.

 (*) Further on the format of the ticket is in the documentation under Subst <attribute> = <string>

Sorry for multiple edits, why cannot I cross-reference an entry in this forum as I can in my local logbook?

 

             icon2.gif   Re: trouble ticket systems w/ elog?, posted by Miles Fidelman on Wed Jan 9 22:28:20 2013 

David Pilgram wrote:

Miles Fidelman wrote:

David Pilgram wrote:

Miles Fidelman wrote:

Updating my toolbox.  Starting to use elog as, well, a logbook.  Kind of liking the short, sweet, to the point capabilities.

Which leads me to wonder if anybody has opinions on trouble ticket systems that work well with elog?

Thanks!

Miles Fidelman

 

 I use elog's built-in ticketing system, and use the auto-generated ticket number to cross-reference with other matters/documents/files.  Much of the documentation for tickets is rather buried away under Subst <attribute> = <string>.

I've not found a way to link from an entry to a set of entries in another thread by their ticket number, particularly across more than one logbook.  [This is possible via their elog entry number, and which logbook it is in].  The former would be usefil to cross-reference an incident which you identify external to the elog system - "Oh, it's another one like [Ticket no] NOV12-001" possibily easier than "Oh it's another one like elog:archive12/67142 ".  Oh, the last bit should be highlighed as a (non-existant) link here, to show my point, nice of the ticket could be as well.

On the plus side, you can arrange the ticket number to show up in the thread display, quick search by ticket number, run different ticket colours (as it were) in different logbooks (i.e. different prefixes).  Just ensure you don't archive the latest entry, as that can lead to duplication of ticket numbers.

 

 By "ticket number" are you referring to the Message ID, or is there some additional trouble ticket functionality buried away?  And... can you point me to the documentation that's "buried away under Subst <attribute> = <string>?  Thanks!

Message ID is the internal numbering of each entry.  It is the number that is used internally for generating the threads, and which you can reference with the elog:[message ID] code within an entry to cross reference the entry with that message ID.

"Ticket" is the name of an attribute.  You define the attribute "Ticket", and can preload the attribute with the format  you require(*).  In the following extract of an elog.cfg file are the relivent lines to generate tickets, show the ticket number in the thread display, search for a particular ticket, and allow it to be edited when writing an entry - there are reasons.  The attribute "Organisation" here is an example of another attribute you would enter with the initial entry, of course there will be others specific to your requirements.

Attributes = Ticket, Organisation, ...

Preset ticket = T#####

Thread display = $Ticket: $Organisation, ...

Quick filter = Ticket, ID

 

When you start an new entry, the Ticket attribute is prepopulated with a number.  The first time will be T00001, subsequently it will be one higher than the currently existing highest ticket number in the logbook.

Why might you edit the ticket number?  You may wish to go back and edit an old (complete) entry's ticket number so it has some obvious name - perhaps the solution of what proves to be a stock problem, that has become known by a pet phrase, so it can be found by searching for that phrase in the quick fillter "Ticket".  That is a more advanced use of the ticket system.

 (*) Further on the format of the ticket is in the documentation under Subst <attribute> = <string>

Sorry for multiple edits, why cannot I cross-reference an entry in this forum as I can in my local logbook?

 

Thanks for the additional details!

 

icon5.gif   hyperlink to file, posted by Diego on Tue Jan 8 20:02:04 2013 

 Hi,

I would like to make an hyperlink to an external file in a messaje. I have writen Allow (HTML = 1) in .cfg file and the hyperlink as

<p><a href="file:\\external_computer\directory">test</a></p>

It did not work. However if I write in the chrome browser:

file:\\external_computer\directory

It works.

Thank you so much!!

 

    icon2.gif   Re: hyperlink to file, posted by Stefan Ritt on Wed Jan 9 10:12:14 2013 

Diego wrote:

 Hi,

I would like to make an hyperlink to an external file in a messaje. I have writen Allow (HTML = 1) in .cfg file and the hyperlink as

<p><a href="file:\\external_computer\directory">test</a></p>

It did not work. However if I write in the chrome browser:

file:\\external_computer\directory

It works.

Thank you so much!!

 

A link to a local file inside a web page does never work on purpose. Malicious web pages could otherwise get access to your local password file for example which would be a huge security hole. You have to copy the link address explicitly into your URL bar of the browser.

icon5.gif   number of attachments limit, posted by Devin Bougie on Thu Dec 20 17:08:51 2012 

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

    icon2.gif   Re: number of attachments limit, posted by Stefan Ritt on Mon Jan 7 16:46:54 2013 

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

 

icon5.gif   How to put "Quote text" _below_ new message?, posted by Valentin on Thu Dec 27 01:33:11 2012 

Hi there,

It seems that by default in a message created as "reply" of another message, the "quoted text" of the original entry is put at the _TOP_ of the new entry and not movable (Firefox 17, elog 2.92). I would strongly like to have it opposite, i.e. that one is able to create a new text first and only then has the "quoted text" since people are interested to see a new information and only then the previous messages as sort of "reminder". It was like this in older (2.6?) version but now I did not find how to change this default behavior. Did I miss something?

Cheers

Valentin

    icon2.gif   Re: How to put "Quote text" _below_ new message?, posted by David Pilgram on Thu Dec 27 12:52:00 2012 

Valentin wrote:

Hi there,

It seems that by default in a message created as "reply" of another message, the "quoted text" of the original entry is put at the _TOP_ of the new entry and not movable (Firefox 17, elog 2.92). I would strongly like to have it opposite, i.e. that one is able to create a new text first and only then has the "quoted text" since people are interested to see a new information and only then the previous messages as sort of "reminder". It was like this in older (2.6?) version but now I did not find how to change this default behavior. Did I miss something?

Cheers

Valentin

I use plain encoding, cannot answer for the others but it should do the trick as it's in the documentation.  I'm using Firefox some large number and 2.9.2.-2475

I do what I believe you want, and get it by having the following line in my config file for that logbook (which is part of elog.cfg):

 Prepend on reply = \n

This gives a blank line at the "top" of the entries when you start a reply, and all the previous entries gain another "> " unless you've also altered that default behaviou (as in fact I have).  The result then looks like:

Latest line of text

> Previous entry

> > Previous entry to that

       icon2.gif   Re: How to put "Quote text" _below_ new message?, posted by Stefan Ritt on Mon Jan 7 16:43:27 2013 

If you use HTML encoding, you can do that with

Prepend on reply = <br />

to achieve the same thing (as I did just here in this reply).

Stefan

 

David Pilgram wrote:

Valentin wrote:

Hi there,

It seems that by default in a message created as "reply" of another message, the "quoted text" of the original entry is put at the _TOP_ of the new entry and not movable (Firefox 17, elog 2.92). I would strongly like to have it opposite, i.e. that one is able to create a new text first and only then has the "quoted text" since people are interested to see a new information and only then the previous messages as sort of "reminder". It was like this in older (2.6?) version but now I did not find how to change this default behavior. Did I miss something?

Cheers

Valentin

I use plain encoding, cannot answer for the others but it should do the trick as it's in the documentation.  I'm using Firefox some large number and 2.9.2.-2475

I do what I believe you want, and get it by having the following line in my config file for that logbook (which is part of elog.cfg):

 Prepend on reply = \n

This gives a blank line at the "top" of the entries when you start a reply, and all the previous entries gain another "> " unless you've also altered that default behaviou (as in fact I have).  The result then looks like:

Latest line of text

> Previous entry

> > Previous entry to that

 

icon5.gif   SMTP Error: authentication not enabled, posted by Satish Desai on Fri Jan 4 00:28:09 2013 

Hi all,

I am trying to set up elog here at the University of Minnesota.  It looks very promising for helping to manage a fairly complicated operation.  I've got most of what I want set up without too much difficulty.  However, I find that I'm having some difficulty to get it working properly with email.

In particular, I have my account set up to email me when log entries are made (subscribe to logbooks option is selected).   In the global section of my elogd.conf file I have set up the variables:

SMTP host = factoryserver5
SMTP username = factory

However, when I make a test entry, I get an error at the top:

Error sending Email via <i>"factoryserver5"</i>: 5.5.1 Error: authentication not enabled

I tried setting the password using "elogd -t" but to no avail.  I also tried a few different values for SMTP host

Any suggestions as to what I am doing wrong?

 

Cheers,

Satish

    icon2.gif   Re: SMTP Error: authentication not enabled, posted by Stefan Ritt on Mon Jan 7 16:39:31 2013 

Satish Desai wrote:

Hi all,

I am trying to set up elog here at the University of Minnesota.  It looks very promising for helping to manage a fairly complicated operation.  I've got most of what I want set up without too much difficulty.  However, I find that I'm having some difficulty to get it working properly with email.

In particular, I have my account set up to email me when log entries are made (subscribe to logbooks option is selected).   In the global section of my elogd.conf file I have set up the variables:

SMTP host = factoryserver5
SMTP username = factory

However, when I make a test entry, I get an error at the top:

Error sending Email via <i>"factoryserver5"</i>: 5.5.1 Error: authentication not enabled

I tried setting the password using "elogd -t" but to no avail.  I also tried a few different values for SMTP host

Any suggestions as to what I am doing wrong?

 

Cheers,

Satish

There are several SMTP authorisation options, and only a subset is supported by ELOG. Have you tried without the "SMTP username"?

Stefan

icon5.gif   Hide/Un-hide Commands based on Attribute Option value, posted by Barend on Wed Jan 2 14:04:41 2013 

Hi Stefan,

Happy New Year!

I ran several searches thru the forum but I could not detect a suitable entry on the following:

Is it possible to hide/un-hide the Commands, like "Edit", "Reply", "Duplicate", from the Menu based upon an Option of an Attribute?

E.g. Attributes = Status, .. | Options Status = Open, Closed

When Status = "Open"; the Menu Commands "Edit", "Reply" and "Duplicate" are available.

When Status = "Closed"; the Menu Commands "Edit", "Reply" and "Duplicate" are hidden/not available.

-or-

Can this only be accomplished using 2 Logbooks (Open / Closed) and move an entry from "Open" to "Closed" where the Logbook "Closed" is not using the Commands  "Edit", "Reply", "Duplicate".

 

Kind regards,

Barend

ELOG V3.1.5-3fb85fa6