[wp-trac] [WordPress Trac] #34377: Another unexpected break in behavior for wp_new_user_notification()

[WordPress Trac]

#34377: Another unexpected break in behavior for wp_new_user_notification()
-----------------------------+----------------------
 Reporter:  danielbachhuber  |       Owner:  ocean90
     Type:  defect (bug)     |      Status:  closed
 Priority:  normal           |   Milestone:  4.3.2
Component:  Users            |     Version:
 Severity:  normal           |  Resolution:  fixed
 Keywords:  has-patch        |     Focuses:
-----------------------------+----------------------
Changes (by ocean90):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"35735"]:
 {{{
 #!CommitTicketReference repository="" revision="35735"
 Passwords: Support the pre-4.3 behavior of `wp_new_user_notification()`.

 Hello, it's me again. A pluggable function named
 `wp_new_user_notification()`. A few months ago, after [33023], I have lost
 my second parameter `$plaintext_pass`. But thanks to [33620] I got a new
 one.
 Bad idea - It hasn't had the same behavior as my previous parameter.
 To solve that the second parameter got deprecated and reintroduced as the
 third parameter in [34116]. I was happy again, for a short time.
 You remember my lost friend `$plaintext_pass`? No? Well, if its value was
 empty no notification was sent to the user. This behavior was still lost.
 And that's what this change is about: Don't notify a user if a plugin uses
 `wp_new_user_notification( $user_id )`.

 You're asking if I'm happy now? Dunno, but maybe you have learned
 something about pluggable functions, have you?

 Props danielbachhuber.
 Fixes #34377.
 }}}

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