[wp-meta] [Making WordPress.org] #4322: Invalid length search inputs should be handled more cleanly

Making WordPress.org noreply at wordpress.org
Tue Feb 11 05:09:25 UTC 2020


#4322: Invalid length search inputs should be handled more cleanly
----------------------------+---------------------
 Reporter:  jonoaldersonwp  |       Owner:  (none)
     Type:  defect          |      Status:  new
 Priority:  lowest          |   Milestone:
Component:  General         |  Resolution:
 Keywords:  seo analytics   |
----------------------------+---------------------

Comment (by dd32):

 Replying to [comment:1 Otto42]:
 > For reference, the exact breakage point seems to be at 1600 characters.
 I suspect this to be a limit in the underlying search engine.

 After a lot of digging around, I found the culprit - WordPress.

 [https://core.trac.wordpress.org/changeset/25632/trunk/src/wp-
 includes/query.php r25632] added an upper bound of 1600 characters for
 search requests, just ignoring it after that.

 The plugin directory actually limits it to 200char for searching purposes,
 but it's discarded by core prior to that point.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4322#comment:3>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org


More information about the wp-meta mailing list