#1696 - Formal warning count on the warn/punish member audit page is inaccurate
-
By PDStig
- Added
- 2 views
| Identifier | #1696 |
|---|---|
| Issue type | Minor issue (breaks specific functionality) |
| Title | Formal warning count on the warn/punish member audit page is inaccurate |
| Status | Completed |
| Handling member | PDStig |
| Addon | cns_warnings |
| Description | When going to the audit page to warn or punish a member, the text at the top of the form explaining how many warnings the user already had is incorrect. For a couple times, it counted informal warnings. |
| Steps to reproduce | 1. Log in as an administrator or other account with punishing capabilities. 2. Locate a member. 3. Go to the warn/punish user page found on the member's profile under the audit menu. 4. Punish the user informally. 5. Go back to that page. It still sometimes shows up on the count even though it was informal. |
| Additional information | On my website, I have rephrased the language. Instead of calling it informal warnings / formal warnings, I call it warnings / strikes.
The member I punished was failsafe, an admin account I created in case if Facebook connect fails on the main admin account. The first two times were just warnings (informal), but it counted as a strike on the text. The third time I made it formal (a strike), and it counted. But the fourth time, I made it an informal warning and that time it did not count. |
| Funded? | No |
| Commits |
The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".
Comments
Deleting warnings, and running the warning cleanup tool, will not correctly recalculate the warnings - the "is formal warning" setting is wrongly ignored in those cases.
After applying this hotfix re-run the warnings cleanup tool (Admin Zone > Tools > Website Cleanup Tools).