[wp-trac] [WordPress Trac] #11589: Disable the availability of deprecated functions by default for new installs

[WordPress Trac]

#11589: Disable the availability of deprecated functions by default for new
installs
-----------------------------+----------------------------------------------
 Reporter:  westi            |       Owner:  westi
     Type:  feature request  |      Status:  new  
 Priority:  normal           |   Milestone:  3.0  
Component:  General          |     Version:  3.0  
 Severity:  normal           |    Keywords:       
-----------------------------+----------------------------------------------

Comment(by filosofo):

 Replying to [comment:7 westi]:
 > For existing installs the functions are always going to be available.
 >
 > '''This change would only affect new installs.'''

 I've read the ticket and looked at the patch, and I don't understand how
 the following wouldn't happen:
  * Joe newly installs WordPress with version 3.0.  Hence
 WP_ENABLE_DEPRECATED_FUNCTIONS is true in Joe's wp-config.php file.
  * For 3.1, we deprecate function x.
  * Joe upgrades to 3.1.  Bam!  x is gone---not just deprecated---
 undefined, breaking his site with fatal errors from plugins calling x.

 Instead, why not
  * Do a better job marking the version in which a function was deprecated
 (currently many just say "0.0").
  * At every major release, delete all functions deprecated 3 major
 versions ago.
  * Perhaps for functions one release away from being removed, throw an
 error in admin even if WP_DEBUG isn't set.

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