- π©πͺGermany Anybody Porta Westfalica
+1 on this. Would absolutely make sense to track if someone was logged out. This should be configurable.
- π¬π§United Kingdom aaron.ferris
aaron.ferris β made their first commit to this issueβs fork.
- Open on Drupal.org βCore: 9.5.x + Environment: PHP 7.4 & MySQL 5.7last update
11 months ago Waiting for branch to pass - Open on Drupal.org βCore: 9.5.x + Environment: PHP 7.4 & MySQL 5.7last update
11 months ago Waiting for branch to pass - Open on Drupal.org βCore: 9.5.x + Environment: PHP 7.4 & MySQL 5.7last update
11 months ago Waiting for branch to pass - π¬π§United Kingdom aaron.ferris
Raised an initial MR for this, open to suggestions to where else we want to log events but ive replaced the @todo in the codebase.
Followed the Core user module approach for the log entry, wording etc, I did toy with the idea of including more info, session ID etc but didn't know if we felt that would be worth it.
- Status changed to Needs review
11 months ago 5:29pm 25 April 2024 - Open on Drupal.org βCore: 9.5.x + Environment: PHP 7.4 & MySQL 5.7last update
11 months ago Waiting for branch to pass - π©πͺGermany Anybody Porta Westfalica
Really nice work @aaron.ferris, thank you! :)
Regarding your comments I agree it wouldn't make much sense to log the other variables in that function.
What might be improved:$this->loggerFactory->get('session_limit')
could be set as $this->sessionLimitLogger in the constructor. That would be more typical.- The username could be put more in front of the message
- It would be great to log the session limit (count) that caused the logout, which would be helpful for debugging but also to understand why exactly the user was logged out
But anyway, the current state is already better than the @todo before :D
- π¬π§United Kingdom aaron.ferris
Thanks for the feedback, ill get onto those points.
- Assigned to aaron.ferris
- Open on Drupal.org βCore: 9.5.x + Environment: PHP 7.4 & MySQL 5.7last update
11 months ago Waiting for branch to pass - Status changed to Needs work
11 months ago 2:24pm 29 April 2024 - π©πͺGermany Grevil
LGTM! The only thing missing is an update hook prepopulating the new "session_limit_log_events" config with the default value "false". Otherwise, "session_limit_log_events" will be null for already existing site installations.
- Open on Drupal.org βCore: 9.5.x + Environment: PHP 7.4 & MySQL 5.7last update
11 months ago Waiting for branch to pass - Status changed to Needs review
11 months ago 3:54pm 29 April 2024 - Issue was unassigned.
- Status changed to RTBC
11 months ago 7:21am 30 April 2024 - First commit to issue fork.
- Open on Drupal.org βCore: 9.5.x + Environment: PHP 7.4 & MySQL 5.7last update
11 months ago Waiting for branch to pass -
VladimirAus β
committed 3fb97195 on 2.x authored by
aaron.ferris β
Issue #2674244 by aaron.ferris, johnennew, Anybody, Grevil: Add useful...
-
VladimirAus β
committed 3fb97195 on 2.x authored by
aaron.ferris β
- Status changed to Fixed
11 months ago 1:30pm 6 May 2024 - π¦πΊAustralia VladimirAus Brisbane, Australia
Great work! Thank you all! π°
Committed! Automatically closed - issue fixed for 2 weeks with no activity.