[Understanding Confirmation] Sessions, expiration and session.gc_probability
-
I would like confirmation that I am understanding the following correctly.
While using WP Session Manager, I am seeing MANY stale sessions that do not delete themselves from the database. I am in an Ubuntu hosted environment where session.gc_probability is set to zero. This appears to be a default thing for Ubuntu/Debian. For those environments, expired session cleanup is done by way of a cron task – BUT those environments assume file-based sessions, not database sessions (such as WP Session Manager provides).
For such a scenario, would I be correct that I need to do session cleanup for expired sessions myself? Probably a short cron task that calls DataManager::clean()?
-
You are likely correct. The call would be something like:
`
$handler = new \EAMann\WPSession\DatabaseHandler();
$handler->clean();
`That being said, doing this directly is entirely untested at the moment. I’ll queue up an issue on GitHub to add a cron cleanup for the DB handler directly to WordPress in the next release.
- The topic ‘[Understanding Confirmation] Sessions, expiration and session.gc_probability’ is closed to new replies.
