Search extensions

The paging of the search can be customised. In this way, cases in which the number of hits per page varies can also be mapped.
For example, the first page should only list 5 hits for an initial display of the hit list. After user interaction to display further results, however, more hits should be displayed quickly, e.g. 10 hits per page.

The authorisation for the search can be adjusted so that the rights check is only carried out after the request to the search server.
One use case is a search query in an area that is largely authorised for anonymous users and where the results are not paged on the server side - or where it is not necessary to take into account that individual pages are not loaded during paging.

By default, the search is called via the SearchController and therefore via an explicit service such as ‘search’.
With this extension, it is possible to integrate the search into a template.
An example of its use is provided in the SDK tutorial in the "searchCaller" plugin.

References can be filtered in the search if the original content is contained in the search result.