Paul Biron

Such a feature is certainly "up for discussion", but the result of that discussion is likely to be that it is "plugin territory" (i.e., not something that is likely to...

> I am representing Easy Updates Manager with these questions: Thanx for the questions. > 1. Since the merge proposal has already been submitted and a ticket created, how reliable...

With regard to buttons vs links, I don't know if the same reasoning should apply here (tho I suspect it would), but prior to 5.4 the Privacy tools (which are...

@audrasjb I just did some checking and if using `` would be better for a11y (which is what the Privacy tools mentioned above use) we can switch to that with...

I'll add separate comments below for the constants and hooks that control various aspects of functionality.

~~These are the constants used by this plugin that are not already in core:~~ * ~~WP_DISABLE_PLUGINS_AUTO_UPDATE~~ * ~~WP_DISABLE_THEMES_AUTO_UPDATE~~ * ~~WP_DISABLE_PLUGINS_AUTO_UPDATE_EMAIL~~ * ~~WP_DISABLE_THEMES_AUTO_UPDATE_EMAIL~~ ~~Like the existing `AUTOMATIC_UPDATER_DISABLED` constant, the merge proposal...

These are the filters defined by this plugin (and will be part of the merge proposal): * wp_plugins_auto_update_enabled * wp_themes_auto_update_enabled * wp_autoupdates_notifications_email * send_plugins_auto_update_email * send_themes_auto_update_email All have complete DocBlocks...

No new constants and no additional filters, but - wp_plugins_auto_update_enabled - wp_themes_auto_update_enabled still exist. e.g. `add_filter( 'wp_plugins_auto_update_enabled', '__return_false' )` will disable the UI on the plugins screen.

Thanx for the reminder. As part of the core merge, those filters were renamed to: - `plugins_auto_update_enabled` - `themes_auto_update_enabled` they still have the same names in the latest version of...

Especially in the context Jonathan is talking about, using wording like Sé suggests is better than "CMS" (because those who don't know what WP is probably won't know know what...