Good day,

I have 2 logbooks. The main one and the one for the archived entries.

I can make a "move to" command in the main one witch will bring the drop down for the archive. (working perfect).

I was wondering if it is possible to make a "custom" move to in witch I can directly specify the destination logbook, hide the drop down and rename the button.

The main objective is to make a button called "Archive" witch the users only have to press to move the selected entries.<

I know I can make some custom command in list view ie :<a href="?xxx=xxx1|xxx2">zzz</a> so I was wondering if the same is possible and if so, can you guide me on the syntax ?

Thanks for your help :)

 G'day everyone.

Looking for some input on this idea.

I work for an organization which uses elog extensively for day to day operations.

In several of our logbooks we use a "location" attribute where we would enter an address or intersection.

I am working with the google places api and am able to create the auto complete form in a separate html page, but am interested if anyone has a good direction how i could change the input box into the google map autocomplete search box.

I have the code already for the api search box. but when i add it to the config it doesn't really do anything different.

Attached is the html file i setup with the api code.

the autocomplete works great, now i just want it to work in elog.

Any help is much appreciated!

And perhaps the Elog Powers that be might be interested in making it a function down the road? :)

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!

The ELOG repository has been moved from Subversion to GIT. While the old repository will be visible for some time, all new development is done on the GIT repository. To download the repository, do a

git clone https://bitbucket.org/ritt/elog.git
git clone https://bitbucket.org/tmidas/mxml.git


or access it online at https://bitbucket.org/ritt/elog/

/Stefan 

Hi Barend,

Cheers, Andreas

Workaround: you can modify your old entries and add a leading zero to all entries where your specific date field starts with a '9'.

Stefan: you should fix it at least well before 20-Nov-2286 18:46:40, when the same bug strikes again!

Hi there, In the "Find" page, I changed the default of the "Show last" drop down box in the Entry Date section from the (unstated) "All time" to "Day", and added back in an "All Time" option at the very bottom.  This gives a default of searching the last day, and one has to think and select the period of time to search back on.

I did this on my 2.9.2-2475 version, recompiled and it works.  Two lines of code changed and even my cr*ppy coding was up to the task.  I don't know if Stefan would want to put this into the Master copy (I'll forward the changes if you want Stefan, but it's pretty easy if I can do it), but if you can edit and recompile (Eoin) I can tell you which to lines for immediate functionality.  Back up everything first, though!