[wp-trac] [WordPress Trac] #25709: Searches with stopwords can trigger E_WARNING when PCRE is lacking UTF-8 support

[WordPress Trac]

#25709: Searches with stopwords can trigger E_WARNING when PCRE is lacking UTF-8
support
--------------------------+--------------------
 Reporter:  nacin         |       Owner:
     Type:  defect (bug)  |      Status:  new
 Priority:  high          |   Milestone:  3.7.1
Component:  General       |     Version:  3.7
 Severity:  major         |  Resolution:
 Keywords:                |
--------------------------+--------------------

Comment (by dd32):

 >  Something smells funny.

 My gut feeling is that `/u` is simply used as a flag to tell PCRE to
 enable extra UTF8 support, if it's not compiled with UTF8, nothing
 happens, `.` continues to match partial UTf8 characters. However, this
 warning is triggered when a UTF8-specific character selector (such as
 \p{L}) is used but is unsupported.

 If that's correct, all the other cases are fine, but may not act as
 expected if there's no UTF8 support, it's just this one will also emit a
 PHP Warning.

--
Ticket URL: <http://core.trac.wordpress.org/ticket/25709#comment:3>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software