The Find Bar is the heart of the Magnolia user interface. It is the central starting point for all your tasks: search through content across apps, open apps and access items directly. The Find Bar searches and adapts its results in real time as you type. It offers full text search and precise filters for you to make the most of your content. You can plug in any REST-compliant data source to be able to search through content that is not stored in Magnolia too.
The Find Bar allows you to search across all content search inside and outside Magnolia (federated search, enterprise search). The search covers all Magnolia and custom content apps, assets and pages. Developers can integrate external datasets using the API.
Start typing in the Find Bar to see search results adapt in real time to keywords. Results are pre-sorted by app as well as type of content (e.g. app, page, story, asset or tour).
Use the Up and Down arrow keys to move through search results. Press Enter to open the highlighted result.
The Find Bar automatically recognizes any command you enter. To execute, press Enter or use the speech recognition functionality.
Since Magnolia 6.2.6, full text search is also possible in chooser dialogs of apps that use the JCR data source:
Currently, only a single JCR workspace can be searched.
Since Magnolia 6.2.2, you can use the Find Bar to search for a specific path. This allows you to reach a target node more quickly than by checking an app’s node tree or by browsing search results supplied for a less specific keyword or phrase.
You can use the Find Bar to search not only through all your Magnolia content but also through content stored in external data sources. To do so, developers can build custom search result suppliers extending the Find Bar’s capabilities using a purpose-built API. The API facilitates integration with any outside source such as assets stored on Flickr or your client data in a CRM application.
For configuration properties and an example showing how to configure a REST-based search result supplier, see REST search result suppliers for Periscope.
You can use multiple parallel filters to quickly narrow down your search results and find exactly what you are looking for without scrolling through dozens of results.
You can easily remove or refine the filter by type, tags (DX Core), latest editor or the date the content was last edited.
The Type filter lists all types of content that have been configured for search. By default, this includes all JCR content apps. External data sources can also be configured.
In the Tags filter, you can search through all the tags applied to your content in Magnolia.
If you use the Magnolia Image Recognition module, all automatically generated tags applied to your assets will be available here.
If you start searching while having an open app, Magnolia will automatically filter results based on the current app so you can get relevant results straight away.
The search results the Find Bar returns are relevant for each user. Admins can refine your search results based on your user role in Magnolia.
If you do not have access to the Assets app, for example, you will not get results from that app.
Search beyond text with the help of the Image Recognition module.
The Image Recognition module analyzes your assets and automatically tags them with content tags. The tags populate the Tags filter in the Find Bar, making your visual data searchable without requiring any time-consuming human intervention.
For example, an image automatically tagged as
lion will be returned
as a result if you search for
lion in the Find Bar even if the
image’s file name and metadata do not contain the word
You can talk to Magnolia to find content and open apps. The Find Bar
understands simple voice commands such as
find'' and ``open.
Click the microphone icon in the Find Bar, and talk to Magnolia. Your voice data is transcribed, displayed in the Find Bar search box and processed.
open pages app
open tours app
open definitions app
find botswana tour
find surfing asset
find asia story
Talk to our Travel Demo instance
(username / password:
See Web Speech API supported browsers. At the time of publication, only Google Chrome is supported.
You can configure how many search results are displayed. The configuration is found in the
config.yaml file under
/modules/admincentral/ in the Resource Files app. Please refer to the Admincentral module documentation for more details and configuration properties.
Table 1 below depicts two properties in the Admincentral module that affect the number of results shown.
optional, default is
Integer defining the maximum number of search results shown from any single search supplier.
optional, default is
Integer defining the grid size for content suggestions. Compare below
the default setting of
Open the Resource Files app.
Go to the
config.yamlfile under the admincentral folder.
Edit the file and update the properties that you want to change. For example, update
defaultCountPerSupplierto 20 if you want to see up to 20 search results.
Save your changes and then restart the webapp.