After an exhausting week and a half tracking down the source of a mysterious bug in wpSearch, I think I can finally close the book on the “null result” issue that had me pouring over the source code.
wpSearch 220.127.116.11, the first official release after the 1.5 landmark, brings to the forefront some of the features and fixes slated in the last post. wpSearch 1.5 has had the following features implemented:
- Comment Searching
- A behind-the-scenes event logger for easily figuring out user issues
- An upgrade to the underlying Lucene Search
- An upgrade to the underlying StandardAnalyzer (used for relevancy)
And these fixes:
- No more null results after a post is edited
- Foreign character support (or simply indexing content with ‘UTF-8′ encoding
- Memory issues for content-heavy posts
wpSearch 18.104.22.168 is a rock-solid release that is starting to make a name for itself in the WordPress world. The new ‘Phone Home’ feature in wpSearch allows users to report their copy of wpSearch. A few of the blogs with wpSearch currently in use are listed here:
Of course, as far as wpSearch has come in its short lifespan, there exists a set of users that deserve credit for pointing out issues and keeping me informed of bugs, needed features, etc.. So, in no particular order, I would like to thank:
- ComputerBob, at ComputerBob.com for pointing out the first instance of the empty result issue. He has thoroughly documented his usage with wpSearch at his blog, in a fair and balanced fashion. Furthermore, he has sent his index data back with detailed comments when most users would simply give up on wpSearch. Thanks ComputerBob.
- Robert Irizarry, who has kept the wpSearch thread at the WordPress repository stuffed with feature ideas and issue notices.
- Olivier, who’s 6000 posts provided the first failed scalability test for wpSearch. His pointing out of this issue led to a change to allow for greater scalability — in other words, wpSearch 1.5 was tested successfully up to 7,000 posts. Great dedication to detailing these issues has helped wpSearch greatly.
- Karl Heigl, who first mentioned the fact the wpSearch was not handling German accents, and subsequently all foreign (to the U.S.) characters. This also ended up affecting Olivier. This bug was fixed in 22.214.171.124. Thanks Karl!
- A user named Brian, said, “Thanks for the update. If you need any other information or even help testing, I’d be happy to assist. Just let me know. ” Thanks for your support Brian.
- And to all those who have donated to this project so far!
So, wpSearch 126.96.36.199 wouldn’t be at it’s current status if it weren’t for those supporting it.
Features coming up for wpSearch include result highlighting, contextual snippets, and a progress meter for index building. I encourage everyone who is reading this but hasn’t installed wpSearch yet to try it out, and see the awesome blog search that you’ve been missing.