Timeout issues

- MODX Staff
- 10,725 Posts
opengeek Reply #11, 18 years, 2 months ago
Luckily, that’s only one file in MODx 0.9.x!

Take a look at the startCMSSession() function inside of /manager/includes/config.inc.php and that’s the only place you’ll need to modify. I am not sure that will solve the issue with timeouts, but it’s a simple change and worth a try.

Here’s an example of the modified function:
```
	// start cms session
	if(!function_exists('startCMSSession')) {
		function startCMSSession(){
			global $site_sessionname;
			session_name($site_sessionname);
			session_save_path('manager/sessions');
			session_start();
		}
	}
```
Jason Coward
Chief Architect @ MODX
http://www.jasoncoward.com | http://twitter.com/drumshaman | https://github.com/opengeek
- ☆ A M B ☆
- 24,524 Posts
sottwell Reply #12, 18 years, 2 months ago

Nice! Good to know, if writing snippets or what-have-you that mess with the session!

It is a security measure to move your session files elsewhere than the default if you’re on shared hosting (usually /tmp or something) because it’s possible for someone to log in, get his session ID, then get into that shared /tmp folder and mess with his session, giving himself permissions we would prefer he not have.

There is also the issue of hosting that uses cluster technology; you can’t be sure that your user will be accessing the same server at each page request, so in that case you need to use save_session_path().

You’ll need to have some way of clearing out old sessions (maybe those a day or more without activity?) since they won’t be getting deleted and will fill up the filesystem eventually.
Studying MODX in the desert - http://sottwell.com
Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
Join the Slack Community - http://modx.org