plone/plone.app.search — comment on commit 7402bd3fdd427b53bc3314e45f04c4c50003415e
File:  line 0
By mishunov:

Just to make it clear, guys, all of you are talking from the Plone developer a.k.a. "advanced user" point of view. It is absolutely valid and makes total sense. But when it comes to an end user, the expectations might be different.

Arguments like "livesearch is not search, this is why it has a different name." don't work for normal users. Guess what, they don't even know what the hell livesearch is and that it is called "livesearch" :) They have ONE search field and in most cases expect it to work consistently. What does matter for them is the fact that with previous implementation, by typing "auto" in the search field, they get different results in livesearch and on the actual search results page. In reality, for the end users it means "hey, guys, the search is broken — I get different results!". After all, any site, no matter whether it's Plone or not, should be built for "normal" people and from a normal user's perspective in the first place, unless it is explicitly dedicated to the developers.

Adding yet another option to a configlet… I think we have way too much things "burried" in the configlets and thus we need to think twice before adding anything else there. And that is the reason why we have removed 80% of the fields in that Search configlet.

But, the good news is, there is a workaround for those who need the old behavior. Just try typing something like 'auto *' in the search and here comes the old behavior — livesearch shows everything including 'automobile', 'automatic' and 'auto', but the search results page will show only items with 'auto'. Should be easy ;)

So, I consider this topic closed and there is no need to revert the commit ;)