?
avatar gee2803
gee2803
5 Sep 2016

Steps to reproduce the issue

Since Joomla 3.6.2 I am facing the following problem: Some (not all) users log in and won't get a correct session entry in the database. They appear as offline but can use the site as a normal registered user. I am using JomSocial but the problem affects also logins via Joomla login module. I can not reproduce why and never faced the problem myself but I many users report it and I have a much higher guest count now.

Expected result

Users should be logged in in session table

Actual result

Many users are just shown as offline

System information (as much as possible)

Database Version 5.5.5-10.0.25-MariaDB-0+deb8u1
Database Collation utf8_general_ci
Database Connection Collation utf8mb4_general_ci
PHP Version 5.6.24
Web Server Apache
WebServer to PHP Interface cgi-fcgi
Joomla! Version Joomla! 3.6.2 Stable [ Noether ] 4-August-2016 23:41 GMT
Joomla! Platform Version Joomla Platform 13.1.0 Stable [ Curiosity ] 24-Apr-2013 00:00 GMT

avatar gee2803 gee2803 - open - 5 Sep 2016
avatar C-Lodder
C-Lodder - comment - 5 Sep 2016

Please test this patch: #11691

avatar brianteeman brianteeman - change - 5 Sep 2016
Priority Critical Medium
avatar brianteeman
brianteeman - comment - 5 Sep 2016

Reset priority according to the documented standards https://docs.joomla.org/Priority


This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/11933.

avatar gee2803
gee2803 - comment - 5 Sep 2016

@C-Lodder: Thank you very much. I can confirm that the patch solves my problem, too. I hope this will be in the next Joomla update.
@brianteeman: Sorry for the wrong priority setting. I am new here and it was very critical to me, because it looks to new guests like an empty community. I read the guideline now.


This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/11933.

avatar brianteeman
brianteeman - comment - 5 Sep 2016

closing as resolved by #11691

avatar brianteeman brianteeman - change - 5 Sep 2016
Status New Closed
Closed_Date 0000-00-00 00:00:00 2016-09-05 13:10:06
Closed_By brianteeman
avatar brianteeman brianteeman - close - 5 Sep 2016
avatar brianteeman
brianteeman - comment - 5 Sep 2016

@gee2803 yes the fix from #11691 will be in the next release

Add a Comment

Login with GitHub to post a comment