View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005516 | Composr | cns_warnings | public | 2023-12-30 19:19 | 2024-04-12 20:04 |
| Reporter | Patrick Schmalstig | Assigned To | Patrick Schmalstig | ||
| Severity | Feature-request | ||||
| Status | resolved | Resolution | fixed | ||
| Product Version | 11.alpha1 | ||||
| Fixed in Version | |||||
| Summary | 0005516: Improvements to the automatic prepped e-mails to site owners in warnings forms | ||||
| Description | Currently, when using warnings to send e-mails to site owners who have been spammed by spammers, the example spam includes text which has been completely stripped of Comcode. This makes it difficult for the site owner to determine where the link was located in the message as it only shows the page title as text. Instead, use the function (I forget what it is) that converts Comcode to human readable text / "Markdown". Also change the language of "example spam" to "evidence of spam". And perhaps include the member's username / display name because we are encouraging the company to stop doing business with the spammer, but they need an identifier to know who the spammer is. | ||||
| Tags | Roadmap: v11 | ||||
| Time estimation (hours) | |||||
| Sponsorship open | |||||
|
|
Actually best not to include username at first, but include a line saying ask for the username or e-mail if needed (after verifying they are not the ones facilitating the spam themselves). |
|
|
Automated response: Improvements to the automatic prepped e-mails to site owners in warnings forms E-mails now use human readable version of comcode (tempcode converted to comcode, then comcode stripped). |
|
|
Fixed in Git commit 34232ecc5d (https://gitlab.com/composr-foundation/composr/commit/34232ecc5d - link will become active once code pushed to GitLab) |
|
|
hotfix-5516, 2024-04-12 8pm.tar (124,928 bytes) |
|
|
A hotfix (a TAR of files to upload) has 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. If there are files in a hot-fix that you don't have then they probably relate to addons that you don't have installed and should be skipped. 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/). |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2023-12-30 19:19 | Patrick Schmalstig | New Issue | |
| 2023-12-30 19:19 | Patrick Schmalstig | Status | non-assigned => assigned |
| 2023-12-30 19:19 | Patrick Schmalstig | Assigned To | => Patrick Schmalstig |
| 2024-01-23 22:22 | Patrick Schmalstig | Tag Attached: Roadmap: v11 | |
| 2024-03-30 15:17 | Patrick Schmalstig | Note Added: 0008502 |
