Hello,

I am currently using ELOG as a daily logbook for work performed for customers.  This is a critical tool and process for 1. Showing customers work history 2. having a searchable knowledge base for future reference.  

Currently, I will create a new log entry, assign the customer using a custom ROPTION in my elog.conf.  This process all works fine, mostly, except I run into the following obstacles (that are all human related.)

1. Many days, there are no log entries to be created for a PARTICULAR customer, and other days there are no long entries to be created for ANY customer.

2. Many days when there is a log entry to be created, it's created by me much later then when the work was performed.  For example, I do a bunch of work Tuesday and Wednesday, but I don't have time to enter all my entries until Thursday.  

2A. In this case, I have to manually go back and edit the log entries with text-editor to adjust the times, dates, and such.

2B. In this case, I have log files with a file-name of THURSDAY (042513a.log) for work entries done on Tues and Wed, so I have to go back and rename the log files for consistency sake (mv 042513a.log 042313a.log).  ** I know this is not a requirement of the program, but I like to have the log filenames consistent with the dates contained in them.

All these I admit are human error -- but as a small business owner, I just can't always get to the log entries every day.

To overcome this, the manual solution would: at the beginning of each day, create a new log entry -- regardless of work to be performed and updated later.  This would serve as sort of a place holder.

However, I can't commit myself to always create a log entry for every day either.  Again, human error.

Is what I would like to be able to do is create a new log entry, every single day, automatically.  I would then have a growing log dir of daily log entries (files) for ever day of the week, most blank but some would then contain data that I enter later-- either at the end-of-day or on a day I have downtime and can commit to administrative work.

My thought is I could probably schedule a cron job do to this, but i'm not completely sure how I would go about auto-populating the incremental ID's, dates, etc.  Second, I don't know if there is a way to do this within ELOG itself, or if there is a built-in mechanism that already covers this.

Has anyone run into this, or solved this problem, or can someone kindly point me in the right direction or how I can implement the daily auto creation of logs?

Thank you very much in advance!

 Hi, 

One question, is possible activate auto-save while write a new "ticket"?

Thanks very much.

Auto-saving does not seem to be working. In the config file, I have the following:

Save drafts = 1
Autosave = 10

but I never see the "auto saving" message or get any other indication that the feature is working.

Am I missing something?

Hello, I have installed ELOG in an Ubuntu 22.04 machine and is working great, but I have found a small bug with Author names.

I have the config set like this for the Author attribute:

Preset Author = $long_name
Locked Attributes = Author

For context, my name is Víctor, which includes the accented "í". When creating a new entry and submitting immediately seems to work well. However, if I create a new entry, save it as draft, go back to the list, and then go to the draft entry, the accented "í" has transformed into "Ã". If I repeat the process, it turns into "ÃÂ", and so on. As I have configured the Author to not be editable, the user cannot fix this manually.

I found a way around this bug by setting

Subst Author = $long_name

Which is okay for us, but might not be for everyone.

In fact I saved this entry as a draft and then on another tab tried to edit it and it wouldn't let me edit because the author name now did not match.

My elog has this config for the author:

Option Author = Filled In Automatically
Preset Author = $Long_name
Locked Attributes = Author

This works as intended: when you submit a new entry, the author name is filled in automatically and cannot be changed.

However, when Alice wants to post a reply to an entry the Bruce has made, the preset author name does not say Alice, it says Bruce. I haven't been able to find out how to change this (other than make the author name editable). Even when Author isn't configured as as locked attribute, it still displays the original author's name.

How can I get this to work like I want/need to?

Hi,

how can i make the author field read only on new postings? It should take the value from $long_name after login and without login there is no way to make new postings.

This is a part of my elogd.cfg

[global]
.......

Logfile = elogd.log
Logging level = 3
Login expiration = 24
Password file = ./passwd
.......

[Informations]
.......

Logout to main = 1
Logbook tabs = 1
Guest menu commands = Back, Find, Login, Help
Guest find menu commands = Find, Select, Login, Help


Preset Author = $long_name
Attributes = Author, Subject
Required Attributes = Author, Subject
........

Thanks Brassmann

Hi 
I followed copied the example config provide to run on my server .
Apparently , the author field was blank when i do a reply .
I was hoping to get it to be the actual reply author.
Just like the way the forum is done up.
Please help ..

Are you using Remove on reply option ? 

regards