#16719 closed defect (bug) (fixed)
Remove vestige add_users capability
Reported by: | nacin | Owned by: | dd32 |
---|---|---|---|
Milestone: | 4.4 | Priority: | normal |
Severity: | normal | Version: | |
Component: | Role/Capability | Keywords: | has-patch commit |
Focuses: | Cc: |
Description
Listed in populate_roles_300() and added in [14174], it was never used. The situation it was presumably introduced for now falls on promote_users.
Attachments (4)
Change History (22)
#1
@
12 years ago
- Keywords has-patch added
- Milestone changed from Future Release to 3.5
Wondering whether we should go through the trouble of also removing it in an upgrade routine.
#2
@
12 years ago
Four plugins in the repo are using it. Should we yank the actual cap and then map it to promote_users? Either way, I'm thinking that the actual cap should be removed from any roles that have it.
#3
@
12 years ago
Either way, I'm thinking that the actual cap should be removed from any roles that have it.
Seems fine to me. We can use map_meta_cap to map it to promote_users. Opens us up to adding it in the future.
#6
@
10 years ago
- Keywords needs-patch good-first-bug added; 3.2-early has-patch removed
Needs patch that removes cap from users and map_meta_cap's the cap as described in comment:2
#7
@
9 years ago
- Keywords has-patch added; needs-patch removed
16719-1.patch removes add_users legacy cap and maps it to promote_users
#11
@
9 years ago
- Owner set to wonderboymusic
- Resolution set to fixed
- Status changed from new to closed
In 35507:
#12
@
9 years ago
- Resolution fixed deleted
- Status changed from closed to reopened
It seemed like 3 years ago, @markjaquith and I agreed:
Wondering whether we should go through the trouble of also removing it in an upgrade routine.
I'm thinking that the actual cap should be removed from any roles that have it.
An upgrade routine seems prudent. Please re-close if you disagree.
#13
@
9 years ago
- Owner changed from wonderboymusic to dd32
- Status changed from reopened to assigned
This ticket was mentioned in Slack in #core by wonderboymusic. View the logs.
9 years ago
#15
@
9 years ago
- Keywords good-first-bug removed
16179.diff introduces the migration routine suggested above.
#16
@
9 years ago
- Keywords commit added
Noting that I've reviewed the patch, and it looks good to me (assuming it works ;) )
#18
@
9 years ago
Not sure if this is the right place but it would be good to update the codex on this one:
https://codex.wordpress.org/Roles_and_Capabilities#add_users
Remove legacy hook as per proposed