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!

 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.

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

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

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

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

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

Any reason why when I click "Reply" to a previous submission that the body is full of HTML code?

See below:

<p>
<table width="98%" align="center" cellspacing="1" style="border:1px solid #486090;">
<tbody>
<tr>
<td cellpadding="3px" style="background-color:#486090; font-weidht:bold; color:white;">Hal Proctor wrote:</td></tr>
<tr>
<td cellpadding="10px" style="background-color:#FFFFB0;"><p>
<table width="98%" align="center" cellspacing="1" style="border:1px solid #486090;">
<tbody>
<tr>
<td cellpadding="3px" style="background-color:#486090; font-weidht:bold; color:white;">Quote:</td></tr>
<tr>
<td cellpadding="10px" style="background-color:#FFFFB0;">removed the thing and the other thing....added this and that!</td>
</tr>
</tbody>
</table>
</p><p> </p>
testing reply</td>
</tr>
</tbody>
 

Here is my logbook config:

[Logbook]
Theme = default
Comment = Maintenance Logbook
Attributes = Author, Type, Category, Subject, Shift
Options Type = Repair, Routine, Preventative, Other
Options Category = Emergency, General, Change-Over, Other
Options Shift = 1, 2, 3
Extendable Options = Category
Required Attributes = Author, Type
Page Title = Maint Log - $subject
Reverse sort = 1
Preset Author = $long_name
Preset on reply Author = $long_name
Locked Attributes = Author
Quick filter = Date, Type, Category

I don't see any mistake in the configuration file. Did you switch the "Encoding" from HTML to plain? (Radio buttons at the bottom just below the text window). Is there a problem with your FCKEditor? Do you see the formatting menu bar? 

 I do not get the formatting menu with HTML.  I switched to plain and code still exists.  The only formatting menu I get is when I choose ELCode.   I have no problem with this forum seeing the formatting menu with HTML (although it does take some time to load). 

 Tested it in Chrome and acts the same as IE8 (just much slower)

 It's version issue!!   2.92 does not utilize FCKeditor correctly.  Backed off one version and it works fine!  2.91 is GOOD!

Actually I can confirm a similar issue with 2.9.2:

when I create a new entry with the default "HTML" encoding and then swap to "plain", the text area is cluttered with HTML code (see attachment new_entry.txt)

I did notice it, but I did not pay much attention to it. But I agree is should be fixed. But in my case it could be related to a firefox add-on "It's all text" that uses java script to modify the HTML code.

Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Detect language Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish ⇄ Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish

Detect language » English

 

Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Detect language Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish ⇄ Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish

Detect language » English

 

Andreas

Hi all,

I'm absolutely new with ELOG and have only basic programming skills...

I'd like to use ELOG, so I have installed it in my computer to start playing with it (I installed version 2.7.0-1953 because with the latest one I got an error with the elogd.cfg file). I've been able to open the Demo logbook but wasn't able to submit a new entry into it. I get the following error:

"HTML encoding not allowed"

Could you please explain me how I could solve this problem?

I thank you in advance for your help.

Version 2.7.0 is very old and has knows problem. Better go with the current version and fix the problem with the elogd.cfg file.