messages_mark_thread_read – illogical?
I spent an hour or two debugging a weird issue for my client yesterday, and I have finally found the culprit –
Client was using a theme (woffice) that offers a live chat functionality (by basically displaying buddypress threads in a chat format). The problem was that, when someone would view someone else’s profile, and have a chat open at the same time, instead of marking that thread as read for him, it would instead mark it as read for that person.
messages_mark_thread_readfirst checkes whether a user is displayed, and then clears the
unread_count` for that user, only falling back to a logged in user if no user is being displayed currently.
I was wondering why is that so?
- You must be logged in to reply to this topic.