$g_session_handler
Posted: 12 Dec 2013, 17:14
Hi,
I recently migrated my web servers to a new hosting. The new setup is using a load balanced environment.
This means that the session handler can't use the default 'php' setting. Trying to do so results in numerous errors like this:
One solution for this issue is to store the sessions in the database ($g_session_handler='adodb';), rather than on the web server ($g_session_handler='php';).
I've updated mantis to the latest stable version (1.2.15) and updated the config to store the sessions in the database.
Once I opened mantis, I got error #2700 (invalid session handler).
Doing some digging, I found that only $g_session_handler='php'; is implemented.
Yet the documentation mentions the options for storing in the database or memcaching.
Are there plans to implement the other session handlers or are they missing by error?
If they are not yet implemented, as the code suggests, may I suggest to remove the option for the session handler from the documentation so others don't have to lose time on investigating why setting the configuration option results in errors?
Thank you
I recently migrated my web servers to a new hosting. The new setup is using a load balanced environment.
This means that the session handler can't use the default 'php' setting. Trying to do so results in numerous errors like this:
Code: Select all
APPLICATION ERROR #2800
Invalid form security token. This could be caused by a session timeout, or accidentally submitting the form twice.I've updated mantis to the latest stable version (1.2.15) and updated the config to store the sessions in the database.
Once I opened mantis, I got error #2700 (invalid session handler).
Doing some digging, I found that only $g_session_handler='php'; is implemented.
Code: Select all
switch( utf8_strtolower( $g_session_handler ) ) {
case 'php':
$g_session = new MantisPHPSession( $p_session_id );
break;
case 'adodb':
# Not yet implemented
case 'memcached':
# Not yet implemented
default:
trigger_error( ERROR_SESSION_HANDLER_INVALID, ERROR );
break;
} Are there plans to implement the other session handlers or are they missing by error?
If they are not yet implemented, as the code suggests, may I suggest to remove the option for the session handler from the documentation so others don't have to lose time on investigating why setting the configuration option results in errors?
Thank you