You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't know if this is a bug in upstream SearchAPI or a configuration problem...
The {search_api_db_localgov_directories_index_default_text} table has lots of entries for words which appear to be from HTML tags and attributes:
div
field
'node content'
This means that if you search for 'field' you get ALL results. For technical words like div or node that doesn't matter so much, but if a school was called something like 'King George V Field', it's going to be hard to search for.
The text was updated successfully, but these errors were encountered:
Thanks @joachim-n
Very interesting!
I'm just looking at the default settings for the index, as the title field does not seem to get indexed at present, on a default install.
Strips HTML tags from fulltext fields and decodes HTML entities. Use this processor when indexing HTML data – for example, node bodies for certain text formats. The processor also allows to boost (or ignore) the contents of specific elements.
Indeed.... as you mention @joachim-n , searching for "field" brings back all results on a default install of localgov_directories, as demonstrated if we enable the localgov_demo module and search for field on the collaborators demo content:
I don't know if this is a bug in upstream SearchAPI or a configuration problem...
The {search_api_db_localgov_directories_index_default_text} table has lots of entries for words which appear to be from HTML tags and attributes:
This means that if you search for 'field' you get ALL results. For technical words like div or node that doesn't matter so much, but if a school was called something like 'King George V Field', it's going to be hard to search for.
The text was updated successfully, but these errors were encountered: