Closed (fixed)
Project:
Advanced Forum
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
22 May 2009 at 15:13 UTC
Updated:
7 Jan 2010 at 07:59 UTC
Jump to comment: Most recent file
Comments
Comment #1
michelleBumping to development branch. Will backport when it's fixed.
Michelle
Comment #2
michelleThe likely culprit:
[12:51] I will note that mark as read compares node.created and Views, at least, compares node.changed
[12:51] So with this query I think a node with a very old created and a more recent changed might get marked unread because its history record would get deleted and no one one might get added.
Comment #3
tom_o_t commentedHere's the patch for testing - thanks to merlinofchaos for getting to the root of this one
Comment #4
michelleI reviewed this enough to test that it didn't break MAR but I didn't set up the edge case the fix targetted. Going to call this fixed. If I (or anyone) run into any more weirdness, I'll re-open.
Thanks,
Michelle
Comment #5
neclimdulseems to be working for me.
Comment #6
neclimdulComment #7
dparrott commentedhi,
is this fix in the current dev version of advanced forums? my users are running into this issue.
Thanks!
dave
Comment #8
michelleIt's fixed in 2.x. I haven't backported it to 1.x. I suppose I could do that. It's a small enough thing.
Michelle
Comment #9
dparrott commentedwell, what do you suggest? I could either upgrade to 2.x-dev or use the 1.x-dev (if you want to port it), or finally, if you give me the fix I could just put it into my current code base (if it isn't too complicated).
Comment #10
michelleThe fix is in #3. No, I don't recommend upgrading to 2.x. I'll get it into the 1.x dev eventually. This is a weird edge case thing that rarely happens so it hasn't been a super high priority for me.
Michelle
Comment #11
dparrott commentedthanks, michelle. guess i didn't look close enough to the thread. sorry about that!
Comment #12
dparrott commentedwell, i noticed this works when i am at a forum page (viewing just topics for a forum). But, when i try to mark all read from a container page (containing multiple forums), it doesn't seem to work. am i missing something?
Comment #13
michelleContainers can't have posts in them so there would be nothing to mark read. Being able to mark all forums in a container all read at once would be a new feature request. The code isn't designed to handle that, and that's unrelated to this issue.
Michelle
Comment #14
dparrott commentedoh ok, i guess i'll just make it so the button doesn't show up in containers.
Comment #15
michelleFixing title so I remember what this is.
Michelle
Comment #16
michelleOk, backported to both 1.x and D5.
Michelle
Comment #18
maulwuff commentedplease create a new D5 release, as the backport is still in the dev branch. It's missing in 5.x-1.1