-
Your queries must have been a bit messed up as I searched by author all of the time (I'd forget where somebody posted something but remembered who posted it)
EDIT: By 'all of the time' I clearly meant 'once in a while'
arrowplum-
Your queries must have been a bit messed up as I searched by author all of the time (I'd forget where somebody posted something but remembered who posted it)
EDIT: By 'all of the time' I clearly meant 'once in a while'
I specifically qualified my statement by pointing our that vBulletin cached the queries, and it was the cache I looked at.
Out of the ~15,000 queries that were cached, none were for an author search.
That doesn't mean no-one ever did an author search, it only means: in the cache, representing a few days of query, there were no searches by author.
So whilst they do happen, there are extremely rare relative to all other kinds of search.
Given that information... is this the highest priority work I could be doing when the means to perform the search exists already? My conclusion, no. Other real bugs and issues do exist that are directly impacting some people, those take priority.
Velocio
Search in thread is already there... on the right (probably near the top) >>>>
With author, I'm prioritising other more essential bugs as I couldn't find an example of anyone searching by author in the old vBulletin database (it cached queries, I could see the args).
Because we already support it with
authorId:47714(for you) I'm treating it as lower priority than other more critical bugs that break layout or are navigation papercuts, etc.When we've done all of the more critical things or low hanging fruit, we'll re-visit search to add authorId using a better method (most likely an @ autocomplete).