Custom values in the search result list

By default the indexed content will be shown in the search result list (either the abstract or a part of the indexed content).

The partial for a single result row is stored at ke_search/Resources/Private/Partials/ResultRow.html.

If you want to adapt your search result list to show other content than the indexed content, e.g. the content of individual database fields, you have the following possibilities.

Format date for different locales

The date of the search result will printed if the setting Show date is activated in the plugin settings. You will get the date as a unix timestamp and can use the <> viewhelper to use different locales.


< format="%d. %B %Y">{resultrow.date_timestamp}</>

Accessing the original database row

The UID and the PID and also the original database row are available in the result list by using the following variables


The orig_row is only available for pages, news and tt_address records or if the key for a custom indexer is exactly the same as the corresponding table name (e.g. create a custom indexer for frontend users and use the key fe_users). But you can also register your own table names. See ke_search/Classes/Domain/Repository/GenericRepository.php.

Add a hook

You can add a hook additionalResultMarker in order to add more variables to the fluid template, see ke:search/Classes/Lib/Pluginbase.php.

Write a view helper

You could also write a view helper. Since you have the type and the UID of the original record available, you could pass this to the view helper and you are then free to create whatever content you want.

Debug available values

By adding


to the Fluid template, you can see all the available values for each result.