PM notifications not working consistently
-
On my profile:
But:
The PM in question (now read):
And my notifications:
This was my last notification for a PM. I've had 5 since then, no notifications.
-
So I actually had one from a PM from 2 days ago. Except it's part of a chain and I don't have a notification for the OP of the PM thread or the first reply, just the third reply (the second being me so no notification there, natch).
-
@loopback0 - Days Since Last Discourse Bug: -1
-
It's not just you ;)
-
I wasn't sure, but I don't remember seeing posts with anyone else complaining about it.
-
I got it once and I don't use PMs, like almost never.
... maybe that's why I have so many public posts on record ...
-
Huh… I just got a notification for one of my Sekret PM club threads, but not for an auto-response when I flagged a post for whoosh.
Maybe that's significant?
-
I thought it was just for flag responses, as I don't really have PMs other than those, but having checked a PM topic I do have from the other day, I was missing at least one notification from there too.
No idea what the pattern is, if anything. That's why I haven't logged it, it's far too inconsistent.
-
Possibly related:
There is a bug @codinghorror hits fairly frequently that I got to get fixed.
If you invite a user to an existing PM they have they have it set to regular instead of watching which can cause some real confusing states.
-
If you invite a user to an existing PM they have they have it set to regular instead of watching which can cause some real confusing states.
So THAT'S how that happened! I assumed my husband clicked the button by mistake.
-
Repro (cheers @sam) & logged on meta.d.
-
If you invite a user to an existing PM they have they have it set to regular instead of watching which can cause some real confusing states.
It also happens if your post gets moved to a new topic and it becomes the OP: the whole topic is set to "Regular".
Which is inconsistent with opening a new topic which sets it to "Watching".
Also, notifications get resent, but that's a separate issue.
-
This seems to be working now at least.