View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002643 | Composr | core_notifications | public | 2016-06-07 03:27 | 2016-06-07 20:51 |
| Reporter | Patrick Schmalstig | Assigned To | Chris Graham | ||
| Severity | Minor-bug | ||||
| Status | resolved | Resolution | fixed | ||
| Product Version | |||||
| Fixed in Version | |||||
| Summary | 0002643: If user has no permission to use private topic, user gets no notification even if staff send a PT to them | ||||
| Description | On my website, users in probation are not allowed to use Private Topics because of the abuse implications. In addition, notification lock down states all users should receive an email when they receive a private topic (this is forced so users get an email for Private Topics, especially necessary for staff messages and warnings/punishments). However, if a user in probation (without private topic permissions) receives a private topic, say, from the warning/punishment system or staff, they do not get a notification about it like they should. | ||||
| Tags | No tags attached. | ||||
| Time estimation (hours) | |||||
| Sponsorship open | |||||
|
|
It's a curious one this. If they're not allowed to create them, they shouldn't be able to configure the notification as we shouldn't bloat up their settings UI - except maybe if people keep sending them them, they'd want to. I think the best compromise is to make it send using default settings and just acknowledge this can never be perfect; I don't want to make some config option to control the behaviour. So that's what I've done. The default settings is A__STATISTICAL, i.e. they'll get a notification using the average of what they've set for other ones (or in your case, your lock-down setting). |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2016-06-07 03:27 | Patrick Schmalstig | New Issue | |
| 2016-06-07 20:51 | Chris Graham | Note Added: 0003993 | |
| 2016-06-07 20:51 | Chris Graham | Status | non-assigned => resolved |
| 2016-06-07 20:51 | Chris Graham | Resolution | open => fixed |
| 2016-06-07 20:51 | Chris Graham | Assigned To | => Chris Graham |
