[wp-trac] [WordPress Trac] #18453: Improve doing_it_wrong() and stop it from breaking WP

[WordPress Trac]

#18453: Improve doing_it_wrong() and stop it from breaking WP
-------------------------+-----------------------
 Reporter:  azaozz       |       Owner:  nacin
     Type:  enhancement  |      Status:  accepted
 Priority:  normal       |   Milestone:  3.3
Component:  General      |     Version:
 Severity:  normal       |  Resolution:
 Keywords:               |
-------------------------+-----------------------

Comment (by azaozz):

 Replying to [comment:22 westi]:
 > I don't see why we need to do this at all.

 This ticket was meant to enhance the "first time" experience for new or
 beginner developers starting to work with WordPress. We care a lot about
 first time user experience but kind of ignore the new plugin and theme
 authors.

 It was meant to prompt them to install a debugging plugin and not break
 the output in the process. By default most PHP installations show errors
 instead of logging them. This was meant to cover these cases.

 User case:

 - install LAMP, MAMP, WAMP, etc.
 - add WordPress, make an account, etc.
 - add a plugin that would trigger deprecated or doing_in_wrong.

 At this point if the warning triggers before 'init' the new developer will
 see our warning message followed by many "headers already sent...". If it
 triggers at 'init', WP will load but all ajax will be broken (as the
 warning message is printed before the expected ajax return).

 We chatted with @nacin late yesterday night and agreed that the current
 code is not the best way to handle this, but I still think we need to have
 something to cover the default PHP installs when outputting the deprecated
 and doing_it_wrong warnings.

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