Excluding specific templates in AjaxSearch

Maybe it’s a stupid question, but are there a possibility to exclude specific templates in a search?

I’ve tried this:

in Evo 1.01 and AS 1.8.3a, but with no luck.

What I want is that every ressource with the template id = 6 are removed from the results. I know that I just can unmark the searchable checkbox in the Page Settings (Shouldn’t it be Resource settings by the way?) but not on 800 resources...

Had I missed something?

Try the DocManager module (Modules -> DocManager); it lets you set that and other setting in bulk in the "Other Properties" tab. Select "Searchable/Unsearchable" from the Available Settings select drop-down, and the Unsearchable radio button. Then in the field below, put in the document IDs you want. You can use ranges (46-68, for example), specify a document and its children, and individual documents all on the same line, each grouping separated by a comma.

You might find it easier, however, to use your domain’s MySQL client (phpMyAdmin?) and run a simple query

Quote from: sottwell at Aug 17, 2009, 03:13 PM

You might find it easier, however, to use your domain’s MySQL client (phpMyAdmin?) and run a simple query

UPDATE modx_site_content SET cacheable=0 WHERE template IN (6,2)

Thanks sottwell,

I try the query, the solution in the DocManager will be just as time-consuming as editing one ressource at a time. And that is the biggest problem: The customer is not very structured in the website and that - in the long run - it would be better to filter the templates.

If this is going to be an ongoing issue, you might want to make a plugin to work with the OnDocFormSave event and check the template and update the database if necessary.

&filter=`template,6,2`

should work. Have you set this parameter in the two ajaxSearch snippet calls (on the page with the search input) and on the page with results ?

That would make everything a lot easier, that’s for sure!

@sottwell: The plugin OnDocFormSave is a good suggestion - it can be very useful!!!! Thanks again!!!

@coroico:

I have this on the page with the search form:


And this on the resultspage: