After upgrade rankbadges gets taken away.

[vBET]

Whole code about usergroups you have in file /includes/vbenterprisetranslator_functions_usergroups.php.

There is only one function which is used as reaction to vBulletin logic (for hook: userdata_presave) and the function name is vbenterprisetranslator_functions_usergroups.php (7 matches).

Other 2 functions in the file which makes changes are used for removing vBET usergroups during vBET un-installation and nowhere else.

So if it is wrong because of vBET, then it can be only because of function vbet_changeDefaultLanguageGroup. Nothing else is making any changes on usergroups.

So if you want to disable it, then the simplest way is to just disable "Set appropriate Default Language Group" plugin. But this will disable automatic handle for vBET usergroups. So if you want those also be removed just remove it by Admin CP.

We recommend just to disable the plugin first. If you find your issue disappear, then we can check it again (we checked it already twice), still we have same thing - we do not know how to reproduce the issue.

Also you can check other plugins for hook userdata_presave and change execution order to be executed before/after vBET plugin.

[Taurus]

After disabling that plugin, and running without it for about 48 hours now, I have not had this issue again. So I think it would be safe to assume that it is because vBET added and additional usergroup, and if you have a few already, for some reason the others gets taken away with some cron running. lol, that sounds a bit vague I know, but without the plugin it is all good again.

[vBET]

OK so - we will check it again. This was the only change you made - disabling the plugin? Does vBET usergroups are still on your forum or you removed those? What is exact version of your vBulettin (we want to look close not only in our code but also in hook environment)?

[Taurus]

Yes, that is the only change I made. And I took the ticks out from the usergroups for vBET. But they are still there though. Is there an easy way to remove those? Because it takes up a lot of space.

[vBET]

And I took the ticks out from the usergroups for vBET.

What does it mean exactly? You did what?

About removing vBET groups - you can do it by Admin CP in vBulletin options, or by executing function vbet_removeDefaultLanguageGroups from /includes/vbenterprisetranslator_functions_usergroups.php

Please note that if you remove those we will be not ale to look closer at the issue, because it happens only on your forum.

[Taurus]

What does it mean exactly? You did what?

I deselected the usergroups from vBET. Like when you select a user in ACP it will have a tick/mark by let's say 'Spanish' as an additional usergroup. This I deselected.

[vBET]

As I wrote you in PM we still do not know what is the reason of the issue on your forum. Still I made some changes in vBET code in this area. Right now vBET will handle usergroups only when some usergroups changed or when user default language chanes. So in hook it is added condition:

if ($this->setfields['membergroupids'] || $this->setfields['vbet_def_lang']) { 

I have no idea will it help to your issue since we do not know what causes it. Anyway it is possible that it will help. As I wrote you in PM, in your changes history often usergroups from before column was cleared - maybe because those where not loaded from database at all. With this condition in such cases vBET will do nothing, because in booth cases when user changes data by User CP or admin by Admin CP, then usergroups are loaded.

This will be included in next release, so please check it. If it will not work then you will disable the hook again and we will made investigation again.

Please confirm after update does it help.

EDITED - it is confirmed. For quick fix please:
1. Go to Admin CP -> Plugins & Products -> Plugin Manager
2. Find hook named Set appropriate Default Language Group for hook userdata_presave and click Edit for it
3. Add at the beggining of code:

if ($this->setfields['membergroupids'] || $this->setfields['vbet_def_lang']) { 

4. Add at the end of code:

} 

5. Save it

[Taurus]

OK, I upgraded now, and will check if I still have this problem. I will let you know. Thanks.

[Taurus]

After running with the update for more than 2 days now, and without disabling that plugin or anything else, I have not had this issue again. So I think it is safe to say that your fix did the trick. Thanks again Michal. A real big thanks! I know that this issue was only present on my forum, and I sincerely appreciate the extra mile you went to help me on this!

[kamilkurczak]

thanks for this confirmation