Admin post form (3)

1 Name: trollfag : 2007-05-11 06:45 ID:lXiERqXL [Del]

Hi, it looks like there is a bug with admin message posting form. This is how admin post template in defined:

use constant ADMIN_POST_TEMPLATE => compile_template(MANAGER_HEAD_INCLUDE.q{
<tr><td class="postblock"><const S_NAME></td><td><input type="text" name="name" size="28" /></td></tr>
<tr><td class="postblock"><const S_EMAIL></td><td><input type="text" name="email" size="28" /></td></tr>
<tr><td class="postblock"><const S_SUBJECT></td><td><input type="text" name="subject" size="35" />
<input type="submit" value="<const S_SUBMIT>" /></td></tr>
<tr><td class="postblock"><const S_COMMENT></td><td><textarea name="comment" cols="48" rows="4"></textarea>...

The names of variables which will be send to are "name", "email", "subject", "comment".

But then in such requests are processed like this:

elsif($task eq "post")

    my $parent=$query->param("parent");
my $name=$query->param("field1");
my $email=$query->param("field2");
my $subject=$query->param("field3");
my $comment=$query->param("field4");
my $file=$query->param("file");

The names for name, email, subject, comment are "field1" to "field4", so those variables from admin post form aren't in use at all. When I try to make an admin post I get antispam warning (triggering on "name" and "email" fields or something like that, right?) So the question is: Am I getting it right? Should we change admin post form to use "field1", ..., "field4" variables? It was tested on wakaba 3.0.7 and it works. And also sorry for mistakes, I'm not native Engrish speaker.

2 Name: Anonymous : 2007-05-11 17:56 ID:yeesbNF8 [Del]


3 Name: Anonymous : 2007-06-02 12:55 ID:3nBWQrwI [Del]

any idea why?

Name: Link:
Leave these fields empty (spam trap):
More options...