User tests: Successful: Unsuccessful:
When a user changes his profile, the groups data is lost because before saving the new data, the groups property is set to null.
I propose to save the groups property before saving and restore it after.
I use the latest version of Joomla (3.3.6) and I think that the problem is from the core of Joomla (profile.php in models of com_users), not from an extension
I work with the lastest staging branch and can also not reproduce this behaviour.
I have the same problem (joomla 3.3.6 version), i had install jomsocial. but them said that is a issue from joomla core. Please help me i lost the super user group permission.
viewed the answer from jomsocial:
Yes, it's Joomla! issue. Users lost assignment to groups.
We reported this issue and fix is on the way.**
all component are licenced
As the only people who have confirmed this are jomsocial users we have to conclude it is an issue with jomsocial. I am closing this at this time. If more information is provided to show that the issue is in the core of joomla it can always be reopened
|Closed_Date||0000-00-00 00:00:00||⇒||2015-01-01 16:59:10|
You might want to consider actually fixing this Brian.
Closing this report is good, because it is a duplicate, but that doesn't mean issue is resolved.
This problem occurs dominantly with JomSocial, because JomSocial saves a User basically on every use of the CUser object, even if there was no change. So you have a huge load on the database very quickly and it seems the statements simply get dropped. In a MySQL bin log I had the update on #__user, the deleting of the group 3 seconds later and the insert statement for the group missing completly.
In my case it was Joomla 3.3.3, but I assume this can happen on any version where groups are saved this way, at least back to 2.5 .
How about comparing database with user object and only change it, if there is a difference. That should be at least as save as the current solution. However I think the components using the User class should be more responsible with saving. Maybe core Joomla should offer a way of saving only the data for the #__user table, since a lot of 3rd part components need to use it.