[wp-trac] [WordPress Trac] #25587: wp_search_stopwords filter shouldn't be cached
WordPress Trac
noreply at wordpress.org
Thu Oct 17 13:16:34 UTC 2013
#25587: wp_search_stopwords filter shouldn't be cached
-------------------------------------+------------------------------
Reporter: alex-ye | Owner:
Type: defect (bug) | Status: new
Priority: normal | Milestone: Awaiting Review
Component: General | Version: trunk
Severity: normal | Resolution:
Keywords: has-patch needs-testing |
-------------------------------------+------------------------------
Comment (by alex-ye):
Replying to [comment:3 azaozz]:
> > Arabic language has more than 1000 stopword.
>
> Keep in mind that WordPress should use the shortest list of stopwords
possible. The default English stopwords are approximately what the search
engines use, however there is a much longer list used in
[http://dev.mysql.com/doc/refman/5.1/en/fulltext-stopwords.html MySQL] for
full-text queries which is not suitable.
OK..
So is there any real reason about why `wp_search_stopwords` filter is
cached?
--
Ticket URL: <http://core.trac.wordpress.org/ticket/25587#comment:4>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list