Steven, Jesse & Friends,

I'm having a problem using the param() method from CGI::Application as
inherited by CGI::Application::Session and CGI::Application::Login.

Basically, in the following example, I'm having a problem, because
though the internal data reflects a correct value for the
'session_dir' parameter as set below, the param('session_dir) method
returns 'session_dir'.

    * Put the following line in the cgiapp_init() function for your main program app:

        $self->param( 'session_dir' => '/dir/to/save/session/files' );
        print STDERR Dumper($self), "\n"
        unless ( $self->init_session( 'name_of_cookie' ) ) {
            $self->header_type('redirect');
            $self->header_props( -location => 'http://location/of/login.cgi' );
            return;
        }
        

I used Dumper above from my beloved Data::Dumper module to dump $self,
and come up with a correct value for session_dir:

                 '__PARAMS' => {
8<8<8<
                                 'session_dir' => '/tmp/sessions',
...

Which is great, but I can't get the value of 'session_dir'.  Does it
happen with other parameters, not sure...I just checked 'user' and
it's happening for that one too.

I'm using $CGI::Application::VERSION = '2.1'; and the version of the
CGI::Application::Session and Login stff that's up on the site today
(20 Nov 2001).

So, I'm pretty sure there's something wanky with param() not returning
the right value, but I can't figure out why.

i've got to show my client something tomorrow, and I'd love it to
contain the login stuff.  I think this module is cool.  It was easy to
use my AuthenticatedUser.pm, populate my  user object based on the
username passed in on the form, and validate the form password against
the database password. Cake!  Thanks.....er...but what's going on.

Now, it's sleep or beer, then sleep.  I think it's beer, then sleep.

Thanks, folks.

-Eric.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to