Ron Savage wrote:
Hi Richard

On Fri, 2008-11-21 at 13:09 +0000, Richard Jones wrote:
Richard Jones wrote:

[..]

Then, bringing back all the plugins that Titanium uses one by one until it broke again, CAP::ErrorPage is the one responsible. Presumably there is something in there that causes the session to be retained in a persistent env?
Just found another one: CAP::DebugScreen

Please publish the exact version numbers of the modules you have
problems with.


The two principal ones:
  CAP::ErrorPage   1.12
  CAP::DebugScreen 0.06
  Titanium         1.00 - only due to above 2

Also culpable:
  my custom SIG{__DIE__} handler - pre-alpha ;)

The rest:
  CGI                 3.37
  CGI::Application    4.20
  CGI::Session        4.38
  CAP::Session        1.03
  CGI::Session::Flash 0.01
  CAP::Flash          0.01
  CAP::AutoRunmode    0.15
  CAP::DBH            4.00
--
Richard Jones

#####  CGI::Application community mailing list  ################
##                                                            ##
##  To unsubscribe, or change your message delivery options,  ##
##  visit:  http://www.erlbaum.net/mailman/listinfo/cgiapp    ##
##                                                            ##
##  Web archive:   http://www.erlbaum.net/pipermail/cgiapp/   ##
##  Wiki:          http://cgiapp.erlbaum.net/                 ##
##                                                            ##
################################################################

Reply via email to