Tim Hibbard wrote:
I have created a custom Axkit Provider and I am having problems processing parameters when the form method is POST. However I have no problems when the form method is GET. I was wondering/hoping if anyone could provide any suggestions or feedback. I can use the GET method, but the browsers 'location' looks cleaner when using the POST method.
<snip/>
if ($application eq "award_letter"){
if ($function eq "admin_query"){
my $apr = Apache::Request->new($r);
my $project_number = $apr->param("project_number");
#IF FORM METHOD IS GET THEN THERE IS A PROJECT NUMBER
#IF FORM METHOD IS POST, NO PROJECT NUMBER
}
}
In all AxKit component classes that will access POSTed params, you should use the instance() constructor method, rather than new(). From the mod_perl docs:
"This solves the problem with creating the Apache::Request object twice within the same request - the symptoms being that the second Apache::Request object will not contain the form parameters because they have already been read and parsed."
So, try:
my $apr = Apache::Request->instance($r)
If that doesn't solve the problem, perhaps the other PerlHandler is accessing (and therefore clobbering) the params before AxKit takes over?
Cheers, -kip
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
