The package optimizes the query for fetching unread posts as recommended by @XFA

As we already fetch the nodes in a separate query, no additional query was required.

Thank you!

Due to migration to a new caching strategy, a bug was introduced that would not change unread post count badge when the user reads an unread post.

Please note, that the product has an option Unread Post Count Cache (Minutes) in the option group Threads, discussions and conversations which defines how long unread post counts should be cached. If caching is not desired, and you want your users to always immediately see the number of unread posts, just set this option to 0. Caching is highly recommended for large websites, for at least as short as 1 minute, as executing an aggregation query on each page load may increase server load considerably.

This release fixes a bug that caused the unread post count badge not to be shown immediately after login. The issue was caused by storing cached information in the session which would reset with every logout/login. Now the cache is stored in the registry and is rebuilt only once per user and when the cache expires for the given user.