@Moc This is definitely a bug.

forum_threadclass is exactly for this and if you check forum update, you can see it is filled from
$tmp['forum_threadclass'] = $tmp['forum_postclass'];

function sc_newthreadbuttonx() is checking this:
if ($this->var['ntUrl'])

and this is checking permission this way:

//-- if($forum->checkPerm($forumId, 'thread')) //new thread access only.
	if($forum->checkPerm($forumId, 'post')) //new thread access only.
	{
		$forumSCvars['ntUrl'] = e107::url('forum', 'post') . "?f=nt&amp;id=" . $forumId;
	}

The correct way is: (no idea why it is commented now):


	if($forum->checkPerm($forumId, 'thread')) //new thread access only.
	{
		$forumSCvars['ntUrl'] = e107::url('forum', 'post') . "?f=nt&amp;id=" . $forumId;
	}

If you check 1.0.4 code for this:

if (check_class($forum_info['forum_postclass']) && check_class($forum_info['parent_postclass']))
{
	$NEWTHREADBUTTON = "<a href='".e_PLUGIN."forum/forum_post.php?nt.".$forum_id."'>".IMAGE_newthread."</a>";
}

but legacy forum_postclass is not forum_threadclass

Uh oh!

Forum permissions for creating topics (+announcements/sticky) #3974

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions