Show Thread Enhancements - Mark Threads Unread (vB4)

This product undoes thread read marking so the thread will show in New Posts in case you want to come back to it later. Open the Thread Tools menu and click the button at the bottom. Enable/disable is in General Settings.

Improved version now handles both database and cookie methods of marking threads read. The link now shows only for threads younger than the read marking limit.

Bug fixed The improved version had a bug, which I have fixed.

Installation: Import the product file in Product Manager

[nerbert]

I fixed the problem with cookie based thread marking and now the link shows only for threads younger than the marking cut off limit.


Here's a quick paste in update.

For the "Build Form and Link" Plugin:

if($vbulletin->options['enable_mark_unread'])
{
	$template_hook['showthread_after_activeusers'] .= '
		<form name="unmark">
			<input type="hidden" name="do" value="unmark" />
			<input type="hidden" name="threadid" value="' . $threadinfo['threadid'] . '" />
			<input type="hidden" name="forumid" value="' . $foruminfo['forumid'] . '" />
			<input type="hidden" name="userid" value="' . $vbulletin->userinfo['userid'] . '" />
			<input type="hidden" name="s" value="' . $session['sessionhash'] . '" />
			<input type="hidden" name="securitytoken" value="' . $vbulletin->userinfo['securitytoken'] . '" />
		</form>
		<script>
			function vB_AJAX_Mark_Unread(form) {
				this.form = form;
				this.lastPost = ' . $threadinfo['lastpost'] . ';
				this.cutOff   = ' . (TIMENOW - ($vbulletin->options['markinglimit'] * 86400)) . ';
			}
			vB_AJAX_Mark_Unread.prototype.addLink = function() {
				if(this.lastPost > this.cutOff) {
					var unmark = document.createElement("li");
					unmark.innerHTML = \'<a id="mark_unread"  href="javascript:markUnread.unmark();">' . $vbphrase['mark_unread'] . '</a>\';
					fetch_object("threadtools").getElementsByTagName("ul")[0].appendChild(unmark);
				}
			}
			vB_AJAX_Mark_Unread.prototype.unmark = function() {
				YAHOO.util.Connect.setForm(this.form);
				YAHOO.util.Connect.asyncRequest("POST","showthread.php?do=unmark",{success:this.confirm,failure:this.confirm,timeout:vB_Default_Timeout,scope:this});
			}
			vB_AJAX_Mark_Unread.prototype.confirm = function(doc) {
				fetch_object("mark_unread").parentNode.innerHTML = \'<a style="background:rgb(200,50,20);color:white;">' . $vbphrase['marked_unread'] .'</a>\';
			}
			markUnread = new vB_AJAX_Mark_Unread(document.forms.unmark);
			window.onload = function() {
				markUnread.addLink();
			}
		</script>
	';
}

For the "Delete Query" plugin:

if($vbulletin->options['enable_mark_unread'])
{
	if($_REQUEST['do'] == 'unmark')
	{

		$vbulletin->input->clean_array_gpc('r', array(
			'threadid' 	=> TYPE_STR,
			'forumid' 	=> TYPE_STR,
			'userid' 	=> TYPE_STR
		));
		
		$threadid = intval($vbulletin->GPC['threadid']);
		$forumid  = intval($vbulletin->GPC['forumid']);
		$userid   = intval($vbulletin->GPC['userid']);
		
		if ($vbulletin->options['threadmarking'])
		{
			
			$vbulletin->db->query_write("
				DELETE FROM " . TABLE_PREFIX . "threadread
				WHERE threadid = $threadid 
				AND   userid   = $userid;
			");
			
			$vbulletin->db->query_write("
				DELETE FROM " . TABLE_PREFIX . "forumread
				WHERE forumid  = $forumid 
				AND   userid   = $userid;	
			");
		
			die('done');
		}
		else
		{
			set_bbarray_cookie('thread_lastview', $threadid, 0);
		}
	}
}

[djbaxter]

Originally Posted by nerbert

I fixed the problem with cookie based thread marking and now the link shows only for threads younger than the marking cut off limit.


Here's a quick paste in update.

For the "Build Form and Link" Plugin:

if($vbulletin->options['enable_mark_unread'])
{
	$template_hook['showthread_after_activeusers'] .= '
		<form name="unmark">
			<input type="hidden" name="do" value="unmark" />
			<input type="hidden" name="threadid" value="' . $threadinfo['threadid'] . '" />
			<input type="hidden" name="forumid" value="' . $foruminfo['forumid'] . '" />
			<input type="hidden" name="userid" value="' . $vbulletin->userinfo['userid'] . '" />
			<input type="hidden" name="s" value="' . $session['sessionhash'] . '" />
			<input type="hidden" name="securitytoken" value="' . $vbulletin->userinfo['securitytoken'] . '" />
		</form>
		<script>
			function vB_AJAX_Mark_Unread(form) {
				this.form = form;
				this.lastPost = ' . $threadinfo['lastpost'] . ';
				this.cutOff   = ' . TIMENOW - ($vbulletin->options['markinglimit'] * 86400) . ';
			}
			vB_AJAX_Mark_Unread.prototype.addLink = function() {
				if(this.lastPost > this.cutOff) {
					var unmark = document.createElement("li");
					unmark.innerHTML = \'<a id="mark_unread"  href="javascript:markUnread.unmark();">' . $vbphrase['mark_unread'] . '</a>\';
					fetch_object("threadtools").getElementsByTagName("ul")[0].appendChild(unmark);
				}
			}
			vB_AJAX_Mark_Unread.prototype.unmark = function() {
				YAHOO.util.Connect.setForm(this.form);
				YAHOO.util.Connect.asyncRequest("POST","showthread.php?do=unmark",{success:this.confirm,failure:this.confirm,timeout:vB_Default_Timeout,scope:this});
			}
			vB_AJAX_Mark_Unread.prototype.confirm = function(doc) {
				fetch_object("mark_unread").parentNode.innerHTML = \'<a style="background:rgb(200,50,20);color:white;">' . $vbphrase['marked_unread'] .'</a>\';
			}
			markUnread = new vB_AJAX_Mark_Unread(document.forms.unmark);
			window.onload = function() {
				markUnread.addLink();
			}
		</script>
	';
}

For the "Delete Query" plugin:

if($vbulletin->options['enable_mark_unread'])
{
	if($_REQUEST['do'] == 'unmark')
	{

		$vbulletin->input->clean_array_gpc('r', array(
			'threadid' 	=> TYPE_STR,
			'forumid' 	=> TYPE_STR,
			'userid' 	=> TYPE_STR
		));
		
		$threadid = intval($vbulletin->GPC['threadid']);
		$forumid  = intval($vbulletin->GPC['forumid']);
		$userid   = intval($vbulletin->GPC['userid']);
		
		if ($vbulletin->options['threadmarking'])
		{
			
			$vbulletin->db->query_write("
				DELETE FROM " . TABLE_PREFIX . "threadread
				WHERE threadid = $threadid 
				AND   userid   = $userid;
			");
			
			$vbulletin->db->query_write("
				DELETE FROM " . TABLE_PREFIX . "forumread
				WHERE forumid  = $forumid 
				AND   userid   = $userid;	
			");
		
			die('done');
		}
		else
		{
			set_bbarray_cookie('thread_lastview', $threadid, 0);
		}
	}
}

Not working correctly. It now fails to show the Mark Unread option in threads that are well within the timeframe (using database marking).

Fortunately, I didn't overwrite my saved copy of the previous version which was better, IMO.

[nerbert]

Bug fixed. After I had tested it I tidied up the code and introduced a bug. The file is corrected and a the paste-in code in my earlier post is corrected. Sorry

[tbworld]

Really nice @Nerbert!

[DF031]

It seems there are no instructions on how to insdtall this mod. Or am I missing something ?

[ozzy47]

Sure there is, this is in the first post:

Installation: Import the product file in Product Manager

[nerbert]

Just upload the product xml file in the Import Product page and it's ready to go.

[edgeless]

Will someone please take a guess on what I'm missing here or what's wrong? I've imported this mod and it installed correctly. It shows as being enabled by default in the AdminCP General Settings panel. However, when I go into a thread and click on the 'Mark Unread' menu item, it changes to a bright red highlight and the menu remains visible (i.e., it doesn't go away). The particular thread then does not appear to be marked as unread (no boldface subject text, etc). Am I missing something obvious? Thanks in advance.

[tbworld]

Make sure you have read through the thread and you are using the database for thread marking. Check for JavaScript errors on the AJAX calls.

[edgeless]

Thanks for the reply.

Originally Posted by tbworld

Make sure you have read through the thread and you are using the database for thread marking. Check for JavaScript errors on the AJAX calls.

The threads I'm testing have been read and were recently created. I'm using the cookie thread marking option, BUT the description for this mod says:

Improved version now handles both database and cookie methods of marking threads read.

Both the statement above and nerbert's dialog here lead me to believe that he coded this mod to work with the cookie thread marking option as well. So I'm confused about the behavior I'm noticing. Any ideas what's going on?