I suggest that you start the page in a browser while running a debugger such as FireBug. This will allow you to do two very useful things:
- You can set breakpoints in the JavaScript code, to see what it is doing and where/when it is being called.
- When the page finally submits something to the host, you can see the actual GET/POST that it sent. Never Assume.™
You don’t say whether the JavaScript code is known-good, so let’s assume, until demonstrated otherwise, that it is the actual source of the bug. Let’s assume that the real problem is that the JavaScript either isn’t passing mysample, or that its value is empty. Exercise the code and use FireBug to find the actual POST. If you can see the correct value being passed, only then do you know (but now, you know), that the error is in the Perl software.
-
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.
|
