Hi Daniel,

this is an undesired side effect of a new feature. I wouldn't call it a bug ;-)

There is no straight forward way for elog to distinguish between a "Submit" and an automatic save. Therefore the "... on edit = ..." kicks in when an entry is saved automatically.

I guess Stefan can figure out a workaround, but for the moment I would sugest that you just switch off the auto save feature -- if you want to keep your save history:

Save drafts = 0

Hello.

In Elog i have attribute called "Zmieniano" (eng. changed)  which should store how many times entry was edited. If entry was not edited it should have only preset value "oryginalny wpis" (eng. oryginal entry), but when I edit it, it should have also date, time, and person who make edit (this is made by "Subst on Edit Zmieniano = $Zmieniano<br>- Zmiana $date przez $long_name z $remote_host)". 

From version V3.1.1-3f311c5 I have problem with that. 

When I add entry, and entry is auto saved, then auto save is shown in the attribute "Zmieniano" (eng. changed) as an next edit, which I dont want. Entry from attached screenshot was not edited, but in "Zmieniano" (eng. changed) attributes it has two values:

• Oryginalny wpis (eng. oryginal entry),
• Zmiana 27.08.2015, 10:52 przez Daniel Sajdyk z serwerownia.sr.lez (eng. Changed 27.08.2015.... ) 

The second value is autosave time. 

Is this a bug?

Regards

Daniel. 

Yes, this can be done. See below for an example configuration.

Attributes = entrytype, category
Options entrytype = routine{1}, problem{2}
Options category = software, hardware

{1} Email category software =
{1} Email category hardware =
{2} Email category software = 1@opq.rst, 2@uvw.xyz
{2} Email category hardware = a@bcd.efg, h@ijk.lmn

Is there a way to distribute e-mail based on the consideration of several attributes and values?  A simple example:  attributes type and category have several different values, say, routine and problem for type and hardware and software for category, but one would only like messages sent when there's a problem to different sets of hardware or software types.  Thus:

Email

type routine   category hardware = no message

                        category software = no message

type problem  category hardware =  a@bcd.efg, h@ijk.lmn

                         category software = 1@opq.rst, 2@uvw.xyz

Thanks for reportung that bug. I fixed it in revision f828049.

There seems to be a small problem with the new "Date/Time format <attribute>" implementation. It works great for the detailed view of a single entry:

But fails to work on the list view (same entry, the Date column is formated as it should):

Relevant config part:

Time format Time Start = %H:%M:%S
Time format Time End = %H:%M:%S

I am interested in using LDAP authentication for elogd on Windows for which it looks like I need to compile from source, enabling LDAP in the make file.

Does anyone have advice on build environments for Windows in which they have had success making elog?  Free ones preferably, such as Cygwin. 

I'm sorry... it was my mistake. I put Resolve host names in logbook config instead global.

Regards Daniel.