Page History

...

A generic Magnolia configuration is used for all workspaces. This configuration fine-tunes the default Jackrabbit search configuration for best results. The sections that follow detail the enhancements.

 Special characters

Excluding nodes

Magnolia typically stores many properties, such as author, modification dates, templates etc., that are not relevant in search results. To minimize the index and speed-up search, all properties starting with jcr: or  mgnl: are excluded from the index. This means you get fewer results but those results are more relevant.

<index-rule nodeType="nt:base">
    <property isRegexp="true" nodeScopeIndex="false">mgnl:.*</property>
    <property isRegexp="true" nodeScopeIndex="false">jcr:.*</property>
    <property isRegexp="true">.*:.*</property>
</index-rule>

Boosting title property

Magnolia 5.5.9+:  The generic indexing configuration used for all workspaces but the website workspace is stored in /info/magnolia/jackrabbit/indexing_configuration_default.xml . The indexing configuration for the website workspace is in /info/magnolia/jackrabbit/indexing_configuration_website.xml . You can configure indexing for additional workspaces by setting the workspace name

in <param name="indexingConfiguration" value="/info/magnolia/jackrabbit/indexing_configuration_${wsp.name}.xml"/> in the workspace.xml configuration file.

If you are updating your Magnolia to 5.5.9 or later, we recommend you to set the indexing configuration by specifying workspace name(s) in the indexingConfiguration parameter.

These configurations fine-tune the default Jackrabbit search configuration for best results. The sections that follow detail the enhancements.

 Special characters

Excluding nodes

Magnolia typically stores many properties, such as author, modification dates, templates etc., that are not relevant in search results. To minimize the index and speed-up search, all properties starting with jcr: or  mgnl: are excluded from the index. This means you get fewer results but those results are more relevant.The configuration boosts the title property of the mgnl:page node type since page titles are important.

<index-rule nodeType="mgnlnt:pagebase">
 
   <property boost="3.0">title</property>
</index-rule>

Including areas and components 

The configuration uses index aggregates to ensure area and component content is included in the index. The properties of mgnl:area and mgnl:component make up most of the contents of a page and need to be included explicitly. The aggregate also simplifies searching for content within pages. 

 isRegexp="true" nodeScopeIndex="false">mgnl:.*</property>
    <property isRegexp="true" nodeScopeIndex="false">jcr:.*</property>
    <property isRegexp="true">.*:.*</property>
</index-rule>

Boosting title property

The configuration boosts the title property of the mgnl:page node type since page titles are important.Nested areas are also included using the recursive flag. 

<aggregate<index-rule primaryTypenodeType="mgnl:page"> 
   <property <include primaryTypeboost="3.0">title</property>
</index-rule>

Including areas and components 

The configuration uses index aggregates to ensure area and component content is included in the index. The properties of mgnl:area and mgnl:component make up most of the contents of a page and need to be included explicitly. The aggregate also simplifies searching for content within pages. 

Nested areas are also included using the recursive flag. 

<aggregate primaryType="mgnl:page">
    <include primaryType="mgnl:area">*</include>
    <include primaryType="mgnl:component">*</include>
</aggregate>

<!-- areas can be nested. See mgnl:area">*</include>
    <include primaryType="mgnl:component">*</include>
</aggregate>

<!-- areas can be nested. See http://wiki.apache.org/jackrabbit/IndexingConfiguration for recursion -->
<aggregate primaryType="mgnl:area" recursive="true">
    <include primaryType="mgnl:component">*</include>
    <include primaryType="mgnl:area">*</include>
</aggregate>

...

...

...

SELECT * FROM [nt:base] AS t WHERE 
   ([jcr:primaryType] = 'mgnl:asset' AND 
   [type] <> 'jpg') AND 
   ISDESCENDANTNODE([/example]) 
ORDER BY [t].title asc

Security

...

Solr module

...

].title asc

Security

Search within Magnolia is access controlled. Search results include only content the user has permission to access. Permissions are controlled through Security. When you execute a query in Magnolia context (

Solr module

For more advanced search options you can use the Solr module. This module uses the  Apache Solr  search platform to index and crawl Magnolia content. Solr is a standalone enterprise search server with a REST like API. Solr uses the Lucene library for full-text indexing and provides advanced features such as faceted search, distributed search and index replication.

Magnolia 5.5.9+:  The generic indexing configuration used for all workspaces but the website workspace is stored in /info/magnolia/jackrabbit/indexing_configuration_default.xml . The indexing configuration for the website workspace is in /info/magnolia/jackrabbit/indexing_configuration_website.xml . You can configure indexing for additional workspaces by setting the workspace name

in <param name="indexingConfiguration" value="/info/magnolia/jackrabbit/indexing_configuration_${wsp.name}.xml"/> in the workspace.xml configuration file.

These configuration fine-tune the default Jackrabbit search configuration for best results. The sections that follow detail the enhancements.

If you are updating your Magnolia to 5.5.9 or later, we recommend you to set the indexing configuration by specifying workspace name(s) in the indexingConfiguration parameter.