FUDforum: Bug Reports » Tree View- threads not showing as read

Home » FUDforum Development » Bug Reports » Tree View- threads not showing as read

Show: Today's Messages :: Polls :: Message Navigator

Tree View- threads not showing as read [message #167660]

Thu, 23 August 2012 19:00

Motiak

Messages: 15
Registered: October 2011

Karma: 0

Junior Member

So, I've had a decent number of complaints from users using tree view on my forum (FUDforum 3.0.3 however I downloaded 3.0.4 and tried it out on a VM and ran into the same issue) that threads they read keep showing up as unread. So I poked around with the code a little and it seems to me like the following from tree.tmpl isn't working as expected:

<a href="{TEMPLATE: tree_branch_lnk}" onclick="fud_tree_msg_focus({VAR: cur->id}, \'{DEF: s}\', \'{CHARSET}\'); return false;" class="big">{VAR: cur->subject}</a>

I don't feel like the fud_tree_msg_focus function in lib.js is properly causing messages to be marked as read which cause threads to show up as unread as well in the forum view. Removing the call to that function seems to fix the problem but I haven't tested it on a wide scale. Is there any specific reason that function needs to be called? Thanks.

Report message to a moderator

Re: Tree View- threads not showing as read [message #167674 is a reply to message #167660]

Tue, 28 August 2012 13:08

Motiak

Messages: 15
Registered: October 2011

Karma: 0

Junior Member

Adding the following to tree_msg.php.t also seems to work also:

$th= $msg_obj->thread_id;

if (_uid) {
if ($msg_obj->last_view < $msg_obj->post_stamp) {
user_register_thread_view($th, $msg_obj->post_stamp, $mid);
}
if ($msg_obj->last_forum_view < $msg_obj->post_stamp) {
user_register_forum_view($msg_obj->forum_id);
}
}

Does that addition seem to make sense?

Report message to a moderator

Re: Tree View- threads not showing as read [message #167679 is a reply to message #167674]

Thu, 30 August 2012 01:46

NeXuS

Messages: 121
Registered: July 2010
Location: South Korea

Karma: 5

Senior Member
Contributing Core Developer

Shouldn't the time check be the other way around?

Right now you are saying: if the last_view timestamp is smaller than the object's timestamp (i.e. the user has seen the object BEFORE it has been updated) then mark it as read.

I am very tired and I may be wrong, but it feels that objects should be marked as read only if the user's last_view timestamp is bigger than the object's update timestamp (i.e. if the user has read the object AFTER it has been updated).

Report message to a moderator

Re: Tree View- threads not showing as read [message #167694 is a reply to message #167679]

Thu, 30 August 2012 13:06

Motiak

Messages: 15
Registered: October 2011

Karma: 0

Junior Member

NeXuS wrote on Wed, 29 August 2012 21:46

Shouldn't the time check be the other way around?

Right now you are saying: if the last_view timestamp is smaller than the object's timestamp (i.e. the user has seen the object BEFORE it has been updated) then mark it as read.

I am very tired and I may be wrong, but it feels that objects should be marked as read only if the user's last_view timestamp is bigger than the object's update timestamp (i.e. if the user has read the object AFTER it has been updated).

I pulled that code (altered slightly) out of tree.tmpl. My understanding of it is if your last_view is less than the timestamp (IE if you haven't looked at the post and your last_view=0) then the database is updated so that your last_view=timestamp.

Report message to a moderator

Aw: Re: Tree View- threads not showing as read [message #167704 is a reply to message #167694]

Mon, 03 September 2012 05:53

alopezie

Messages: 106
Registered: September 2003

Karma: 1

Senior Member

Thanks for your work.
We have the same annoying problem for some time (3.0.4RC2), so I´ ll try your fix after updating to the most recent release.

Alopezie.de - das Forum zum Thema Haarausfall

Report message to a moderator

Re: Aw: Re: Tree View- threads not showing as read [message #167706 is a reply to message #167704]

Mon, 03 September 2012 13:48

Motiak

Messages: 15
Registered: October 2011

Karma: 0

Junior Member

alopezie wrote on Mon, 03 September 2012 01:53

Thanks for your work.
We have the same annoying problem for some time (3.0.4RC2), so I´ ll try your fix after updating to the most recent release.

I actually ran into another issue. When I put in my fix things started acting up differently. Basically I ran into two new problems:

1. Sometimes posts would now look as read when they weren't.
2. Posting in a thread causes threads to look completely read when they're not.

I believe this is because the read SQL table works as follows (and I may be wrong):

Each user gets a last_read entry for the last post that they've read timewise in a thread. That means if they read a post then all posts posted before that will show as read, whether or not they actually read it. Also this means that a reply will make the entire thread show as read which as also an issue. I'm trying to think of a good resolution for this, but it mainly just seems like the read table was created for Flat view, not Threaded.

Report message to a moderator

Previous Topic:	Syndication enabled but not functioning
Next Topic:	Error with Googlebot / Invalid links

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Mar 13 06:59:32 GMT 2025

Total time taken to generate the page: 0.02683 seconds