No Code Attached Yet
avatar Teo-Mo80
Teo-Mo80
1 Nov 2025

Steps to reproduce the issue

In the session manager settings, set the database and session lifetime to 60. The session closes normally. The problem is that on the Joomla administration side, the logged in users module continues to track expired sessions. I've been experiencing this problem since Joomla version 5.4. This didn't happen in previous versions.

Image

Image

Expected result

Closed user sessions should not appear

Actual result

Expired user sessions remain visible in the form

System information (as much as possible)

Joomla 5.4

Additional comments

avatar Teo-Mo80 Teo-Mo80 - open - 1 Nov 2025
avatar joomla-cms-bot joomla-cms-bot - change - 1 Nov 2025
Labels Added: No Code Attached Yet
avatar joomla-cms-bot joomla-cms-bot - labeled - 1 Nov 2025
avatar Teo-Mo80 Teo-Mo80 - change - 1 Nov 2025
The description was changed
avatar Teo-Mo80 Teo-Mo80 - edited - 1 Nov 2025
avatar alikon
alikon - comment - 2 Nov 2025

if you set and enable the SessionGC task plugin with the same session time, should solve your issue i guess
can you try and report back ?

avatar alikon alikon - change - 2 Nov 2025
Labels Added: Information Required
avatar alikon alikon - labeled - 2 Nov 2025
avatar heelc29
heelc29 - comment - 2 Nov 2025

if you set and enable the SessionGC task plugin

... maybe the task is not running - similar #46308 and #46378

avatar Teo-Mo80
Teo-Mo80 - comment - 2 Nov 2025

@alikon, The sessiongc plugin is enabled and set up as you intended, I think. I can't figure out how to set the session duration because there isn't the dedicated field.

Image

Image

avatar richard67 richard67 - change - 3 Nov 2025
Labels Removed: Information Required
avatar richard67 richard67 - unlabeled - 3 Nov 2025
avatar Teo-Mo80
Teo-Mo80 - comment - 3 Nov 2025

@alikon With the help of an ITA forum user, I understood what you meant.
The sessionGC activity was already enabled. It was set to 24 hours.
I still made the change you suggested, as you can see in the images, but the problem persists.

Image

Image

Image

I see that the last check performed is stuck on this date, it seems that the active system has not performed any further checks since then.

Image

Add a Comment

Login with GitHub to post a comment