It would help if you post the code for how the other modules use CGI.pm. It's tough to know what could be causing this, but here's one guess:
POSTed data is contained in STDIN. Once read, it's gone. If your other modules do not use this data (and assuming you're using the object-oriented version), you can instantiate their CGI objects as follows:
The empty curly brackets are a hashref that CGI.pm will look for the param data in instead of $ENV{QUERY_STRING} or STDIN, thus preserving the data in STDIN for your original script.my $q = CGI->new({});
CGI.pm will read the contents of STDIN as soon as a CGI object is instantiated or a param() call is made with the function oriented version. If either of these happens before your main program instantiates the object or makes the call, your main script will not have access to the POSTed data.
Cheers,
Ovid
Join the Perlmonks Setiathome Group or just click on the the link and check out our stats.
In reply to (Ovid) Re: CGI.pm not returning POSTed param w/mod_perl
by Ovid
in thread CGI.pm not returning POSTed param w/mod_perl
by voyager
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |