Opened 6 years ago
Last modified 2 years ago
#3674 new defect (bug)
Forums: pending replies do not send notification after reviewed
Reported by: | mariovalney | Owned by: | |
---|---|---|---|
Milestone: | Priority: | high | |
Component: | Support Forums | Keywords: | |
Cc: |
Description
When a reply is pending on Support Forum no notifications are sended.
It's OK but I guess it should trigger a notification when it's published.
Change History (17)
This ticket was mentioned in Slack in #forums by clorith. View the logs.
5 years ago
#3
@
5 years ago
I was talking about the regular notifications (not a new one about the answer beeing reviewed itself).
A user who subscribed for a topic (and most important: the author) is waiting for notifications about new content. So it's not spam even sending it later.
If the answer is not OK for forums will not be published, so OK not sending notification.
EDIT: I checked now the discussion on Slack.
First I was thinking about the answers that fall on spam by mistake (if you point a lot of links for docs, for example) but your concern about the mail vendors is a very good point. Maybe we can send a notification with a (not so) generic text point to a new answer?
#4
follow-up:
↓ 7
@
4 years ago
Maybe we can send a notification with a (not so) generic text pointing to a new answer?
I like the idea about just sending an update, like:
Someone has replied in a topic you're following. Here's a link...
Another question: would this be easier to implement upstream, in bbPress? If yes, and if the development isn't overwhelmingly big, then perhaps it would be better to make it happen there?
This ticket was mentioned in Slack in #forums by vladytimy. View the logs.
4 years ago
#6
@
4 years ago
- Priority changed from low to normal
Lots of people may be missing good replies from devs just because they happen to be flagged or Akismet (wrongly) puts the reply in the moderation queue.
I think it's very important that the OP gets a notification when a reply is approved.
#7
in reply to:
↑ 4
@
4 years ago
Replying to tobifjellner:
Another question: would this be easier to implement upstream, in bbPress? If yes, and if the development isn't overwhelmingly big, then perhaps it would be better to make it happen there?
I like this idea.
Never contributed to bbPress so I'll try to figure out how to take this way. Any suggestion will be appreciated.
This ticket was mentioned in Slack in #meta by vladytimy. View the logs.
4 years ago
This ticket was mentioned in Slack in #meta by vladytimy. View the logs.
4 years ago
This ticket was mentioned in Slack in #forums by vladytimy. View the logs.
4 years ago
This ticket was mentioned in Slack in #forums by vladytimy. View the logs.
3 years ago
This ticket was mentioned in Slack in #forums by vladytimy. View the logs.
3 years ago
This ticket was mentioned in Slack in #forums by vladytimy. View the logs.
3 years ago
#16
@
2 years ago
[11978] works around this, but is intended on being a temporary patch as it appears the solution to this needs to be done within bbPress.
Upstream ticket: https://bbpress.trac.wordpress.org/ticket/3474
I'm not sure if this is a good way forward.
If, for example, Akismet flagged something, then there's a high likelihood that the user receiving an email with the same content later will also view it as spam and mark it as such.
Email services work off reputation these days, and we don't want to risk sending content which may be perceived as spam to users.
As for flagged accounts, they are users who have had a behavior that means we want to keep an eye on them, and the notifications being blocked is part of that task, so that we're certain what information ends up where from a potential bad actor.