[wp-trac] [WordPress Trac] #9864: Performance issues with large number of pages

WordPress Trac noreply at wordpress.org
Sun Oct 29 06:34:07 UTC 2017


#9864: Performance issues with large number of pages
--------------------------------+------------------------------------------
 Reporter:  pp19dd              |       Owner:
     Type:  defect (bug)        |      Status:  assigned
 Priority:  normal              |   Milestone:  Future Release
Component:  Posts, Post Types   |     Version:  2.7.1
 Severity:  normal              |  Resolution:
 Keywords:  2nd-opinion has-    |     Focuses:  performance, administration
  patch                         |
--------------------------------+------------------------------------------

Comment (by Takahashi_Fumiki):

 I have 3 questions before making patches.

 == UI enhancement ==

 WordPress uses select element to  "select parent" UI. But it may raises
 performance issue if target option elements increase.

 * Parent page(also, hierarchical post types)
 * Parent term(also, hierarchical taxonomies)

 SQL optimization doesn't solve these, because parent candidates keep
 increasing.

 So I recommend incremental select, but is it beyond scope of this ticket?

 == Library to use ==

 I think we should choose some library to Candidates.

 * Select2
 * SelectWoo
 * jQuery UI autocomplete

 I prefer select2 https://github.com/select2/select2 but core team tried to
 include and nothing updated https://github.com/select2/select2/issues/3744
 WooCommerce team made SelectWoo and I think this might be good
 https://github.com/woocommerce/selectwoo
 jQuery UI autocomplete is included in core but not similar to original
 select element.

 What should we choose?

 == Resulting UI ==

 Current select element displays option hierarchically, but select2 or
 something like autocomplete don't display "non-match parent.
 Considering its purpose of autocomplete UI, non-matching elements should
 be displayed, but someone may think its worse UX than before.

 Should we show non-match parent elements?

 Thanks in advance.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/9864#comment:49>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform


More information about the wp-trac mailing list