Currently, processors will for the most part just run on any fulltext field coming along (or, in the case of the "Ignore case" processor, optionally also on strings). However, since processors have configuration forms, there is really no reason not to just provide a form where the user can select all fields the processor should run on. Probably as a scrollable select list, like for the "Aggregated fulltext fields" data alteration.

Right now, there is e.g. no way to tell the "HTML fitler" to only run on the node body, and not other, non-HTML fields. And I imagine that only in very few cases all fulltext data will be HTML.

CommentFileSizeAuthor
#2 search_api.processor_fields.patch11.58 KBdrunken monkey
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

drunken monkey’s picture

Component: Code » Plugins
drunken monkey’s picture

Status: Active » Needs review
Issue tags: +API change
FileSize
11.58 KB

Attached patch should do this. Please test.

Would be a small API change, as the abstract base class for processors was modified slightly.

drunken monkey’s picture

Status: Needs review » Fixed

Committed.

Status: Fixed » Closed (fixed)
Issue tags: -API change

Automatically closed -- issue fixed for 2 weeks with no activity.