Error in topic tracking

[tapia]

Man, this was a tough one to reproduce.

Let's say user johndoe have read all the existing topics from a non-empty forum. Then, some of the topics get updated with new posts by other users (IMPORTANT: no new topics created, just some of the existing ones getting updated).

If that happens, when johndoe visits one of the updated topics and go back to the forum page, all the topics appear as already visited.

In terms of database action:

• The initial state is that the user johndoe has an entry for that forum in the table forum_tracking_forumreadtrack, and no related entries in forum_tracking_topicreadtrack.

• Then he visits one of the updated topics. So forum_tracking_forumreadtrack is updated with the new mark_time. That is correct. But a new entry should've been added to forum_tracking_topicreadtrack with the visited topic, but for some reason it isn't.

• As a consequence, the whole forum is marked as read, because the forum's mark_time is greater than the topic update time, but that's not correct.

Please let me know if you need more details to reproduce the bug.

[ellmetha]

👋 I'm not able to reproduce this problem (even if your description is fairly detailed). The TopicReadTrack record is created as expected in my test app.

Perhaps could you give me some step-by-step description to reproduce the problem starting with an empty forum and two users?