Quick Reply/Close Thread Problem

for some reason i can close a thread, but the quick reply box still shows up, and if a member posts using it, the thread will automatically open again and allow them to post, how can i fix this

[ULTIMATESSJ]

bump, needs this badly so if anyone can help, please do, btw we are using the quick reply box firefly made

[Xenon]

hmm, have you installed also the quick open close hack?

normally this bug wouldn't occur, because it is prevented in newreply.php in the first few lines....

so unless you ahcked these lines, there shouldn't be an error

[ULTIMATESSJ]

Originally posted by Xenon
hmm, have you installed also the quick open close hack?

normally this bug wouldn't occur, because it is prevented in newreply.php in the first few lines....

so unless you ahcked these lines, there shouldn't be an error

nope, we haven't added that hack

[Xenon]

hmmm, upload an unhacked newreply.php it shouldn't be that way...

also be sure you installed everything alright?
this shouldn't occur

[ULTIMATESSJ]

could it be something to do with the phpinclude template by any chance, since i had a few problems once when removing some template mods

[Xenon]

well it'S possible, depends on your phpinclude

[ULTIMATESSJ]

well heres my phpinclude, i've added some things from vBT to it

// This code is PHP4 only:
// ob_start(); 
// require("yourheader.html");
// $header = ob_get_contents(); 
// ob_end_clean(); 


if (strpos($_SERVER['PHP_SELF'], 'newreply.php') != false)
{
	// These numbers are usergroupids for usergroups that will always
	// have permission to close/stick the thread, regardless of what
	// permission they already have. To add a usergroup, just follow
	// the format (i.e., array(5, 6, 7) allows smods, admins, and any
	// mods to close/stick the thread).
	// If a usergroupid is not specified then the permissions will
	// be automatically derived. It is recommended that you do not 
	// change this behavior.
	$alwaysallowugids = array(5, 6);
	
	$modperms = array();
	if (in_array($bbuserinfo['usergroupid'], $alwaysallowugids))
	{
		// emulate a call to getmodpermissions
		$modperms['canopenclose'] = 1;
		$modperms['canmanagethreads'] = 1;
	}
	else
	{
		$modperms = getmodpermissions($thread['forumid']);
	}
	
	// ---------------------------------------------------------------
	
    if ($_POST['action'] == 'postreply') // newreply redirect page
    {
		$querybits = array();
        if ($modperms['canopenclose'])
		{
			array_push($querybits, "open = " .
				($_POST['closeonreply'] == 1 ? 0 : 1));
		}
		if ($modperms['canmanagethreads'])
		{
			array_push($querybits, "sticky = " .
				($_POST['stickonreply'] == 1 ? 1 : 0));
		}
		
		if (!empty($querybits)) // perm to do at least one of the two
		{
			$threadid = intval($_POST['threadid']);
			$querybits = implode(", ", $querybits);
		
			$DB_site->query("UPDATE thread SET $querybits
				WHERE threadid = $threadid"); //<
		}
    }
	
	// ---------------------------------------------------------------
	
    else // just assume this is the reply form
    {
		// eval the extra option templates as needed
		
		$closebox = '';
		$stickbox = '';
		if ($modperms['canopenclose'])
		{
			$checked = ($thread['open'] ? "" : " checked");
			eval("\$closebox = \"" . gettemplate("newreply_closebox") . "\";");
		}
		if ($modperms['canmanagethreads']) // perm for sticky
		{
			$checked = ($thread['sticky'] ? " checked" : "");
			eval("\$stickbox = \"" . gettemplate("newreply_stickbox") . "\";");
		}
	}
}

[Xenon]

yes, this could make a problem, not sure
ask at vbulletintemplates for a fix of it...

[TECK]

Why don't you add directly into the files the code? Is alot better IMO...
I hope the phpinclude will taken out from VB3. It's such a bad idea...