[wp-trac] [WordPress Trac] #22942: Deprecate Post by Email

[WordPress Trac]

#22942: Deprecate Post by Email
-------------------------------------------------+-------------------------
 Reporter:  ericmann                             |       Owner:
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  Awaiting
Component:  Blog by Email                        |  Review
 Severity:  normal                               |     Version:  3.5
 Keywords:  dev-feedback 2nd-opinion has-patch   |  Resolution:
  needs-testing                                  |
-------------------------------------------------+-------------------------
Changes (by ericmann):

 * keywords:  dev-feedback 2nd-opinion => dev-feedback 2nd-opinion has-patch
     needs-testing


Comment:

 This first pass at a patch follows the same logic we used when
 deprecating/removing the Link Manager for 3.5:

 * Default options for Post by Email configuration are no longer added to
 the DB on install
 * New installs have `post_by_email_enabled` set to 0 (disabled)
 * Old installs that are still using the default values (i.e.
 mail.example.com for mail server) will have the `post_by_email_enabled`
 option set to 0 upon upgrade
 * Installations actually using the settings will have
 `post_by_email_enabled` set to 1
 * The table on `options-writing.php` that presents the Post by Email
 settings is hidden if `post_by_email_enabled` is set to 0

 This doesn't actually remove the option to post by email from core, but it
 hides it from new installs.  Hopefully, this first step will encourage
 more well-written plugins that enable post-by-email functionality to show
 up in the community.  We already have Jetpack, but quite a few people have
 voiced concern to that being the only player.

 Hiding the feature in such a way will:

 1. Encourage more plugin contributions
 1. Not have a negative impact on those currently using the feature
 1. Allow stubborn users/developers to easily turn things back on by
 changing 1 option in the DB, or by even adding a filter

 The next step will, hopefully, be to actually remove the code for the
 feature in 3.7 or 3.8. But this should be a solid step forward for 3.6.

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