Thanks @julian, that solved that issue.
Additional details. The problem may be the way that I have my S3 content bucket locked down such that my dev forum cannot access the files (different subdomain).
A notification is sent when somebody replies to a post, which is fine. But a second notification is sent for the same post saying that the user has made a new post. I don't think that's right.
The 2 highlighted notifications in this post where from the same post.
I think it happens when you have created that post as you automatically follow it as well I think.
The system should still know that it already sent out a notification from the same user for the same post to user X.
@planner fair enough.
@planner This is what happens when two people write notifications
I wrote the lower one, @baris wrote the top one. They should have the same
unique_id (so the older one gets deleted and replaced with the newer one).
Looking at it now, I'd rather the lower one be shown, as it has more info... alternatively, we should be passing post data (tid/pid, title) to the notification for the "followers" notification.
So it's a case of too many cooks spoiling ... :wink2:
Yes, but what a broth it is...