- Fix silly bug where non-expiring warnings/bans where ignored when considering the next expiry time.
2.6.6 - Maintenance update
- Improve robustness of expiring warnings/bans/etc on the next page visit after they have expired.
- Fix edge case where rebuild pending expiry time-stamp was not triggered as expected
- On rebuild user caches, also rebuild pending expiry time-stamp
Older versions (XF1?) may have caused an expiry date of 4294967295 instead of 0 for non-expiring. It is recommended to review these warnings and manually expiring them;
Code:
select *
from xf_warning
where expiry_date = 4294967295 AND is_expired = 0
After this rebuilding user via tools => rebuild users, or via CLI php cmd.php xf-rebuild:users will recompute the next pending expiry for all users