A lot of extensions use User::isBlocked() to see if a user should be granted access to the extension. This should check the block on a permission-level to ensure that the user does in fact have access. The block can pass (return null) if it does not make an explicit decision either way.
Description
Description
Details
Details
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Open | None | T208749 👩👧👦 Update Extensions to properly handle Partial Blocks | |||
Resolved | Melos | T208512 CheckUser tool is inaccessible while partial-blocked | |||
Resolved | Daimona | T208621 AbuseFilter Log and Edit/Create is inaccessible while partially blocked | |||
Resolved | Tchanders | T208961 FlaggedRevs uses User::isBlocked() in its API endpoints to determine if user has access | |||
Declined | dbarratt | T208563 Update User::isAllowed() to check the user's block with Block::prevents() | |||
Resolved | dmaza | T203821 After QA, enable Partial Blocks MVP on test.wikipedia.org and test.wikidata.org |
Event Timeline
Comment Actions
Change 471210 had a related patch set uploaded (by Dbarratt; owner: Dbarratt):
[mediawiki/core@master] Update User::getRights() to also check that a block is sitewide
Comment Actions
Change 471210 abandoned by Dbarratt:
Update User::isAllowed() to also check that a block does not prevent the user's actions.
Reason:
After a lot of discussion, we are abandoning this patch and defering how to deal with blocks to the extensions themselves.
Comment Actions
After much discussion, we've decided that it is best to let extensions deal with partial blocks themselves.