The SuluSearchBundle is mainly an integration of the MassiveSearchBundle into Sulu. There is also the MassiveSearchBundle Documentation explaining this Bundle in more detail. This documentation is also valid for using it with Sulu, although there are some extensions made by the SuluSearchBundle. It offers a controller to provide a web API to search through the system, adds more fields - like creator and changer - to the search documents and also handles the security provided by Sulu. But the most important thing is that it also contains the administration user interface.


The configuration of this bundle contains some more metadata about each index created by the MassiveSearchBundle. There are two optional values, meaning both of them could be omitted:

  • name: Can contain a name for the index, which will be used in the UI. Useful if the index represents something a non-translatable literal can describe.
  • security_context: This setting is used to describe which security context (see SecurityBundle) the user has to have view permission in, in order to search through this index.

So a sample configuration would look like this:

            security_context: sulu.contacts.people
            contexts: []

The values under indexes, namely contact in this example, result from the index tag in the mapping configuration. The value of security_context indicates that the user has to have the permission to view the sulu.contacts.people security context to see result from the contact index. The contexts configuration is optional, and can be used to filter the indexes in an application. This is used e.g. for the search in the admin.


It is also possible to use PrependExtensions or in more complicated cases to change the value of the sulu_search.indexes parameter in a CompilerPass. Actually that is what most of the Sulu bundles are doing to minimize the configuration effort of the application.

That would be enough for the user to retrieve some search results, but a click on these results would not lead to the corresponding form. So the last missing step is to tell the system how to load this form when clicking on a search result. This has to be done in the main Javascript entry point of the bundle, which is located at Resources/public/js/main.js. A line like the following has to be added to the initialize method:

    'contacts/contacts/edit:<%= id %>/details'

This line tells the urlManager, which is responsible for creating the URLs for the search, how the entry from the search has to be resolved. The variables from the search document can also be used in the template, which is passed as the second argument.

For more complex cases there are two more parameters in the setUrl function, which are shown in the next example.

    function(data) {
        return 'content/contents/<%= webspace %>/<%= locale %>/edit:<%= id %>/content';
    function(data) {
        return {
            url: data.url,
            locale: data.locale
    function (key) {
        if (key.indexOf('page_') === 0) {
            return 'page';

The first argument is again the name of the index, the second one a function, returning a string for the Javascript template engine. The third is a handler returning a new object from the given data, which will passed to the template engine in combination with the string being returned from the second argument. Finally, the fourth argument is the key modifier, which takes the name of the index, and can modify it, before it is compared with the first argument from all setUrl calls. This is especially useful if the ExpressionLanguage is used for the generation of the index name.


The SuluSearchBundle has a WebsiteSearchController, which loads the template from the currently loaded webspace. It therefore uses the RequestAnalyzer, and asks the webspace for its template of type search. This template can then be defined for every webspace in its XML configuration:

    <template type="search">ClientWebsiteBundle:views:search.html.twig</template>

See Setup a Webspace for more details.


Re-indexing is the process of reading all of the documents in the system and regenerating their search records. This is necessary when changes are made to the metadata and it is desirable to propagate these changes over all of the indexed documents / entities in the system – or when you import new data (e.g. from a backup) and need to index that data.

To re-index all entities (Contacts, Media, etc.) and documents (Pages, Snippets) simply run the following:

$ ./app/console massive:search:reindex --env=prod


At the moment it is required to also execute ./app/webconsole massive:search:reindex –env=prod to reindex the pages also for the website.

This may take anywhere between a minute and several hours depending on how much data you have in your system.

To increase speed and reduce memory consumption:

  • Use the --env=prod (see note below) switch to force the production settings: This will reduce logging and increase speed and lead to lower memory consumption.
  • Ensure that the document manager has the debug: false option. This reduces logging dramatically.
  • Use PHP 7: This will increase indexing speed up to 10 times.

To recover if the process is interrupted:

  • You may resume the task simply by running it again.
  • Use the --provider option to limit the reindexing to a certain reindex provider, for example --provider=doctrine_orm.


In recomending the prod environment we assume that you have not changed the default environment configuration. The important point is that logging increases memory consumption and should be disabled.