When replying to a conversation that a participant has already left, conversation_to_user.leftAt is used instead of conversation.lastPostTime for sorting and determining of the unread status. This can lead to incorrect displays if leftAt deviates significantly from the actual date of the last accessible message.
A better solution would be to store the date of the last accessible message directly in conversation_to_user after leaving.
ref https://www.woltlab.com/community/thread/313888-reihenfolge-der-konversationen-inkonsistent/?postID=2017317#post2017317
When replying to a conversation that a participant has already left,
conversation_to_user.leftAtis used instead ofconversation.lastPostTimefor sorting and determining of the unread status. This can lead to incorrect displays ifleftAtdeviates significantly from the actual date of the last accessible message.A better solution would be to store the date of the last accessible message directly in
conversation_to_userafter leaving.ref https://www.woltlab.com/community/thread/313888-reihenfolge-der-konversationen-inkonsistent/?postID=2017317#post2017317