Paul Biron

> I guess it would make it more explicit. I figured that was your thinking. I'm not against the idea, that was just my initial thought upon reading the issue...

> Are there any other places in core where we have these more explicit actions? One came to mind, although it's not quite the same. It has to do with...

> Interesting find. As in the ancient curse: `May you live in interesting times` :-) > I think part of the reasoning for that is because of the `show_admin_bar()` function...

For context, see https://github.com/audrasjb/wp-autoupdates/pull/10#issuecomment-598827167 (my comment on a PR in the old repo for this feature plugin...that didn't get migrated over to this repo).

and "It's fine just the way it is, we don't need to change it" is a perfectly reasonable response :-)

> I actually am a designer :) Thanx for the feedback > * img 1: The alternating green/blue borders just add noise/clutter. They don't make it clear what means what....

I like that, it's subtle but not too subtle. If/when that gets accepted for Gutenberg it is definitely worth considering for this.

> Also, as far as I see the `auto_update_plugin` overrides both `WP_DISABLE_PLUGINS_AUTO_UPDATE` and `wp_plugins_auto_update_enabled` making the UI "wrong". Same for `auto_update_theme`. I'll answer this one first, as I think doing...

I should note that I have not tested (not sure if others have) the case where the Updates API returns a `true` value in the `autoupdate` field of it's response...

> Sorry, should have explained that better :) > > With the plugin enabled, add `add_filter( 'auto_update_plugin', '__return_true', 11 );` to another plugin (this can also be set for individual...