Dan Horne wrote:
Hiwhen running my C::A app as a mod_perl registry script, CGI::Application::Plugin::DevPopup doesn't popup unless the code explicitly sets the environment variable: BEGIN { $ENV{'CAP_DEVPOPUP_EXEC'} = 1; } That is, both the SetEnv and PerlSetEnv config settings seem to be ignored. The popup works when the script is run as a standard CGI. The standard Apache printenv script run as a CGI and under mod_perl verifies that CAP_DEVPOPUP_EXEC is set.
I've tested this on my demo site, running mod_perl 1.29 under apache 1.3. Both SetEnv and PerlSetEnv work as you'd expect: the code doesn't need to set the env var explicitly.
Am I misunderstanding something?
When do you set those in your apache config? Do you preload the module(s) with a startup script or a PerlModule directive prior to setting the env var?
The important thing here is that the devpopup module checks the env var at import() time, which means that it should be set prior to use() being executed.
I'll have a look under a more recent version of mod_perl in the mean time. Rhesa --------------------------------------------------------------------- Web Archive: http://www.mail-archive.com/[email protected]/ http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2 To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
