Page MenuHomePhabricator

Allow a user to be blocked from purge pages only
Closed, DeclinedPublicFeature


Feature summary (what you would like to be able to do and where):
A new block option is added to the block form to prevent the user from sending purge requests.

Use case(s) (list the steps that you performed to discover that problem, and describe the actual underlying problem which you want to solve. Do not describe only a solution):
There is a robot on my wiki which does nothing but send purge requests after registration. The only way to deal with this now is to block the user completely, but in some cases it is extreme.

Benefits (why should this be implemented?):

Since T280226 no longer allows the user to continue purge pages after blocked, we may be able to do this in parts of the block.

Event Timeline

Xaosflux added a subscriber: Xaosflux.

If the only thing a user is doing is violating your project's policies, they probably should be site blocked. That being said I don't have any special objection to this, but think it is very niche and should only be implemented if being done as part of a master action-that-can-be-blocked type list and not as a distinct option unless a much better reason for it can be put forward.

I don't think this is really feasible. You can trigger "purges" from residual actions, like editing a template or flipping a category from visible to hidden or vice versa.

Boldly declining per last comments.