- Edited
This would only affect a system that is using the SystemSessionHandler. Your system should be using database session storage which is AbstractSessionHandler
.
This commit was added to continue to allow systems on 1.6.x (released circa 2009) to be able to upgrade to the latest releases. You see, 1.6.x didn't have the concept of database session storage; this was introduced in later versions. So when you are upgrading from 1.6.x to the latest your 1.6.x database won't have the proper session tables so you still need to use the system session storage until the upgrade is complete. Once upgrade completes then it switches to using the database storage which is the abstract session storage backend.
You can see where we set system
or the configured backend in the config file or default to database
here:
All that to say I really don’t think this is the cause of your issue.
Cheers.