Re: Unable to enter/edit time in user defined $date field?, posted by Stefan Ritt on Tue Mar 22 13:46:57 2005
|
> 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...
|
|
Re: Unable to enter/edit time in user defined $date field?, posted by mark james on Tue Mar 22 23:27:21 2005
|
Stefan,
Oh. OK. I will keep tuned. It would be quite useful to have.
|
|
Re: Unable to enter/edit time in user defined $date field?, posted by Stefan Ritt on Wed Mar 30 11:07:08 2005
|
I implemented a "datetime" option which does exactly what you want. All you
need is a
|
|
Re: Unable to add user, posted by Stefan Ritt on Mon Aug 8 08:26:11 2022
|
I recommend to clear all your browser cookies for the elog server. Sometimes an old cookie confuses the
access mechanism.
|
|
Re: Unable to add user, posted by Uwe Vollbracht on Mon Aug 8 14:06:28 2022
|
Thanks for answering. Just tried your suggestion with different browsers
(firefox, chrome, brave) but the error message still appears when adding a
|
|
Re: Unable to add user, posted by Konstantin Olchanski on Mon Aug 8 20:52:17 2022
|
> Error: Command "config" is not allowed for user ""
Could it be related to the error messages thrown by "activate user"? see
|
|
Re: Unable to add entries with command line elog.exe with SSL, posted by Antonio Bulgheroni on Mon Aug 12 13:11:54 2019
|
Any news for my problem?
Your help is very much appreaciated!
thanks :) |
|
Re: Unable to add entries with command line elog.exe with SSL, posted by Andreas Luedeke on Wed Aug 14 13:25:15 2019
|
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 |