I'm no techy/coder but many on the forum in the past have said use "file" instead of "database". The one drawback of using database is as you found; the session table can get quick big, very quickly.
I think the "left behind" sessions can be caused by, for one reason, the end-user closing their browser before actually logging off (and many other reasons).
Emptying the session table on a regular basis is the best way, e.g. with a scheduled CRON job or doing so manually. Of course, that will auto-log out everyone since you have no control over who you log out.
Login-as-user is a plugin that allows an administrator/super user to effectively log in as any other user. I forgot what it was for.
You could suggest an improvement (on Github) e.g. to warn about the session table size (?). Maybe it just needs to be a small addition or a admin module you can add to the dashboard that simply says "session table (approx size): XYZ KB/MB"
I think the "left behind" sessions can be caused by, for one reason, the end-user closing their browser before actually logging off (and many other reasons).
Emptying the session table on a regular basis is the best way, e.g. with a scheduled CRON job or doing so manually. Of course, that will auto-log out everyone since you have no control over who you log out.
Login-as-user is a plugin that allows an administrator/super user to effectively log in as any other user. I forgot what it was for.
You could suggest an improvement (on Github) e.g. to warn about the session table size (?). Maybe it just needs to be a small addition or a admin module you can add to the dashboard that simply says "session table (approx size): XYZ KB/MB"
Statistics: Posted by AMurray — Tue Nov 26, 2024 10:07 pm