[wp-trac] [WordPress Trac] #17164: More elegant handling of site 'archive' options for MultiSite

[WordPress Trac]

#17164: More elegant handling of site 'archive' options for MultiSite
-------------------------------------+-------------------------------------
 Reporter:  Ipstenu                  |       Owner:
     Type:  enhancement              |      Status:  new
 Priority:  normal                   |   Milestone:  Future Release
Component:  Networks and Sites       |     Version:  3.1
 Severity:  normal                   |  Resolution:
 Keywords:  ux-feedback needs-patch  |     Focuses:  administration,
  ui-feedback                        |  multisite
-------------------------------------+-------------------------------------

Comment (by johnjamesjacoby):

 In my opinion, also related are #36492, #12706.

 Specifically, my comment here:
 https://core.trac.wordpress.org/ticket/12706#comment:211

 ----

 For this ticket specifically, should be update the verbiage? Probably,
 yes. Though it'll be difficult to change their functionalities because of
 how deeply these are integrated into WordPress.com, Jetpack, and other
 open multisite networks.

 ----

 For WordPress in general, deeper scrutiny should be considered. These
 links currently map to several unique columns in the `wp_blogs` global
 database table:

 `public`, `archived`, `mature`, `spam`, `deleted`

 My preference would be to consolidate these columns down to 1 `status`
 column, with an API to help define what those statuses are and what they
 mean within the system.

 Then these row-action links can be driven by their defined statuses rather
 than the literal database schema. The added cardinality of an indexed,
 string-based `status` column should improve query performance over the
 multiple numerical columns, too.

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