View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 1696 | Composr | cns_warnings | public | 2014-10-05 17:54 | 2014-10-05 17:54 |
| Reporter | PDStig | Assigned To | Guest | ||
| Priority | normal | Severity | minor | ||
| Status | resolved | Resolution | fixed | ||
| Summary | 1696: Formal warning count on the warn/punish member audit page is inaccurate | ||||
| 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. | ||||
| Tags | No tags attached. | ||||
| Attach Tags | |||||
| Attached Files | |||||
| Time estimation (hours) | |||||
| Sponsorship open | |||||
|
|
Automated response: Warning count issues 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). |
|
|
Fixed in git commit 2a13608 (https://github.com/chrisgraham/Composr/commit/2a13608 - link will become active once code pushed) A hotfix (a TAR of files to upload) have been uploaded to this issue. These files are made to the latest intra-version state (i.e. may roll in earlier fixes too if made to the same files) - so only upload files newer than what you have already. Always take backups of files you are replacing or keep a copy of the manual installer for your version, and only apply fixes you need. These hotfixes are not necessarily reliable or well supported. Not sure how to extract TAR files to your Windows computer? Try 7-zip (http://www.7-zip.org/). |
