Coronoro

I’m sorry for this mistake >_>
I fixed it right away with an update

I need some of your logs to see where the problem is located:
Sadly I yet do not have a userinterface for enabling this so you need to do it manually.

To do so you need to head to the folder in which all plugins are installed and select the unread posts plugin.
Usually that would be …./wp-content/plugins/bbpress-unread-posts-v2.

There you will find a logging.php. Open it with a text editor or trough your FTP client.

The very first line should look like this:

$isLogging = false;

and you need to change it to:

$isLogging = true;

save your changes and upload the file to where it was.

Open your Browsers console trough (F12 on chrome and firefox).
When you now load a forumpage there should be several entrys shown.
Please post these whenever this issue occurs to you.

If you just recently installed and downloaded the Plugin there should be no problem at all.
If there is an existing topic and someone posts a new reply it should be marked as new.

Sorry for my late reply. I think it is possible to so and in a not so far away update i’m planing on adding this feature.

Could your write down your specs so i can check them?

This functionality is already implemented. This Plugin notices whenever someone wrote a new reply and marks it for everybody as new.
Maybe your facing any problems there?

I just noticed that there isn’t exactly a comment function defined at bbpress or I’m simply not able to find it. Maybe you mean Replys to Posts since they share WordPress Comments settings?

This Plugin does not search trough every Thread if there is a new post.
Rather it notices that there is an update to it and memorise that.

I think that this feature is easily achievable though. However this might not be wanted on every site. So your Request have to wait until an interface is implemented in which the user can choose which notification he wants to show.

Still I could post a snippet which you can paste into the plugin to fit your needs.

Thanks for your post.

I just deployed a new Version which hopefully fixes this issue.