See forum discussion:
http://compo.sr/forum/topicview/misc/deploying/provide-the-ability-for.htm?redirected=1#post_76732

Tests...


main_content_filtering block renders a sensible form for a selected content type
main_content_filtering generates an appropriate default filter: no silly fields, appropriate field selector for all shown
main_content_filtering generates an appropriate default filter for a catalogue: hidden fields do not come up on filter
main_content_filtering generates an appropriate default filter for inclusion of a content type's custom fields
main_content_filtering specification of replacement field labels works
main_content_filtering specification of replacement field types works
The main_content_filtering block works in-situ (i.e. the form really does filter stuff as expected)
The "merge links" option on the main_content_filtering works to allow iteratively filtering via link clicking
main_content_filtering form "time" field selector renders and works correctly
main_content_filtering form "date" field selector renders and works correctly
main_content_filtering form "days" field selector renders and works correctly
main_content_filtering form "tick" field selector renders and works correctly
main_content_filtering form "rating" field selector renders and works correctly
main_content_filtering form "list" field selector renders and works correctly, allowing selection from any value previously entered for the field attached to the filter
main_content_filtering form "list" field selector renders and works correctly for the magic meta_keywords filter, allowing selection from any tag
main_content_filtering form "multilist" field selector renders and works correctly
main_content_filtering form "linklist" field selector renders and works correctly
main_content_filtering form "float" field selector renders and works correctly
main_content_filtering form "integer" field selector renders and works correctly
main_content_filtering form "email" field selector renders and works correctly
main_content_filtering form "author" field selector renders and works correctly
main_content_filtering form "username" field selector renders and works correctly
main_content_filtering form "codename" field selector renders and works correctly
main_content_filtering form "line" field selector renders and works correctly
Filtercode works on default fields
Filtercode works on custom fields, when specified as field_<fieldid>
Filtercode works on custom fields, when specified by the human-readable title for the field
The Filtercode ">" operator works as expected
The Filtercode "=" operator works as expected (equals check, excluding blank)
The Filtercode "==" operator works as expected (equals check, including blank)
The Filtercode "~" operator works as expected (full-text search)
The Filtercode "~=" operator works as expected (substring check)
Filtercode filter works for news - check things pass filters
Filtercode filter works for news - check nothing passes impossible filter
Filtercode propagates across news pagination
Filtercode propagates down to news subcategories
Filtercode propagates down to news entries
Filtercode propagates back via news breadcrumbs
Filtercode filter works for members - check things pass filters
Filtercode filter works for members - check nothing passes impossible filter
Filtercode propagates across members pagination
Filtercode propagates down to members subcategories
Filtercode propagates down to members entries
Filtercode propagates back via members breadcrumbs
Filtercode works on custom profile fields, when specified as field_<fieldid>
Filtercode works on custom profile fields, when specified by the human-readable title for the field
It is impossible to use an Filtercode filter on a password field
The "Narrow-in when browsing" works for galleries
Filtercode filter works for galleries - check things pass filters
Filtercode filter works for galleries - check nothing passes impossible filter
Filtercode propagates across galleries pagination
Filtercode propagates down to galleries subcategories
Filtercode propagates down to images
Filtercode propagates back via galleries breadcrumbs
The "Narrow-in when browsing" works for catalogues
Filtercode filter works for catalogue - check things pass filters
Filtercode filter works for catalogue - check nothing passes impossible filter
Filtercode propagates across catalogue pagination
Filtercode propagates down to catalogue subcategories
Filtercode propagates down to catalogue entries
Filtercode propagates back via catalogue breadcrumbs
The "Narrow-in when browsing" works for downloads
Filtercode filter works for downloads - check things pass filters
Filtercode filter works for downloads - check nothing passes impossible filter
Filtercode propagates across downloads pagination
Filtercode propagates down to downloads subcategories
Filtercode propagates down to download entries
Filtercode propagates back via downloads breadcrumbs
Filtercode works with the magic compound_rating field
Filtercode works with the magic meta_keywords field
Trying to do an Filtercode on non-existent errors produces an appropriate error, not a stack trace
The hidden 'Filtercode_protected_fields' option allows locking down fields so Filtercode can't work on them
Hidden catalogue fields cannot be filtered using Filtercode

This one turned into quite a mammouth exercise. It is implemented across 5 content types (the ones you'd want to filter), as well as anything that is loaded up using the main_multi_content block. It introduces a non-trivial new language to Composr, Filtercode, that has great flexibility and is now a key building block of Composr. There really is a great deal of power in how you can do filtering.

A tutorial was posted in the topic linked above.

A patch and TAR has been attached.

The patch/TAR will definitely conflict with the "catalogue grid view" (forget the exact name) patch that was recently implemented. That is because both heavily alter catalogue category display. The "unstable" development branch has everything working in harmony of course.

The .patch file won't apply to 8.0.1 right away, but it probably work on 8.0.2. This is because some minor bugs were found during development that had to be fixed, and it didn't make sense to roll the fixes into the patch itself.