Hi,

I'm trying to upgrade ELOG 2.9.2, which I have been used many years, to the new version (3.1.2).

I can't run the new version even from the command line:

Message box appears with message:

What do I do wrong ?

I'm trying to use my old config file. New default config gave the same result :-(

Is it possible for an administator to reset a user's password? 

Thanks,

Val

Sure. Hit "Config", select other user, and click on "Change password".

Stefan

What is the input format expected by the elog client for a required Datetime defined field when inserting a record? (Eg: October 26, 2016 = ? in the field's data parameter).

I have read some prior posts on this and the indication is that the input needs to use epoch time, however even when I enter 1477493161 or 0 the client still flags the variable data as missing. If this is in fact the format I shoud be using then I can provide a sample input and output message to illustrate my problem.

UPDATE:

As I continue to test and troubleshoot this problem I noticed something peculiar: the Datetime defined field that the client is rejecting when I attempt a record insert is listed as a Required attribute. However, when I just remove it from the Required list the record including the epoch time is inserted without any problems.

I am now unsure if my configuration is deficient somewhere, vs a problem with the client program code.

Hi Alan,

I have no idea if this helps but the Date and Time formats in the config file internally interconnect, as I discovered in trying to define them separately.  Define one, and the other is defined.

I only mention this as I spent some hours trying to sort out the issue, only to learn it was a "feature" that Stefan didn't want to correct as it may affect too many others.  I can understand that, and made a different solution to what I wanted to do.

I really appreciate your reply David.

There's only one Datetime defined field that I'm working with so I'm not sure what you mean, if you don't mind elaborating? It sounds interesting.

The only thing I gather right now from what you're saying is that there's essentially two locations where a field can be defined - in the Config file, or via the format of the data itself in the client command - but I could be wrong. 

Yes, this is a known bug of ELOG, see elog:68404

Hello,

Has anyone implemented an email gateway for ELOG, allowing users to submit entries by sending an email?  Granted this should be possible using the elog client binary, but I thought I'd see if I've overlooked any examples or docs first.

Thanks!
Devin

Just incase anyone's interested, we went ahead and wrote a python script to act as an email gateway for ELOG.  If anyone's interested, we'd be happy to share and appreciate any additional improvements.

- You can send a new message to the email address to start a new thread.
- You can reply to messages received from that logbook. If you include the message you are replying to in the body of your message, the reply will be threaded appropriately as a response to the initial message.
- The body of a new message will only include the text/html portion of a MIME message if it's available.
- Attachments work, although we remove spaces and add a random identifier (to avoid collisions) to each filename.
- the Author field is derived using the From address of the email.
- the subject field is derived using the Subject of the email.
- both single and double quotes are preserved in the author, subject, or body of the message

Devin

> Hello,
> 
> Has anyone implemented an email gateway for ELOG, allowing users to submit entries by sending an email?  Granted this should be possible using the elog client binary, but I thought I'd see if I've overlooked any examples 
or docs first.
> 
> Thanks!
> Devin

hello

Is there a way to export logs from elog (for example after I have selected a filter) to txt or csv...

I found the "Download" attribute but this works for only one elog entry...

regards

shame on me, there is a way!

I can search with find and then export as csv file

/alex

Is there a way to enforce password complexity for users?

Either in this version of elog or the newest version?

I'm trying to set up a python rss parser to read the output from my collaboration's elog, however the elog is password protected and I cannot figure out how to have a python scrip get past the login screen.  Is there something obvious I'm missing that will allow a parser to submit a username and password? If that's too python-specific of a question for this audience, then what is the exact security method elog uses, so I can get information on that?  I've read through the documentation and either I don't know what I'm reading (likely) or I'm not looking in the right spot.

I'm trying to set up a python rss parser to read the output from my collaboration's elog, however the elog is password protected and I cannot figure out how to have a python scrip get past the login screen.  Is there something obvious I'm missing that will allow a parser to submit a username and password? If that's too python-specific of a question for this audience, then what is the exact security method elog uses, so I can get information on that?  I've read through the documentation and either I don't know what I'm reading (likely) or I'm not looking in the right spot.