Feature #40418
Add an option to flow3:cache:flush thats keeps user sessions active
Added by Martin Brüggemann over 8 years ago.
Updated over 6 years ago.
Description
At the moment all sessions are being flushed with a
./flow3 flow3:cache:flush
There should be an option to flush all caches except the session storage/cache. Otherwise everytime you deploy a fix to your FLOW3 based SaaS project, all your customers loose their sessions and will have to relogin.
Maybe a small option like
./flow3 flow3:cache:flush --keepSessions
would do the trick.
- Target version set to 2.0 beta 1
- Status changed from New to Under Review
- Assignee set to Karsten Dambekalns
- Status changed from Under Review to Rejected
- Priority changed from Must have to Won't have this time
Closing according to comments on https://review.typo3.org/#/c/15846/
Martin Brüggemann, Nov 8:
[...] Active Sessions should be removed by default when you flush the flow cache with the --force option.
The fact that flow loggs you out when deploying a new release with flow depends on the session save path.
By default flow sets an internal temporary path as session save path and if you deploy a new release with Surf
there's a new (empty) temporary path without the active sessions -> everyone is logged out!
SOLUTION: Just set a global session save path with TYPO3.Flow.session.PhpSession.savePath (f.e. /tmp)
and your sessions will stay active even if you deploy new releases with surf.
As soon as commit request #15942 is implemented flushing the cache will automatically flush the session
cache because then the session handling will be completley based on the internal Flow caching backend.
- Status changed from Rejected to Needs Feedback
- Assignee deleted (
Karsten Dambekalns)
- Priority changed from Won't have this time to Could have
- Target version deleted (
2.0 beta 1)
Hi all,
the solution above does not work any longer, because there is no PhpSession in Flow > 2.
What do you think about extending the FileBackend so that the path is configurable?
Then you could add
Flow_Session_Storage:
backendOptions:
cacheDirectory: 'some/other'path'
in your Caches.yaml in order to achieve the same as above?
Does that make sense?
Also available in: Atom
PDF