Fixed Read / unread state missing from conversations, and threads in API
- Thread starter Jake B.
- Start date
I presume this is referring to the API.
At this point, it's probably worth checking against 2.2. In this case, this was something we specifically highlighted as being exposed in 2.2 with our API additions: https://xenforo.com/community/threads/a-few-more-things.183091/
I'll leave this open though, as it looks like we don't actually expose is_unread for conversations even though it's essentially trivial. We could potentially expose unread state for individual posts and conversation messages as well (or just expose the last read date which effectively gives that information).
At this point, it's probably worth checking against 2.2. In this case, this was something we specifically highlighted as being exposed in 2.2 with our API additions: https://xenforo.com/community/threads/a-few-more-things.183091/
I'll leave this open though, as it looks like we don't actually expose is_unread for conversations even though it's essentially trivial. We could potentially expose unread state for individual posts and conversation messages as well (or just expose the last read date which effectively gives that information).
Jake B.
Well-known member
Yeah, thought i put it in the title apparently didn't
Thank you for reporting this issue, it has now been resolved. We are aiming to include any changes that have been made in a future XF release (2.2.1).
Change log:
Change log:
There may be a delay before changes are rolled out to the XenForo Community.
