WordPress.org

Make WordPress Core

Opened 5 weeks ago

Last modified 29 hours ago

#50907 new enhancement

Add a method to opt-in to core auto-updates.

Reported by: whyisjake Owned by:
Milestone: 5.6 Priority: normal
Severity: normal Version: 5.5
Component: Upgrade/Install Keywords: early needs-patch needs-docs needs-unit-tests needs-design
Focuses: Cc:

Description

With WordPress 5.5 gaining support for auto-updates, let add a new feature for users to opt-in to auto-updates for WordPress core.

Attachments (4)

first-exploration-enable-auto-updates.png (87.8 KB) - added by audrasjb 5 weeks ago.
First exploration: Enable auto-updates
first-exploration-disable-auto-updates.png (86.2 KB) - added by audrasjb 5 weeks ago.
First exploration: Disable (previously enabled auto-updates
Auto-update-WP-core.jpg (212.6 KB) - added by paaljoachim 2 weeks ago.
Enable auto updates for WordPress
Enable-auto-updates-of-WordPress.jpg (536.9 KB) - added by paaljoachim 2 weeks ago.
An adjustment.

Download all attachments as: .zip

Change History (23)

#1 @pbiron
5 weeks ago

  • Keywords needs-design added

This ticket was mentioned in Slack in #core by sergey. View the logs.


5 weeks ago

@audrasjb
5 weeks ago

First exploration: Enable auto-updates

@audrasjb
5 weeks ago

First exploration: Disable (previously enabled auto-updates

#3 @audrasjb
5 weeks ago

Above is a first exploration for the main UI.
I think it should takes place on the Update screen.

I used a real button as it is more consistent on this screen, but it's not super consistent with the plugins/themes screen’s auto-updates action link. Not sure it's an issue.

#4 @whyisjake
4 weeks ago

I think the language here needs to be a lot simpler. Something like "Keep WordPress up to date automatically."

Major/Minor/Core are dev terms. As a user, I just want WordPress to stop asking me about updates.

This ticket was mentioned in Slack in #core by whyisjake. View the logs.


4 weeks ago

#6 @jnylen0
4 weeks ago

Something like "Keep WordPress up to date automatically."

I'd advise caution here: this language implies that WP is not already kept up to date, which it is (at least concerning security issues and bugfixes in patch versions).

#7 follow-up: @JoshuaWold
3 weeks ago

Right now WordPress auto-updates security releases. Just to clarify then, is this issue about opt-in for ALL WordPress releases on my site?

This ticket was mentioned in Slack in #core-auto-updates by pbiron. View the logs.


2 weeks ago

#9 in reply to: ↑ 7 @pbiron
2 weeks ago

Replying to JoshuaWold:

Right now WordPress auto-updates security releases. Just to clarify then, is this issue about opt-in for ALL WordPress releases on my site?

Hey @JoshuaWold ... long time no talk :-)

Yes, this is about providing a UI for opting in to core MAJOR updates.

And just my personal opinion, but the UI should also all users to opt-out of core MINOR updates (which currently can be done via PHP constants and/or filters).

Last edited 2 weeks ago by pbiron (previous) (diff)

@paaljoachim
2 weeks ago

Enable auto updates for WordPress

#10 @pbiron
2 weeks ago

Here's a little history on this ticket:

  1. opt-in for core MAJOR updates was first proposed in https://make.wordpress.org/core/2018/12/08/9-priorities-for-2019/
  2. it obviously didn't make it in 2019, so it was carried over into the priorities for 2020 in https://make.wordpress.org/core/2019/12/06/update-9-projects-for-2019/

#11 @paaljoachim
2 weeks ago

In relation to the screenshot I just shared.

I looked at what we have today.
There are groupings for Plugins and below it Themes.
It would be natural to have a WordPress title in the top, and below it the info we see today, and then a button that just says "Enable auto updates for WordPress"
It should probably instead say
"Enable auto updates of WordPress".

The correct language based on the plugins screen would be:
"Enable auto-updates of WordPress".

As it is straight to the point. Pressing the button will automatically keep WordPress up to date. The minor releases are automatically updated. So this button will finally keep the major versions updated. We need to keep the language as simple as possible.

Last edited 2 weeks ago by paaljoachim (previous) (diff)

This ticket was mentioned in Slack in #core by hellofromtonya. View the logs.


2 weeks ago

#13 @hellofromTonya
2 weeks ago

  • Keywords early added

Moving this one to early to ensure it stays on our radar as it's part of scope for 5.6.

This ticket was mentioned in Slack in #core-auto-updates by pbiron. View the logs.


10 days ago

#15 @johnbillion
10 days ago

  • Version changed from trunk to 5.5

#16 @karmatosed
8 days ago

  • Keywords needs-design-feedback added; needs-design removed

This ticket was mentioned in Slack in #design by karmatosed. View the logs.


3 days ago

#18 @karmatosed
29 hours ago

I would caution against adding another button in this case. Why can't this be a checkbox or toggle option? It's an option right not an actionable button? I really think having 3 buttons of equal interaction hierarchy is a little confusing as far as the experience goes. As a result, I would love explorations that look at what other variations could be done here around not using secondary or primary buttons, seeing it more as an option.

#19 @karmatosed
29 hours ago

  • Keywords needs-design added; needs-design-feedback removed
Note: See TracTickets for help on using tickets.