View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005476 | Composr | points | public | 2023-11-27 05:35 | 2024-07-25 21:58 |
| Reporter | Patrick Schmalstig | Assigned To | Patrick Schmalstig | ||
| Severity | Feature-request | ||||
| Status | resolved | Resolution | fixed | ||
| Product Version | |||||
| Fixed in Version | |||||
| Summary | 0005476: Add a warning hook to allow specifying recent point transactions to reverse | ||||
| Description | Ditto. On the warning form, have another section which shows recent point transactions by the member (specifically, ones where the member sent points, received points, or has been credited points... filter out debited points). Since the ledger can get very large very fast, limit it to transactions in the last 7 days, capped at whatever the max is for deleting content. Allow checking off specific transactions to reverse them. When transactions are reversed, a punitive action text should be generated indicating so. This punitive action should not have an undo function as reversed transactions cannot be undone. | ||||
| Additional Information | Should be in a new section called "Points"... and move "Charge points" into this section as well. Keep in mind privileges (whether or not the moderator can reverse point transactions). | ||||
| Tags | Roadmap: v11 | ||||
| Time estimation (hours) | |||||
| Sponsorship open | |||||
| related to | 0003438 | resolved | Patrick Schmalstig | Hooks for the punish form |
|
|
Hard-coding 7 days is interesting. I just tidied it up slightly https://gitlab.com/composr-foundation/composr/-/commit/77c12e0d0510f39e6a715ace5e3df2c0afd109c7. Didn't change the DESCRIPTION_DELETE_CONTENT[_POINTS] lang strings. I could see someone wanting that to be configurable. Or I could see an argument it should be just based on a maximum number of entries to show rather than time. But it's debatable and I'm happy to leave this be unless someone comes back about it. |
|
|
Sounds good. It was hard-coded in the original warnings code before I moved it to hooks (based off of the content delete code), though I think I changed the timeframe. I agree making it configurable in the future would be good. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2023-11-27 05:35 | Patrick Schmalstig | New Issue | |
| 2023-11-27 05:35 | Patrick Schmalstig | Status | non-assigned => assigned |
| 2023-11-27 05:35 | Patrick Schmalstig | Assigned To | => Patrick Schmalstig |
| 2023-11-27 05:36 | Patrick Schmalstig | Additional Information Updated | View Revisions |
| 2023-11-27 05:37 | Patrick Schmalstig | Additional Information Updated | View Revisions |
| 2023-12-05 14:18 | Patrick Schmalstig | Status | assigned => resolved |
| 2023-12-05 14:18 | Patrick Schmalstig | Resolution | open => fixed |
| 2023-12-05 14:18 | Patrick Schmalstig | Tag Attached: Roadmap: v11 | |
| 2024-03-30 03:39 | Patrick Schmalstig | Project | Composr alpha bug reports => Composr |
| 2024-03-30 03:43 | Patrick Schmalstig | Category | General / Uncategorised => points |
| 2024-07-25 18:50 | Chris Graham | Note Added: 0008933 | |
| 2024-07-25 19:02 | Patrick Schmalstig | Note Added: 0008936 | |
| 2024-07-25 19:03 | Patrick Schmalstig | Note Edited: 0008936 | View Revisions |
| 2024-07-25 21:58 | Chris Graham | Relationship added | related to 0003438 |
