Fork me on GitHub

In modules we often use filters. For example you can filter on tags or contact gender etc. We've created a filtering mechanism that makes it easy to implement them.

We're going to implement a filter by album genre. There are various predefined filter types

We'll use the multi select filter.

Create "UX/Modules/Bands/Model/GenreFilter.php":

namespace UX\Modules\Bands\Model;

use IFW\Data\Filter\FilterOption;
use IFW\Data\Filter\MultiselectFilter;
use IFW\Orm\Query;
use PDO;

class GenreFilter extends MultiselectFilter {

     * Applies the filter on a store query
     * @param Query $query
    public function apply(Query $query) {

        $selected = $this->getSelected();

        if(!empty($selected)) {

     * Get's all genres
     * Uses a distinct select query on the album genre column
     * @return string[]
    public function getOptions() {
        $genres = Album::find(
                        (new Query())
                        ->fetchMode(PDO::FETCH_COLUMN, 0)

        $options = [];
        foreach($genres as $genre) {
            $options[] = new FilterOption($this, $genre, $genre, $this->count($genre));

        return $options;


     * Counts the number of occurenses but also applies all selected filter 
     * options in this query.
     * @param string $genre
     * @return int
    private function count($genre){

        $query = $this->collection->countQuery();        
        $query->where(['albums.genre' => $genre]);

        return (int) call_user_func([$this->collection->getModelClassName(), 'find'], $query)->single();


Applying filters

We'll add this filter in a collection that we create in the band module.

Edit 'UX/Modules/Bands/Model/Band.php' and add this use:

use IFW\Data\Filter\FilterCollection;

and this function:

public static function createFilterCollection() {
    $filters = new FilterCollection(Band::class);        

    //Adds custom field filters automatically
    Field::addFilters(BandCustomFields::class, $filters);

    return $filters;

Now we must attach this filter in the BandController. Edit "UX/Modules/Bands/Controller/BandController.php" and add an action to get the filters:

Add these uses:

use GO\Core\CustomFields\Model\Field;
use IFW\Data\Filter\FilterCollection;
use UX\Modules\Bands\Model\BandCustomFields;

Add this action:

public function actionFilters() {

And finally modify actionStore to apply the filters to the store query. I've also add the debug() call to the query so we can see the SQL in our debug output:

protected function actionStore($orderColumn = 'name', $orderDirection = 'ASC', $limit = 10, $offset = 0, $searchQuery = "", $returnProperties = "", $where = null) {

    $query = (new Query())
                    ->orderBy([$orderColumn => $orderDirection])

    if (!empty($searchQuery)) {
        $query->search($searchQuery, ['t.bandname']);

    if (!empty($where)) {

        $where = json_decode($where, true);

        if (count($where)) {

    //Add this line to apply the filters

    $bands = Band::find($query);


Using the filters

To demonstrate the filters we must have band with a different genre. Login as user "admin" again and do this POST request to "/bands":

    "data": {
        "name": "Katy Perry",
                "albums": [{
                    "name": "Prism",
                    "genre": "Pop"

Each filter has a name that defaults to the class name. The function getName() can be overridden to change the name but in most cases this won't be necessary. The name is also used as query paramter to send the filter value. Multiple values are separated by a comma. So to filter on genre we can do this request:

GET http://localhost/api/bands?GenreFilter=Rock,Pop

Remove Pop or Rock to see different results.

Getting the filters

In the controller we've also created a new action to get the filter information. First we must create a route to this action in "UX/Modules/Bands/Module.php":

public static function defineWebRoutes(Router $router) {

                    ->get('bands/hello', 'name');

                    ->get('bands', 'store')
                    ->get('bands/0', 'new')
                    ->get('bands/:bandId', 'read')
                    ->put('bands/:bandId', 'update')
                    ->post('bands', 'create')
                    ->delete('bands/:bandId', 'delete')

                    //Add this route
                    ->get('bands/filters', 'filters');

Now we can do a GET request on "/bands/filters". Note that in this example the "value" and "label" are identical because we don't have a table with id and name for the genres. The response looks like this:

  "filters": [
      "name": "GenreFilter",
      "label": null,
      "type": "multiselect",
      "clearFilters": [],
      "selected": null,
      "options": [
          "count": 1,
          "label": "Rock",
          "value": "Rock",
          "selected": true,
          "className": "IFW\Data\Filter\FilterOption"
          "count": 1,
          "label": "Pop",
          "value": "Pop",
          "selected": false,
          "className": "IFW\Data\Filter\FilterOption"
      "className": "UX\Modules\Bands\Model\GenreFilter"
  "count": 1,
  "className": "IFW\Data\Filter\FilterCollection",
  "success": true

Passing filter options

Each filter option also returns the number of occurrences in the "count" property.

We can also pass the same get parameters to this action so the counts update with that option enabled:

Do a get with GenreFilter=Rock and you'll get count=0 for Pop in the result. This is because there are zero Pop bands that also have the Rock genre.

You can do the same for the route '/bands'. Do a GET request to '/bands?GenreFilter=Rock' and you'll only get the bands with a Rock album.