Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 726 of 808  Not logged in ELOG logo
ID Date Icondown Author Author Email Category OS ELOG Version Subject
  67456   Mon Feb 25 19:10:07 2013 Idea Francois CukierMonsieurdindon@gmail.comQuestionWindows2.9.2Edit from summary view

 Good day,

 

I was wondering (and I searched for :) ) a way to directly edit an entry while in summary view instead of having to first click on the entry then click on Edit...

I mean, in summary view, every row entry is clickable to access the entry itself (except email witch open email client), so instead to open it, can it be edited directly ?

Is it possible ?

  67457   Mon Feb 25 19:12:47 2013 Idea Francois CukierMonsieurdindon@gmail.comQuestionWindows2.9.2Search result background color

 Is it possible to change the "yellow" background color when running a search ? (I looked in the css, there is nothing...) 

Couldn't find any syntax for elogd.cfg

Thanks for your help :)

  67460   Wed Feb 27 13:43:00 2013 Idea Francois CukierMonsieurdindon@gmail.comQuestionWindows2.9.2Custom "move to"

 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 :)

  67480   Fri Apr 26 19:00:07 2013 Idea Garret Delarondegarret.delaronde@gmail.comQuestionWindows2.9.2Google Places API AutoComplete

 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? :)

Attachment 1: Test_Search.html
  67483   Fri Apr 26 22:29:50 2013 Idea Ryan Blakesleerb@blakesys.netQuestionLinux2.5.2Auto-Generate new logbook daily

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!

 

 

 

  67551   Wed Jul 24 02:19:17 2013 Idea Stefan Rittstefan.ritt@psi.chInfoAllALLELOG moved to GIT

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 

  67585   Wed Oct 16 16:53:55 2013 Idea Andreas Luedekeandreas.luedeke@psi.chBug reportWindows2.9.2Re: Importing XML/CSV

Barend wrote:

Andreas Luedeke wrote:

Barend wrote:
Hi Stefan,
I'm experiencing problems importing XML (.csv is not working at all for me).
My logbook contains 3 date-attributes besides the system DATE (entry time), date-format is defined as %d %b %y.
The XML file hold the date format "DD.MM.YYYY"
- During "preview" I see that all entries are listed.
- During the import I get the "wrong date format" error.
- When I review the Summary, I see that only the first XML entry (all 3 date-attributes hold a date) was imported.
- When I try to re-import the XML from the second entry (after removing the 1st entry from XML - this second entry hold NO date-value on one of the date-attributes) the elogd.exe crashes and I get the "Service Temporarily Unavailable" error page.
- When I try to re-import the XML from the modified second entry (after removing the 1st entry from XML - this second entry holds date-value on all of the date-attributes) the elogd.exe crashes and I get the "Service Temporarily Unavailable" error page.

Any suggestion what could be wrong? Is it the missing date-value?

 Can you post your elog configuration file (elog.cfg)?

 
Detect language » English
 

 Hi Andreas,

I had to filter-out some other logbook. Please find attached the configuration section for the affected logbook "UMOWY".

Looking forward to your review.

Regards, Barend

Hi Barend,

I can confirm that this is a bug of the ELOG import function: if you have a field that is defined as type "date" or "datetime", then elogd requires the value of the field to be of a matching format.
It is not even allowed to omit the time in "datetime" format. If the field is not required in an entry, then it is therefore possible to create an entry that cannot be imported.
I've attached a minimal example elogd.cfg and XML import file to reproduce the problem.
I'm afraid you'll either need to wait for a patch, or you can add dummy dates for all your empty date fields in the XML import file. Just do a "replace all" with your favourite editor; in my example you would e.g. replace all "<D></D>" strings with "<D>01-01-1970</D>" before the import.
 
Detect language » English
 

Cheers, Andreas

 
Detect language » English
 
 
Detect language » English
 
Attachment 1: elogd.cfg
[global]
port = 8080

[TestXmlImportOfDate]
Attributes = D
Type D = date
Attachment 2: imp.xml
<?xml version="1.0" encoding="ISO-8859-1"?>
<ELOG_LIST>
	<ENTRY>
		<MID>1</MID>
		<DATE>Mon  07 Oct 2013 11:41:42 +0200</DATE>
		<ENCODING>plain</ENCODING>
		<D>20.10.2012</D>
		<TEXT>ABCD</TEXT>
	</ENTRY>
	<ENTRY>
		<MID>2</MID>
		<DATE>Mon  07 Oct 2013 11:41:43 +0200</DATE>
		<ENCODING>plain</ENCODING>
		<D></D>
		<TEXT>DEF</TEXT>
	</ENTRY>
</ELOG_LIST>
  67705   Wed Sep 17 17:45:18 2014 Idea Andreas Luedekeandreas.luedeke@psi.chInfoAll V2.9.2-24Re: Sort by date prior to 2002

Chris Jennings wrote:

Chris Jennings wrote:

I have an attribute formatted as a date (but not labeled as date) and is sorted as second priority. The sort works fine until I enter a date older than Jan 1st 2002. When I do this it is sorted as the latest. Is this a bug or simply not designed to use dates this old?

Thanks in advance,

Chris

 Sorry, my mistake. The cutoff date is anything before September 9th 2001 does not sort.

I think I remember that this has been discussed earlier: it is a little bug in elogd.
You can see where it comes from if you type in the little command 'date -d "9-Sep-2001 3:46:40" +%s'
Converted to "seconds of the epoche" (seconds since 1970-01-01 00:00:00 UTC) the date "9-Sep-2001 3:46:40" has one digit more than "9-Sep-2001 3:46:39".
Since elog makes a string comparison, suddenly 1'000'000'000 is less than 999'999'999; therefore the wrong sorting.

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!
ELOG V3.1.5-3fb85fa6