Beefy Boxes and Bandwidth Generously Provided by pair Networks
"be consistent"

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
Sorry, I did not realize anything in all caps was unwelcome form. Please forgive me. I shall respond to your questions in order.

When I invoke CGI script 1 via server side HTML, I get the desired and expected output: e.g.
$subject is: {input from HTML form}
$comments is: {other input from HTML form} other words, everything works fine.

When I invoke CGI script 1 via responding to the HTML email which is created by CGI script 2, and thence sent to my AOL client side email account, I get: e.g.

$subject is: {all blank}
$comments is: {all blank}
.......see, I'm expecting the same output results, as the inputs provided for subject and comments are the same (instead I get blanks)

I got the idea to try this after my car was serviced and the service provider sent an email to my AOL email account that contains a satisfaction survey embedded in the body of the AOL email message. Since the service provider's survey worked, I'm inclined to believe the problem is with my code, not the security features on my email client. I hope this gives you a better feel for the problem. If anything still isn't clear, I'm happy to provide more information. Thank you for your patience.

In reply to Re^2: passing CGI form parameters via HTML email by gmacfadden
in thread passing CGI form parameters via HTML email by gmacfadden

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • 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.
Log In?

What's my password?
Create A New User
Domain Nodelet?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others chilling in the Monastery: (5)
As of 2023-12-03 17:09 GMT
Find Nodes?
    Voting Booth?
    What's your preferred 'use VERSION' for new CPAN modules in 2023?

    Results (20 votes). Check out past polls.