WordPress.org

Make WordPress Core

Opened 6 months ago

Closed 2 months ago

#50404 closed enhancement (wontfix)

Provide language pack update information in auto-updates email notifications

Reported by: knutsp Owned by:
Milestone: Priority: normal
Severity: normal Version: 5.5
Component: Upgrade/Install Keywords: close 2nd-opinion
Focuses: Cc:

Description

When doing updates from update-core.php, or when using common auto-update plugins, I can see that also language packs get update, for which plugin/theme and for what language(s), on the page or in the email notification.

This reminds me of three things:

  1. That such updates actually happens (even if it's not an UI option to turn them off)
  2. Which plugins/themes that have got a text update. I sometimes take look at the changes, reviewing the quality, on site first, then at .org.
  3. Which languages I have installed. This important, because this list is quite well hidden. Sometimes I discover that unnecessary language packs are installed. (To remove them is another story/ticket.)

With auto-updates this information is gone, and will stay unseen, as long as one stops manually updating, which is the main point of this feature.

This not just a bit sad (nostalgia), but makes it harder to discover that sites gets bloated with packs for all plugins, all themes, for languages no longer in use or needed as option for users. They are so easy to get in, but hard to remove.

I see no harm in adding this, like "Advanced Automatic Updates" do today.

Change History (6)

#1 @desrosj
5 months ago

  • Keywords close 2nd-opinion added

I'm inclined to say that this is out of scope for the first iteration of the auto-update UI, and possibly even plugin territory.

There is currently no UI for a user to enable/disable language pack updates. They are applied automatically when present at the same time as an update to the plugin/theme that they belong to is performed, but I do not believe that language pack updates are automatically installed otherwise (unless a filter is used to enable this behavior).

While this could be helpful for some, I think for the majority of users will not need to know that the language packs updated with plugins and themes. It should just work (and it does with a very high success rate), and it's in the user's best interest that they are installed at the same time as plugin and theme updates.

If core did add support for this, I would say including this information in the emails should be off by default. It also introduces a new scenario where only language packs are updated.

I'll leave this open for more feedback, but I think a maybelater resolution is appropriate.

#2 follow-up: @johnbillion
5 months ago

In what situation does a user need to manually perform a language pack update?

#3 @desrosj
5 months ago

I did more testing and realized language packs were not auto-updating locally for me because my site was not passing the is_vcs_checkout() check. Language packs always auto-update when available.

Regardless, I still feel information about translation updates are out of scope for the first iteration, and not necessary for the large majority of users (it should just work).

#4 in reply to: ↑ 2 @knutsp
5 months ago

Replying to johnbillion:

In what situation does a user need to manually perform a language pack update?

There is a button on update-core.php when they are available, making it possible to just) update the language packs (all or none), without updating any plugin/theme/core.

Like when I'm waiting for some string updates for a certain plugin or theme, but don't want to update any software (now) just to get those new strings in immediately.

This is, however, unrelated to this ticket. This is about awareness of both installed languages and language packs, a possible loss of awareness that exist today. Something I don't want to loose, and making me want continue to update manually. And that somewhat undermines the goal of the auto-updates feature, for some.

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


2 months ago

#6 @pbiron
2 months ago

  • Milestone Awaiting Review deleted
  • Resolution set to wontfix
  • Status changed from new to closed

This ticket was discussed during the #core-auto-updates office hours today and the consensus was that including translation updates in the notification emails wouldn't provide a tangible benefit.

Note: See TracTickets for help on using tickets.