> I have defined a new field called "Record Date" to accept the dates from a
> previous logging system. I am not too concerned with the timestamp
> associated with these old imported entries. But for new entries...
> There is no way I am able enter/edit the time into my new field. They all
> show as having a time of 12:00. What am I doing wrong? Here is a portion of
> my config

Date is "date", and not "date-time" unfortunately. There is no way right now to
enter a time. I plan however to add a new format "datetime", which allows that
option. So stay tuned.

- Stefan

Stefan,

Oh. OK. I will keep tuned. It would be quite useful to have.

Mark
> > I have defined a new field called "Record Date" to accept the dates from a
> > previous logging system. I am not too concerned with the timestamp
> > associated with these old imported entries. But for new entries...
> > There is no way I am able enter/edit the time into my new field. They all
> > show as having a time of 12:00. What am I doing wrong? Here is a portion of
> > my config
> 
> Date is "date", and not "date-time" unfortunately. There is no way right now to
> enter a time. I plan however to add a new format "datetime", which allows that
> option. So stay tuned.
> 
> - Stefan

I implemented a "datetime" option which does exactly what you want. All you
need is a

Type Record Date = datetime

in your config file. The new option is present in version 2.5.8-2 and ready to
download.

I recommend to clear all your browser cookies for the elog server. Sometimes an old cookie confuses the
access mechanism.

Stefan

Thanks for answering. Just tried your suggestion with different browsers
(firefox, chrome, brave) but the error message still appears when adding a
new user.

By the way, i justed noticed that if you click "back" followed by "cancel" you
enter the logbook as the user you just added. It seems that although elogd
throws an error, the user is added. Weird.

Since most of our users don't trust open source software, the error message
will only confuse them. So, is there any way to avoid this message from
appearing?

Perhaps a few words about our use case:
We are a german non profit organisation in disaster control. Since 2007 we use
elog as mobile mission journal in our unit. We adapted elog to run from
usb-stick, so all our first-responders have to do is to plug it into a laptop
and they are ready to go.
We also hand the adapted installation to other organisations like local fire
department or red cross units and offer them a short (2 hour) course on how to
use it. Since the windows-release is the most requested, it would be confusing
for them if an error message appears every time a new user is added.

So if you have any further ideas, I would appreciate that.

Uwe

>       Error: Command "config" is not allowed for user ""

Could it be related to the error messages thrown by "activate user"? see
https://elog.psi.ch/elogs/Forum/69479

K.O.

Any news for my problem? 

Your help is very much appreaciated! 

thanks :)

I am using SSL with ELOG and it works fine with the "elog" executable. I am no expert on SSL, but I can provide my two cent what you could try, maybe it helps:

• SSL desires to run on the port 443 - I have no idea if you can force it to run on an arbitrary port, it might be possible. But does it make sense?
• Certificates are checked against the provider of the certificate. I guess this works fine from your web browser? Or did you just add a security exception?
• Has the installed "elog.exe" been compiled with SSL support on?