Consistent search fields between posts and terms

[ashworthcreative]

Searching for posts currently checks the post_title and post_content fields, while searching terms checks the name and slug fields. Could post_name be added to the where clause for posts, and description be added to terms? That way, searching would consistently check an entity's title, slug, and content.

[DrewAPicture]

I'd be interested in @johnbillion's take on adding these extra searchable fields by default.

[johnbillion]

Makes sense, but some performance impact numbers will be needed to ensure search queries don't get slowed down any more than they already are.

[SirLouen]

Replying to johnbillion:

Makes sense, but some performance impact numbers will be needed to ensure search queries don't get slowed down any more than they already are.

Without search restriction parameters in the UI, performance impact is going to be always there and not much we should do about it, considering that currently search for posts is being done in Content, which is, by far the worse of all in terms of performance, not any close (more with the current content GB formats)

Personally I believe that search by post_name can be a little overkill and searching by Term description, I'm no going to say that is the most demanded feature, but its fair and gives consistency. (Also searching by slug in terms was an overkill also, clearly a poor design feature that was decided on the fly for the sake of adding it)

Do we want to provide consistency for all 3, title/slug/content? Then both should be added.

For testing is pretty simple: Just add a random word to slug in posts or description in terms, and search for it.