Make WordPress Core

Opened 17 years ago

Closed 17 years ago

Last modified 17 years ago

#9137 closed enhancement (wontfix)

Option to disable email notifications about new users and password resets

Reported by: sirzooro's profile sirzooro Owned by:
Milestone: Priority: normal
Severity: normal Version:
Component: Administration Keywords: has-patch needs-testing
Focuses: Cc:

Description

When someone registers or resets password, an email notification is sent to admin. I have site where everyone can register, and I want to disable these emails sent to admin. Could you add option for this?

Attachments (2)

annoying_emails.diff (4.8 KB) - added by sirzooro 17 years ago.
admin_notifications.diff (6.4 KB) - added by sirzooro 17 years ago.

Download all attachments as: .zip

Change History (10)

#1 @FFEMTcJ
17 years ago

  • Milestone changed from 2.8 to Future Release

#2 @sirzooro
17 years ago

  • Milestone changed from Future Release to 2.7.2

#3 @DD32
17 years ago

  • Component changed from General to Administration
  • Keywords has-patch needs-testing added
  • Milestone changed from 2.7.2 to Future Release

New functionality does not go into bugfix releases.

Patch is not very professional with the choice of option name either

If a commiter feels like commiting it (It'll be on the list of items now that the keywords are set properly) then it'll be commited to 2.8, else, it'll end up in a Future Release if chosen to be implemented.

#4 @mrmist
17 years ago

-2 to the current patch because of the choice of variable name and option name.

If it were me developing the patch for this, I would try not to let my personal annoyances with what can be a useful facility get in the way of making a patch to disable such functionality.

I'd probably consider something like -

"Send notification of password resets to admin" and
"Send notification of new login creation to admin"

Make both options default to "yes" to mimick current functionality, and make them both seperate options, to increase the flexibility of the patch.

#5 @sirzooro
17 years ago

I was not sure how to implement this (add one or two new options), so I choose name which was funny (at least for me) in order to get quicker response :).

I changed my patch according to mrmist suggestions. New version is attached.

#6 @sirzooro
17 years ago

  • Milestone changed from Future Release to 2.8

#7 @ryan
17 years ago

  • Resolution set to wontfix
  • Status changed from new to closed

Those functions are pluggable for this very reason. Define new versions of the functions in a plugin.

#8 @ryan
17 years ago

  • Milestone 2.8 deleted
Note: See TracTickets for help on using tickets.