Page MenuHomePhabricator

Unknown search function "XXX". Supported functions are: all, title, body, core, comment.
Closed, ResolvedPublic

Description

Searching for foo:bar in Maniphest yields Unknown search function "foo". Supported functions are: all, title, body, core, comment..

Given that semicolon is very common in error messages that one searches for often (PHP static calls, for example), this seems like a very annoying way to handle unrecgnized keyword-like search terms.

Event Timeline

Aklapper triaged this task as Lowest priority.Jan 23 2020, 12:00 PM
Aklapper edited projects, added Phabricator (Upstream); removed Phabricator.

Not related as I've experienced this before.

This is expected behavior. Syntax is documented in https://www.mediawiki.org/wiki/Phabricator/Help#Search_terms , see "Field Search" in https://secure.phabricator.com/book/phabricator/article/search/ for upstream documentation. Workaround is to use quotation marks around your term.

epriestley subscribed.

This error got a little stricter recently so it might crop up more often after the next upgrade, and it's normally hard to hit by accident so I don't mind being more verbose in handling it. I can add a hint to the error message, something like:

To search for a term containing a colon, use quotation marks.

There are also two new field operators (title:- for "field is absent" and title:~ for "field is present") in the current release. They're fairly niche/specialized but maybe they'll be helpful in some edge cases.

epriestley moved this task from Reported Upstream to Patch merged upstream on the Upstream board.

I added a hint about this to the upstream in https://secure.phabricator.com/D21209.

... (To search for a term containing a colon, surround the term in double quotes.)

Screen Shot 2020-05-03 at 9.32.04 AM.png (179×1 px, 22 KB)

It nowadays says Unknown search function "foo". Supported functions are: all, body, comment, core, title. (To search for a term containing a colon, surround the term in double quotes.) (as described by Evan in the previous comment)