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.
My point is, even if I am already logged in, each time I try to submit an html form, it sais I am not logged in ...
please refer to the corresponding form to see the screenshots.
Many thanks
Hayg
------->
that is strange since I logged in ...
It seems like when I go in the shift check topic in the elog, it does not get my login id ... is there something coming from the HTML file that should be set in order to get the login from elog ?
see in the attached image : I am logged in but I still need to feed the Author item. And even If I fill it,
And then if I Click on new to write a new filling form, author is not filled as you could see on the second image "Author ?" ...
so I don' see from where appears the problem
| Stefan Ritt wrote: |
|
Probably people have to log in to the logbook before opening the form. I guess the "submit not allowed" comes from the fact that they access the logbook as a guest.
Stefan
| Hayg Guler wrote: |
|
Dear All,
we are trying to post from an HTML form, as included in our config file :
[ShiftCheck]
Comment = Shift Check List (exemple a modifier)
Attributes = Author, D, M, Y, Shift, LasE, LasIris, Q, E, Li, TL, RI
Quick filter = Shift, Author
Options Shift = Morning, Evening, Night
Enable attachments = 0
Show text = 1
Custom new form = /www/Web/htdocs/elog/sites/THOMX/shiftcheck.html
Custom edit form = /www/Web/htdocs/elog/sites/THOMX/shiftcheck.html
Custom display form = /www/Web/htdocs/elog/sites/THOMX/shiftcheck.html
we are facing the following problem when trying to submit :
--> Error: Command "Submit" not allowed
is there something missing in our config file ?
Many thanks in advance
|
|
|
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 :
[ShiftCheck]
Comment = Shift Check List (exemple a modifier)
Attributes = Author, D, M, Y, Shift, LasE, LasIris, Q, E, Li, TL, RI
Quick filter = Shift, Author
Options Shift = Morning, Evening, Night
Enable attachments = 0
Show text = 1
Custom new form = /www/Web/htdocs/elog/sites/THOMX/shiftcheck.html
Custom edit form = /www/Web/htdocs/elog/sites/THOMX/shiftcheck.html
Custom display form = /www/Web/htdocs/elog/sites/THOMX/shiftcheck.html
we are facing the following problem when trying to submit :
--> Error: Command "Submit" not allowed
is there something missing in our config file ?
Many thanks in advance |
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?
Thanks, Thorsten |
|
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.
From our config:
Attributes = Last Edit, etc etc
.
.
.
Preset Last Edit =$date
Locked Attributes = Last Edit
Subst on edit Last Edit = $date
This works fine, but when we sort the LastEdit column, the dates are sorted alphabetically. Is there a way to tell Elog to treat this particular attribute
as a date when sorting? |
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 messages get something like <logbook>-<entryId>@<domain>. See source code. For this header to become unique, there should be a random part in it.
Having the same Message-Id in multiple email messages results in only the first one being delivered on some email systems.
Moreover, elogd sets the In-Reply-To: header in the same manner (<logbook>-<entryId>@<domain>). Which is incorrect because this header relates to email messages, not elog entries, and should contain the email Message-Id of the email message to which it replies, itself handled by the email messaing system. But elogd hasn't received any email messsage in the first place. So I believe this header should simply be dropped.
I think I can provide a pull request on bitbucket for the Message-Id issue, and probably also for the In-Reply-To: if you decide it can be removed.
Cheers |
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:
for (i = 0; i < MAX_ATTACHMENTS; i++)
generate_subdir_name(att_file[i], subdir, sizeof(subdir));
if (att_file[i][0] && strlen(shell_cmd) + strlen(lbs->data_dir) + strl$
< sizeof(shell_cmd) + 1) {
strcpy(p, "\"");
strcat(p, lbs->data_dir);
strlcat(str, subdir, sizeof(str));
strlcpy(str, att_file[i], sizeof(str));
str_escape(str, sizeof(str));
strcat(p, str);
strcat(p, "\" ");
p += strlen(p);
}
and the if statment is accessing the loop variable i but it is actually outside the loop. Presumably, there should be some more curly brackets here. gcc6 gave the warning:
src/elogd.c: In function ‘execute_shell’:
src/elogd.c:22538:10: warning: statement is indented as if it were guarded by... [-Wmisleading-indentation]
if (att_file[i][0] && strlen(shell_cmd) + strlen(lbs->data_dir) + strlen(subdir) + strlen(att_file[i])
^~
src/elogd.c:22536:7: note: ...this ‘for’ clause, but it is not
for (i = 0; i < MAX_ATTACHMENTS; i++)
^~~
|
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:
for (i = 0; i < MAX_ATTACHMENTS; i++)
generate_subdir_name(att_file[i], subdir, sizeof(subdir));
if (att_file[i][0] && strlen(shell_cmd) + strlen(lbs->data_dir) + strl$
< sizeof(shell_cmd) + 1) {
strcpy(p, "\"");
strcat(p, lbs->data_dir);
strlcat(str, subdir, sizeof(str));
strlcpy(str, att_file[i], sizeof(str));
str_escape(str, sizeof(str));
strcat(p, str);
strcat(p, "\" ");
p += strlen(p);
}
and the if statment is accessing the loop variable i but it is actually outside the loop. Presumably, there should be some more curly brackets here. gcc6 gave the warning:
src/elogd.c: In function ‘execute_shell’:
src/elogd.c:22538:10: warning: statement is indented as if it were guarded by... [-Wmisleading-indentation]
if (att_file[i][0] && strlen(shell_cmd) + strlen(lbs->data_dir) + strlen(subdir) + strlen(att_file[i])
^~
src/elogd.c:22536:7: note: ...this ‘for’ clause, but it is not
for (i = 0; i < MAX_ATTACHMENTS; i++)
^~~
|
|