: parameters empty when using
ModPerl::Registry(okay when using ModPerl:PerlRun)...
...snip...
I believe I see the source of your troubles in the code that you
posted. You are creating a closure by using a lexical variable and then
accessing it from within a sub. This is a no-no with any long
Stas,
Replies below:
--
Steve Bannerman
[EMAIL PROTECTED]
44.(0)1865.273866
-Original Message-
From: Stas Bekman [mailto:[EMAIL PROTECTED]
Sent: 05 August 2003 18:07
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: HTTP POST: parameters empty when using ModPerl
]
Subject: Re: HTTP POST: parameters empty when using ModPerl::Registry
(okay when using ModPerl:PerlRun)...
Steve Bannerman wrote:
All,
I apologize if this has already been covered...I looked at the archives
since May but couldn't see anything covering this (there were related items
PROTECTED]
Subject: RE: HTTP POST: parameters empty when using ModPerl::Registry
(okay when using ModPerl:PerlRun)...
try
CGI-initialize_globals();
at the begining of the script but before you use params
if you are depending on the 'use CGI' statement to initialize
your params (like a command line
On Wed, 2003-08-06 at 04:50, Steve Bannerman wrote:
However, it doesn't really explain why the root problem exists. The way I
think about it, the creation of a new CGI object should create a new set
of slots for instance data.
That would make sense, but very little about CGI.pm actually works
