Closed (fixed)
Project:
Search API (8.x)
Component:
Framework
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
2 May 2014 at 14:13 UTC
Updated:
6 Aug 2014 at 08:20 UTC
Jump to comment: Most recent, Most recent file
The per filter settings (admin/config/search/search-api/index/[filtername]/filters),
coming from the FieldsProcessorPluginBase settings form (Fields to run on),
affect always all filters, instead of only the desired one.
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | 2257113-07.search_api.processor-fields.patch | 1.41 KB | ekes |
Comments
Comment #1
drunken monkeyCould you please elaborate?
Comment #2
ytsurkComment #3
drunken monkeyI still don't know what you mean. I just tested this, and everything seems to work fine. What steps are you executing exactly, what do you expect to happen and what does?
Comment #4
ytsurkthe fields to run on property (if existing for the processor - fe. Transliteration & Ignore case) share this property.
both have it in their settings tab - but a change always affects both - clearer now ?
Comment #5
ekes commentedHaving just done a clean install (with at least) Ignore case & HTML filter on indexes I can't save the settings for which fields they apply to at all. Other settings for the filter are saved.
Comment #6
ekes commentedComment #7
ekes commentedThe fields a processor/filter operate on are stored with the index entity. So are specific to that entity.
However the index was now 'field' => 0; #disabled 'field' => 1; #enabled. The form was expecting only 'field' where enabled.
If this wants tests they are tests of the form?
Comment #10
ekes commentedPushed to master.
Comment #22
drunken monkeyThis seems to be fixed?