No problem! It seems to work perfectly so far — but only for notifications generated after the patch is applied. Older ones still need to be marked as read manually.
It looks like this is a known bug, and a patch might be implemented in the future (see “Attachments”):
https://bbpress.trac.wordpress.org/ticket/3341
Editing bbpress/includes/extend/buddypress/notifications.php as shown there has fixed the issue for me.
I have this problem too, and it also occurs on another, larger bbPress forum where I am a moderator.
I’ve asked someone who knows PHP to take a look at the code in bbpress/includes/extend/buddypress/notifications.php, but the couldn’t find any problem there.
I’m not sure if they were onto something or not, but they said the bug might originate in an incorrect reference to the database topic/post IDs, similarly to what @nikbond said above.
Robin’s solution above does not seem to work for me either.
This probably comes too late to be of any use to you, and maybe your error had a different cause, but I encountered this problem on my site yesterday and was able to fix it by deleting some replies that did not have associated parent topics in the wp_posts database.
I accessed wp_posts using PHP My Admin, entered “reply” next to “post type”, and manually deleted all posts that had “0” under their “Post parent”.
In my case the error appeared after I clicked on “Replies” – “Add new” – “Preview” in the dashboard. It created an errant entry in the database. It’s probably a bbPress bug.
Please use maximum caution before modifying the database though, and don’t do it if you don’t have a proper backup.
