Post using html form --> not solved ... , posted by Hayg Guler on Wed Jan 4 11:00:01 2023
|
Dear All,
Just want to come back to this issue I faced.
In the config file, I call an html form to format input. The way I call the html file inside my config file is described below. |
Post using html form , posted by Hayg Guler on Thu Oct 20 16:52:09 2022
|
Dear All,
we are trying to post from an HTML form, as included in our config file :
|
Post appearing twice, posted by Dan Chitwood on Fri Sep 23 19:23:26 2005
|
We are having trouble on our logbook with posts appearing twice. Both posts contain the same ID number, time, etc. This most often occurs when the e-log
entry is being written for an extended period of time (ie. more than 30 minutes), but I don't know if that is the root cause of the problem. It may also
be related to posts that are edited after an initial posting. Could this be due to an improper setting in our config file? |
|
Possible to submit entries by email to logbook, posted by thorsten kamps on Fri Oct 17 16:59:42 2008
|
Hi, thanks to everyone involved for giving us the elog.
A question:
Is it possible to submit entries to an elog on a remote machine by email? |
|
Possible to sort attribute chronologically? , posted by Dennis Seitz on Tue Jan 29 04:25:11 2008
|
Hi,
We've defined a "LastEdit" attribute for some of our logs so that we can indicate that an entry has been revised, and when that was done.
|
Possible misuse of email headers Message-Id and In-Reply-To, posted by fbretel on Wed Feb 8 16:38:15 2017
|
Hi,
As mentionned before, we happen to fail to receive email messages related to updates on
elog entries at our site. My understanding is that the SMTP header Message-Id MUST be unique for each email message. Whereas all elogd email |
Possible bug in elogd execute_shell, posted by Nigel Warr on Fri Feb 26 08:38:06 2016
|
I was just playing around with gcc6's new feature for warning about misleading indentation (which can often hide real bugs) and I think it found
one in elog-3.1.1-1 at src/elogd.c:22538. Here there is an if statement, which looks as though it should be inside a loop, but it isn't.
The code is: |
Possible bug in elogd execute_shell, posted by Nigel Warr on Fri Feb 26 08:47:22 2016
|
I was just playing around with gcc6's new feature for warning about misleading indentation (which can often hide real bugs) and I think it found
one in elog-3.1.1-1 at src/elogd.c:22538. Here there is an if statement, which looks as though it should be inside a loop, but it isn't.
The code is: |