PHPackages aplia/filter - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. [Search & Filtering](/categories/search) 4. / 5. aplia/filter ActiveEzpublish-legacy-extension[Search & Filtering](/categories/search) aplia/filter ============ Flexible and extendible attribute filters for eZ publish legacy v2.4.1(6y ago)087GPL-2.0PHPPHP >=5.3 Since Aug 25Pushed 6y ago4 watchersCompare [ Source](https://github.com/Aplia/ezp-content-filter)[ Packagist](https://packagist.org/packages/aplia/filter)[ Docs](https://github.com/Aplia/ezp-content-filter)[ RSS](/packages/aplia-filter/feed)WikiDiscussions master Synced 6d ago READMEChangelogDependencies (1)Versions (10)Used By (0) Aplia Content Filter ==================== [](#aplia-content-filter) Advanced filter support for content objects in eZ publish legacy. The filter support nested structures with `AND` and `OR` operations and more. It effectively replaces other specific filter extensions such as `OWOrFilter`, as well as regular attribute filters. This installs as an extension called `apliafilter` and provides an attribute filter called `NestedFilterSet`. [![Latest Stable Version](https://camo.githubusercontent.com/0f75dc043053ec5d7e4af0fc3bfe9f167d37a0d342423d2725e6deb6233b335e/68747470733a2f2f696d672e736869656c64732e696f2f7061636b61676973742f762f61706c69612f66696c7465722e7376673f7374796c653d666c61742d737175617265)](https://packagist.org/packages/aplia/filter)[![Minimum PHP Version](https://camo.githubusercontent.com/b3f29eb7882d2bf523390e9982827e9d2d3a4f74266ca923b512e5d02b9e4011/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f7068702d253345253344253230352e332d3838393242462e7376673f7374796c653d666c61742d737175617265)](https://php.net/) Installation ------------ [](#installation) Install this extension using composer: ``` composer require aplia/filter ``` Usage ----- [](#usage) When listing content objects this filter can be enabled by installing it as an extended attribute filter, then using `params` to define a nested structure. The structure will then be transformed into SQL queries and added to the normal content object query. For instance in a template one can do: ``` {fetch('content', 'list', hash( 'parent_node_id', 2, 'depth', 20, 'limit', 10, 'sort_by', array('published', false()), 'class_filter_type', 'include', 'class_filter_array', array('article'), 'extended_attribute_filter', hash( 'id', 'NestedFilterSet', 'params', array( array(array('article/type'), $type), ) ) ) )} ``` A similar example in PHP: ``` \eZContentObjectTreeNode::subTreeByNodeId( array( 'Depth' => 20, 'Limit' => 10, 'SortBy' => ['published', false], 'ClassFilterType' => 'include', 'ClassFilterArray' => ['article'], 'ExtendedAttributeFilter' => [ 'id' => 'NestedFilterSet', 'params' => array( 'cond' => 'OR', 'attrs' => array( ) ), ], ), 2 ); ``` NestedFilterSet --------------- [](#nestedfilterset) An extended attribute filter which allows for nested structures and unifies attribute filters and extended attribute filter. The filter can be extended with custom classes which allows it to get around the problem that only one extended attribute filter may be used. The filter also supports filtering on multiple content classes at the same time, it will do an outer join with the attribute table in this case. The following elements can be extended: 1. Data-Types 2. Modifiers 3. Attributes See filter.ini.append for configuration. ### Syntax [](#syntax) The syntax of each attribute filters are an array containing the attribute name and the value, e.g. ``` ['name', 'foo'] ``` The attribute name may also contain modifiers and an operator (default is `=`). e.g. ``` ['my_class/size:>', 5] ``` The operators supported are the same as for the attribute filters in eZ publish. - `=` - `!=` - `>` - `>=` - ` 'and'/'or', 'attrs' => [...] ``` This defines a list of attribute filters with either an `and` or `or` condition between each filter. A shorthand is available by just supplying a list of attribute filters, it will then default to `and` as the condition. Entries in the `attrs` list is either defined as an array with `key` and `value`, like this: ``` [ 'name' => 'foo', 'folder/title' => 'bar', ] ``` or as an array with each entry being an array containg the attribute name and value, like this: ``` [ ['name', 'foo'], ['folder/title' => 'bar'], ] ``` The latter form allows for having the attribute name as an array of names, in which case it will filter the value on all attributes with an `or` condition. ``` [ [['folder/title', 'article/title'] => 'bar'], ] ``` The long-form of this would be: ``` [ [ 'cond' => 'or', 'attrs' => [ 'folder/title' => 'bar', 'article/'title' => 'bar', ], ] ] ``` The attribute entry may also contain the array key `call`, which means that a callback is used to fetch the filter structure. The callback may either return a normal structure as extended attribute filters does or return a new attribute filter structure, if the `cond` key is not used it will assume the `and` condition and wrap it into a long-form structure. The value for the `call` is any callback structure supported by PHP. A full example: ``` [ ['folder/is_public', true], [ 'cond' => 'or', 'attrs' => [ 'folder/title' => 'bar', 'article/'title' => 'bar', ], ], [ 'call' => ['MyClass', 'makeFilter'], ] ] ``` ### Data-Types [](#data-types) These are handlers for the content class datatypes which allows for dynamic attribute names to be used. The content class attribute is looked up and the first handler to support the data-type will be used for creating joins and the filter. The following specialized data-types are supported: - ezobjectrelation - ezobjectrelationlist - ezselection In addition it supports datatypes from the following extensions: - eztags - Filters on the eztags keyword ids The others falls back to a default handler which uses `sort_key_string` or `sort_key_int`. Data-Type handlers are specified using the classname with namespace prefixed. ### Modifiers [](#modifiers) Modifiers are simple callbacks which can wrap SQL functions around the fields or values. Modifiers are specified in the attribute string, either before or after the operator. `created:date` would wrap the `created` field in a `DATE()` SQL call while `created:=:date` would wrap the matching value. Modifiers may also be specified in the `array()` form of a filter as the fourth parameter. e.g. ``` ['folder/name', '=', 'A', ['pre' => 'first_letter']] ``` Modifiers must be defined in `filter.ini` and point to a static method in a class, the method will then receive one parameter which is name of the field and the method must return a string with the SQL code which modifies the field. e.g. to get the first letter one might do this: First define the filter name and place the full namespace for the class + `::` and the method name. ``` #filter.ini [Handlers] Modifiers[first_letter]=MyClass::firstLetter ``` Then define the code ```