I just ran some simple tests in 2.2.0b1, and as far as I can see, text field searching is still broken. A two word search string, one word of which is valid (and returns results when used by itself) and one of which is not yeilds no hits. This is true regardless of whether or not the words are joined by an 'or' or a 'not'. Also, a keyword such as 'T-shirt' results in an object that cannot be found with either 't' or 'shirt' or 't-shirt'. However, the behavior of stop words seems to be fixed: if one of the two words is a stop word, hits are found as one would expect, with both 'and' and 'or' and no connective returning the hits from the non-stopword of the pair. --RDM