Best Of

I presume the author forgot to tie in the bits that probably works on his side. Or maybe it is intentional! Designed for us to tie in the bits ourselves with some custom CSS and JS.

I did the latter!

Hide the all the fields with CSS, and then reveal with JS upon click of the button

Worked like a charm.

If you need support in translations (e.g. german), let me know.

I don't know the feature list, therefore it's hard to judge.

But if I would have to implement that as a Vanilla addon, I surely would use another DiscussionType just like the Q'n'A plugin does and create categories which are only able to hold discussions of that type. Looks like Vanilla already has a pretty good support for custom discussion types. There is DiscussionModel::discussionTypes() and CategoryModel::allowedDiscussionTypes() which both fire events so that you can extent it quite easily. And the newdiscussionmodule builds its button dynamically based on the discussion types.

@TwistedTwigleg and@despecial the check for the QNA plugin is inessential and unnecessary since this wonderful and awesome search plugin works without QNA. The QNA bits are triggered only on demand.

Go to plugins/FilteredForumSearch/class.filteredforumsearch.plugin.php

and remove ...

  'RequiredPlugins' => array ('QnA' => '1.4'),

And everything below is for cosmetics ...

And/or go to plugins/FilteredForumSearch/views/index.php

before the first echo

add:

$QNA_Menu = '';
if (class_exists('QnAPlugin')) {
	$QNA_Menu = 
	'<div class="SearchAnswerDropdown">'.
	$Form->Label(Gdn::translate('Filter by Q&A'), 'ADV_Filter_QNA'). ' ' .
	$Form->DropDown('ADV_Filter_QNA', $AnswerDropdownOptions, $AnswerDropdownFields).
	'</div>';
}

Then find this bit

// Q&A dropdown
'<div class="SearchAnswerDropdown">',
$Form->Label(Gdn::translate('Filter by Q&A'), 'ADV_Filter_QNA'), ' ',
$Form->DropDown('ADV_Filter_QNA', $AnswerDropdownOptions, $AnswerDropdownFields).
'</div>',

And replace with

// Q&A dropdown
$QNA_Menu,