Plugin info

Total downloads: 7,032
Active installs: 2,000
Total reviews: 1
Average rating: 5
Support threads opened: 0
Support threads resolved: 0 (0%)
Available in: 1 language(s)
Contributors: 3
Last updated: 5/5/2016 (3527 days ago)
Added to WordPress: 5/5/2016 (9 years old)
Minimum WordPress version: 4.0
Tested up to WordPress version: 4.5.33
Minimum PHP version: f

Maintenance & Compatibility

Maintenance score

Possibly abandoned • Last updated 3527 days ago • 1 reviews

22/100

Is Disable WordPress Core Update Email abandoned?

Possibly abandoned (last update 3527 days ago).

Compatibility

Requires WordPress: 4.0
Tested up to: 4.5.33
Requires PHP: f

Similar & Alternatives

Explore plugins with similar tags, and compare key metrics like downloads, ratings, updates, support, and WP/PHP compatibility.

Disable Updates for WordPress Core, Plugins and Themes
Rating 4.8/5 (4 reviews)Active installs 10,000
Disable All Update Notifications
Rating 0.0/5 (0 reviews)Active installs 60
Custom WP Update Message
Rating 0.0/5 (0 reviews)Active installs 20
Remove Update Notification
Rating 0.0/5 (0 reviews)Active installs 10

Description

Disables the default notification email sent by WordPress for an automatic core update. Simply activate the plugin to disable the notification email 🙂

Installation

This section describes how to install the plugin and get it working.

  1. Upload disable-wordpress-core-update-email directory to the /wp-content/plugins/ directory
  2. Activate the plugin through the ‘Plugins’ menu in WordPress
  3. Go to the Facebook Comments settings

Frequently Asked Questions

No FAQ available

Review feed

KZeni
1/7/2021

Does exactly what it says it does (even 5 years since last update)

The simplicity of the plugin helps it be lightweight & easy to use. That also means the one line of active PHP code that it consists of (it then being what WordPress recommends in its current documentation per https://wordpress.org/support/article/configuring-automatic-background-updates/#disable-emails-via-filter) is likely to continue to work exactly as expected unless WordPress were to completely overhaul its setup regarding this (with there appearing to be no plans for this.) Especially considering it's using a filter so it's even more flexible if things were to change in the future (won't outright break things due to a code error beyond WordPress doing a fundamental change to a core function like add_filter or __return_false & that'd then break the majority of plugins & themes out there [they'd need a good reason for doing so & it appears they obviously have no plans for doing that either.])

Screenshots

No screenshots available

Changelog

1.0

  • Initial release.