[wp-trac] [WordPress Trac] #47678: Modernize/simplify current_user_can()
WordPress Trac
noreply at wordpress.org
Tue Jul 16 00:21:47 UTC 2019
#47678: Modernize/simplify current_user_can()
-------------------------------------+-------------------------------------
Reporter: jrf | Owner: pento
Type: enhancement | Status: assigned
Priority: normal | Milestone: 5.3
Component: Role/Capability | Version: trunk
Severity: normal | Resolution:
Keywords: has-patch has-unit- | Focuses: performance, coding-
tests commit needs-dev-note | standards
-------------------------------------+-------------------------------------
Changes (by peterwilsoncc):
* keywords: has-patch has-unit-tests commit => has-patch has-unit-tests
commit needs-dev-note
Comment:
Replying to [comment:28 jrf]:
> Of course, this excludes the commercial plugins and themes, as well as
private plugins and themes, but all the same, I do think it's safe to
assume that the numbers will be roughly the same, which means that less
than **0.05%** of plugins and themes will run into this issue.
>
> So, while I appreciate that we should be very careful about this, I
think that we may be overestimating the impact a bit.
Agreed, the common use case is for `*_lvl()` and `*_el()` modifications.
@pento's suggestion of a dev-note ought to be adequate.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/47678#comment:29>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list