Just to illustrate what perin said, i ran your TT template through the tpage command line tool, cleaned up some extraneous tag attributes and used the output for a CGI test script. Feel free to run this on your own:
use strict;
use warnings;
use Data::Dumper;
use CGI::Pretty qw(:standard);
print header;
print while <DATA>;
print pre( Dumper { CGI::Vars() } );
__DATA__
<form method="post" action="?rm=page3">
viewer:
<input type="text" name="view" size="10" /><br/>
phone:
<input type="text" name="phone" size="10" /><br/>
<input type="submit" name="cm" value="login" />
</form>
Or test it out here: http://unlocalhost.com/cgi-bin/post_get.cgi -- notice how your run mode parameter goes to a ... different place. Interestingly enough, i really thought that switch from POST to GET would solve the problem, but it does not. You have to pass a hidden param.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|