[EdQ]

Originally Posted by Delphiprogrammi

Bans maturity periodEnter the number of days, a ban remains in a member's account. If set to '0', then the bans remain in the members accounts for ever. If set to a different number, a cron job will reduce the number of bans in a member's account by one, after so many days pass, from the day that ban was applied.
Attention: This does not mean that the user is unbanned. If you have a banning period of 7 days and you have set the bans maturity period to 5 days, the ban will be removed from the user's account after 5 days, but he will still be banned for another 2 days. In a production system, this option should always be much larger than the number of days a member is banned, when he reaches the ban limit.
This option obviously applies only to non-permanent bans.

admincp => Advanced Warning System => Manage Warning Options => Banning Options => Ban Maturity Period

I understand that, but does it matter if I use historical data?

I prefer not to so the warnings will come off when they mature. It seems when I use historical data, warnings are not removed when they mature. Just the warning level.


I am not sure if I am getting my point across.

Using historical data.
Warning Level is removed when matured
Warning is never removed (Not what I want)
Warning Bans stay until matured.

Not using historical data.
Warning Level is removed when matured
Warning is removed when matured
Warning Bans are removed when the ban ends. (Not what I want)

What I would like to see if either the warning or ban matures. It drops off the users account.