Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #42281, comment 1


Ignore:
Timestamp:
11/19/2017 09:43:12 AM (7 years ago)
Author:
Jyria
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #42281, comment 1

    initial v1  
    1414And yes, I agree there should be some improvement here:
    15151. At least present the user a list of the exact translation files which just became available, with the possibility to NOT install one or all of them (just like available plugins/themes update list)
    16 2. Even though codex says, that WP should not force anything onto your installation, without your consent by default ( i.e. "update plugins"-button, "update themes"-button), we should take into account that newly available translation files already ran through thorough review, and you already decided to run the corresponding plugin and/or WP core versions in your installation. Thus the admin of the current installation already gave their consent to these code versions (plugin, theme, core). And since translation files should be considered as "part" of the installed plugin/theme/core versions, translation updates should run atuomaticall, just like mnro core updates.
     162. Even though codex says, that WP should not force anything onto your installation, without your consent by default ( i.e. "update plugins"-button, "update themes"-button), we should take into account that newly available translation files already ran through thorough review, and you already decided to run the corresponding plugin and/or WP core versions in your installation. Thus the admin of the current installation already gave their consent to these code versions (plugin, theme, core). And since translation files should be considered as "part" of the installed plugin/theme/core versions, translation updates should run automatically, just like minor core updates.
    1717
    1818Best regards