[wp-trac] [WordPress Trac] #44457: Rename `upgrade_php` capability to `update_php`
WordPress Trac
noreply at wordpress.org
Mon Jun 25 15:24:52 UTC 2018
#44457: Rename `upgrade_php` capability to `update_php`
-----------------------------+------------------------------------
Reporter: flixos90 | Owner: (none)
Type: defect (bug) | Status: new
Priority: normal | Milestone: 5.0
Component: Role/Capability | Version: trunk
Severity: normal | Keywords: needs-patch servehappy
Focuses: |
-----------------------------+------------------------------------
In today's PHP meeting, we decided to use the term "update" instead of
"upgrade" throughout. This is in line with how WordPress has commonly used
only "update", with "upgrade" only appearing sometimes internally in the
code.
Similar capabilities are called `update_core`, `update_plugins` etc., so
our capability should be in line with this too. While we initially
considered "upgrade" a more fitting term for PHP, eventually consistency
makes sense here, and users are more familiar already with the term
"update".
This is a follow-up to #41191. Since the capability has not been part of
any WordPress release and has not been used outside of its single use-
case, we can easily rename it without backward-compatibility implications.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/44457>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list