[UPDATE] Thanx to Phoenix, found out that *yes*, in the midst of recent database load changes, Search functionality was tweaked. This includes:
* classifieds searches use name prefix matching instead of word in
name or word in description
* group member titles are no longer part of the search
* group name searches use prefix matching
* groups are not retuned in any particular sort order
* event searches only use name prefix matching instead of word in
name or word in description
Tentatively, we're open to changing some of this back, but we need to figure out first what's the root of the problems. Hope this helps!
* classifieds searches use name prefix matching instead of word in
name or word in description
* group member titles are no longer part of the search
* group name searches use prefix matching
* groups are not retuned in any particular sort order
* event searches only use name prefix matching instead of word in
name or word in description
Tentatively, we're open to changing some of this back, but we need to figure out first what's the root of the problems. Hope this helps!
I can search for my two store ads by searching for "Ceera", and it shows "Ceera's Fashions" at both locations. But if I search for "Fashions" I get NO RESULTS AT ALL. The only way to search for and find my ad for "Fox and Ground Construction Company" is to search for "Fox".
That is worse than worthless, Torley! The search needs to be able, at the VERY LEAST, to return a match on any word in the name or description fields!
I am cancelling renewal on my ads until this is fixed. It's certainly not a functional service as it stands, and whoever says it is is just trying to cover their own ineptitude. If you ask me, and I am certain that almost everyone who pays good money for these ads will agree, LL needs to extend the paid time on every single ad, one day's extension for each and every day that Search has been worthless, or else pay a cash refund for services contracted but not delivered.
PS: Today's unscheduled, forced update to 1.13.0.10 did not fix this.