[wp-trac] [WordPress Trac] #11541: Remove all IM fields from core.

WordPress Trac noreply at wordpress.org
Sun Dec 16 08:33:53 UTC 2012


#11541: Remove all IM fields from core.
-------------------------+-----------------------
 Reporter:  ShaneF       |       Owner:  ShaneF
     Type:  enhancement  |      Status:  accepted
 Priority:  normal       |   Milestone:  3.6
Component:  Users        |     Version:  2.9
 Severity:  normal       |  Resolution:
 Keywords:  needs-patch  |
-------------------------+-----------------------
Changes (by nacin):

 * keywords:  has-patch dev-feedback => needs-patch
 * milestone:  Future Release => 3.6


Comment:

 A few years ago, I would argue it was fairly rare to put stuff in the
 options (or sitemeta) tables for the purposes of hiding or disabling
 something (or a general behavior shift) for new installs. This is
 partially why I've avoided pushing this until now.

 But, we've shown we haven't been afraid to put stuff in options/sitemeta.
 3.5 gave us ms_files_rewriting and link_manager_enabled, and flipped the
 default multisite setting for upload checks to no default limit.

 We've done this before, however fleeting. 3.0 gave us
 global_terms_enabled. 2.6 gave us enable_xmlrpc and enable_app. In 3.3, we
 added initial_db_version but didn't use it; that's because for pointers we
 decided to go with the user-specific dismissed_wp_pointers (which is
 created for all new users).

 I think it is time to shut these off for new installs. New option:
 legacy_contact_methods = 0. We can even shut them off for old installs
 that don't use them, by checking if this query returns anything:

 `SELECT meta_key FROM $wpdb->usermeta WHERE meta_key IN ('yim', 'jabber',
 'aim') AND meta_value <> '' LIMIT 1`

 Some notes on implementation:
  * We should avoid doing this when DO_NOT_UPGRADE_GLOBAL_TABLES is set,
 because that will signify this may be run on a huge usermeta table.
  * It should be run only on the main site, as usermeta is of course a
 global table in multisite.
  * As it is global, it should be stored globally, so get_site_option().

 It probably took me longer to write this comment than it would be to code
 it.

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


More information about the wp-trac mailing list