I've just realized that, using 'Simple search', all one has to do to
get past the article title suggestions is lengthen ones search string
till it no longer exactly matches any article titles. Then, and only
then, does 'Simple search' take you to a search results page. Might
this simply be something folks need to learn to do, by doing? And
might it simply work? Are average users consistently so cleaver?
Argggg. I think if we lead them in the right direction it will work
fine. What do you think?
On Fri, Sep 6, 2013 at 8:27 PM, <roger(a)rogerchrisman.com> wrote:
Now that I
think about it, does the prefix search still work with that hack?
By work I mean you should be able to select one of the entries that pops
down under the search box as you type and it takes you to that article.
No, with the hack in place clicking on one of the drop down search
suggestions takes you to the search results page for that value, not
to an article page. That _is_ perhaps what I want. I want Search to
take you to a search results page, so that a user may choose which
page he wants.
Is the drop down list of search suggestions generated from a list of
the wiki's page titles? Hm, I guess it is. I had not realized that. So
how does one search the wiki's page texts? This whole search feature
seems to be designed to take a user to a destination article directly
whenever possible. I'm not sure that is best for my wiki because that
page may not always be the one a user wants and without the search
results page, how will he find the one he does want? By doing another
search with more search terms? Hm, maybe we can all get used to this
and maybe it will just work.
Argggg, and trying to change this designed in behavior may not be so
easy for a chiefly point and click guy like me.
So I may decide to use the two button ('Go' + 'Search') Search box
that I get when I set $wgVectorUseSimpleSearch to false, instead,
especially if this hack is not going to work in future.
Thanks for the tips.