...
Info |
---|
Implantation and availability of a handler sometimes depends on SearchEngine capabilities/limitations. |
Common concepts for all SortClausesSort Clauses
For how to use each and every SortClause see list below as it depends on the SortClause Value constructor, but in general you should be aware of the following common concept:
sortDirection
: The direction to perform the sort, either Query::SORT_ASC
(default) or Query::SORT_DESC
List of SortClausesSort Clauses
The list below reflects SortClauses Sort Clauses available in eZ\Publish\API\Repository\Values\Content\Query\SortClause
namespace (it is also possible to make custom SortClause):
Info |
---|
Arguments starting with "? " are optional. |
Only for LocationSearch
SortClauseSort Clause | Constructor arguments description |
---|
Location\Depth Status |
---|
colour | Yellow |
---|
title | >= 5.3/2014.03 |
---|
|
| ?sortDirection |
Location\Id Status |
---|
colour | Yellow |
---|
title | >= 5.3/2014.03 |
---|
|
| ?sortDirection |
Location\IsMainLocation Status |
---|
colour | Yellow |
---|
title | >= 5.3/2014.03 |
---|
|
| ?sortDirection |
Location\Depth Status |
---|
colour | Yellow |
---|
title | >= 5.3/2014.03 |
---|
|
| ?sortDirection |
Location\Priority Status |
---|
colour | Yellow |
---|
title | >= 5.3/2014.03 |
---|
|
| ?sortDirection |
Location\Visibility Status |
---|
colour | Yellow |
---|
title | >= 5.3/2014.03 |
---|
|
| ?sortDirection |
Only for ContentSearch
SortClauseSort Clause | Constructor arguments description |
---|
LocationDepth Status |
---|
colour | Red |
---|
title | deprecated in 5.3/2014.03 |
---|
|
| Use LocationSearch with Location\Depth , since LocationDepth can give unpredictable results when content has several locations. |
LocationPath Status |
---|
colour | Red |
---|
title | deprecated in 5.3/2014.03 |
---|
|
| |
LocationPathString Status |
---|
colour | Red |
---|
title | deprecated in 5.3/2014.03 |
---|
|
| |
LocationPriority Status |
---|
colour | Red |
---|
title | deprecated in 5.3/2014.03 |
---|
|
| Use LocationSearch with Location\Priority , since LocationPriority can give unpredictable results when content has several locations. |
Common
SortClauseSort Clause | Constructor arguments description |
---|
ContentId | ?sortDirection |
ContentName | ?sortDirection |
DateModified | ?sortDirection |
DatePublished | ?sortDirection |
Field | typeIdentifier as string, fieldIdentifier as string, ?sortDirection, ?languageCode
Status |
---|
colour | Yellow |
---|
title | >= 5.3/2014.01 |
---|
| as string |
MapLocationDistance Status |
---|
colour | Yellow |
---|
title | >= 5.3/2014.03 |
---|
|
| typeIdentifier as string, fieldIdentifier as string, latitude as float, longitude as float, ?sortDirection, ?languageCode as string |
SectionIdentifier | ?sortDirection |
SectionName | ?sortDirection |