The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.When changing a field's type from "fulltext" to something else, the field should be removed from some processor configurations (e.g., tokenizer).
Comments
Comment #2
drunken monkeyJust tried it out myself and could indeed reproduce the problem. A bit of debugging revealed that this was caused by the "Tokenizer" processor, which was still set to work on this field, even though it should never be active for string fields. Re-saving the "Processors" form without any changes fixed the problem for me.
Could you try whether this is also the case for you? Then I guess the issue would be to react to field changes with the processors, or to ensure processors check the field type again before running – or both.
Comment #3
strykaizerAfter saving the processors form, for me it also works again.
Comment #4
drunken monkeyDamn, then that's another thing to be solved in the framework before we can call it stable.
Comment #5
drunken monkeyOh, nevermind, we do have
preIndexSave()already.Just need to implement it for whichever processor needs to, and probably add some tests.
Comment #6
drunken monkeyComment #7
drunken monkeyPretty straight-forward, but should fix that problem nicely. (Also, I guess a similar problem exists when removing fields from the index? Is fixed with this patch, too.)
Comment #9
borisson_Comment #11
drunken monkeyThanks, committed.