feat: relevanssi excerpt in search queries #5
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
closes #4
Tested in production and can be seen live here https://nordenmfg.com/?s=norden
Note
Medium Risk
Changes excerpt generation logic and global
$posthandling for REST query responses, which can affect search result formatting/highlighting and content returned by the API.Overview
Search queries using Relevanssi now return the plugin-generated excerpt (including highlighting) through the query REST API’s dynamic
postexcerptfield instead of always regenerating/stripping excerpts.To preserve Relevanssi data,
process_specific_dynamics()accepts an optional post object and callers pass theWP_Querypost through; excerpt output now conditionally returns raw highlighted HTML (no character limit) or a tag-stripped truncated version (with character limit).Written by Cursor Bugbot for commit bbd8f09. This will update automatically on new commits. Configure here.