Re: [SM-DEVEL] Custom session handler errors with squirrelmail-20071111_0000-SVN.devel.tar.gz

[Tomas K. <to...@us...>]

> Hi,
>
> I very recently switched to a database backed custom session handler,
> which promptly broke my 1.5.1 SquirrelMail. After reviewing the svn
> notes, I downloaded squirrelmail-20071111_0000-SVN.devel.tar.gz which
> includes patch 12756 by pdontthink.
>
> This hasn't fixed the problem, though.
>
> As referenced in the commit message, I'm using to auto_prepend_file to
> load my custom session handler.
>
> auto_prepend_file = /conf/pgsql_session_handler.php
>
> The rest of my changed session variables as set in php.ini are:
>
> session.save_handler = user
> session.save_path = php_sessions
> session.use_cookies = 1
> session.name = WCAASESSID
> session.auto_start = 0
> session.cookie_lifetime = 86400
>
> pgsql_session_handler.php contains the session handling functions and
> the  following code:
>
> /* Register the session handling functions with PHP. */
> session_set_save_handler(
>      'pgsql_session_open',
>      'pgsql_session_close',
>      'pgsql_session_read',
>      'pgsql_session_write',
>      'pgsql_session_destroy',
>      'pgsql_session_gc'
> );
> session_start();
> ?>
>
> I followed the directions coded in src/init.php and added my
> custom_session_handlers array definition to config/config_local.php.
>
> When I attempt to login, I simply get a blank page, with no error
> message generated to the logs by php.
>
> The custom session handler is working fine with our inhouse apps and has
> eliminated some of the weird loss of session variable errors.
>
> Any suggestions would be greatly appreciated!

Don't start session in auto prepend. Set session params and allow
SquirrelMail to start session.

Don't set session.name in auto prepend. Set session name in SquirrelMail
configuration.

I think your white page is 'Failed to initialize storage module: user'
error. session_start() is called after session_destroy().

-- 
Tomas