Something strange

[Jamsoft]

We just today upgraded to the latest version of AWS. We were running 3.2.0 but are now up and running on 3.4.16 (we are on the 3.0.x version of vBulletin).

The other day one of our users, who SHOULD have been perm banned posted in one of our forums. Looking at the account, it looked like he was perm banned, and THEN warned later on. (Our perm ban warnings have an expiration of 99,999 days). We thought that perhaps when the warning expired, it accidently lifted the ban. The warning points were still correct, but he was just unbanned.

So we upgraded hoping this was just a bug.

Now today (this was before we upgraded), I see another user who was banned on 12/28. He started a new thread yesterday. This one was not perm banned, but had received two warnings for 5 points each. When you reach 10 points, you get a temp ban.

What would be causing these bans to be removed? any ideas? Should this be fixed with our new version?

Thanks!

[sv1cec]

We just today upgraded to the latest version of AWS. We were running 3.2.0 but are now up and running on 3.4.16 (we are on the 3.0.x version of vBulletin).

The other day one of our users, who SHOULD have been perm banned posted in one of our forums. Looking at the account, it looked like he was perm banned, and THEN warned later on. (Our perm ban warnings have an expiration of 99,999 days). We thought that perhaps when the warning expired, it accidently lifted the ban. The warning points were still correct, but he was just unbanned.

So we upgraded hoping this was just a bug.

Now today (this was before we upgraded), I see another user who was banned on 12/28. He started a new thread yesterday. This one was not perm banned, but had received two warnings for 5 points each. When you reach 10 points, you get a temp ban.

What would be causing these bans to be removed? any ideas? Should this be fixed with our new version?

Thanks!


Try replacing the kill_bans.php file in includes/cron directory with the one attached here. I think there was a bug in that file, which was causing this behaviour and I have corrected it but probably failed to come up with a new version. Please test it and let me know if you have any more problems.