Does anyone have any experience with the OFFLINE SiteSearch and Tailor?
The search works so far but it doesn’t seem to work when I use it in a blueprint with groups.
From the documentation:
# your-blueprint.yaml
siteSearch:
providerBadge: MyEntry # Display this beside each search result.
pageName: 'cms-page' # Filename of the target CMS page, used to build links.
urlParams: # Given a page URL: /target-cms-page/:slug/:something
- slug: $slug # Use the value of the "slug" field, since it is prefixed with a "$"
- something: else # Use the literal string "else", since there is no $-prefix
# the output is: /target-cms-page/slug-field-value/else
# See "Custom URL Resolver" below
# This is used *instead of* pageName + urlParams
urlResolver: '\App\Provider::resolveSiteSearchUrl'
searchFields: # Fields to search in.
- title
- description
- something_elase
resultFields:
title: title # Use the "title" field as the search result title
text: description # Use the "description" field as the search result text
Is it possible to nest the searchFields or something?
The title and content fields from your example should be search correctly now. I’m not sure where the answer field comes from, so this probably won’t work.
so…I did a bit of testing and noticed the following:
The dump shows all fields of the blueprint in which siteSearch was integrated. However, only from one Blueprint. If I comment out the siteSearch in all other blueprints, the search in the content field from the post earlier works. That means… if the siteSearch is integrated in another Blueprint, it no longer works.
I’m trying to sort out a similar thing. I have a similar setup to you initially, but my Builder mixin has more groups/mixins in it. These are what I’d like to be searched but I’m not sure if it’s possible.
I’ve tried adding ‘builder’ to the searchFields property, but I just get a column not found in database error. Which makes sense.
Any advice on what I need to do to be able to search through these nested mixins?
