Problem/Motivation

It is not necessary to have confirmation forms for disabling/enabling user restrictions. The Search module, for example, uses a controller for its Search page entities.

Proposed resolution

  • Remove the RestrictionDisableForm and the RestrictionEnableForm classes
  • Remove any reference to those classes from handlers.form
  • Leave the links for disable and enable in links
  • Add a controller for the enable and disable operations

Issue fork user_restrictions-3553385

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

avpaderno created an issue. See original summary.

avpaderno opened merge request !82

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Status: Active » Needs review
avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Issue summary: View changes

  • avpaderno committed db63c698 on 3.0.x 
    Issue #3553385: Remove the RestrictionEnableForm and the...
avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Version: 3.0.x-dev » 2.1.x-dev
avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Issue summary: View changes

avpaderno opened merge request !83

  • avpaderno committed cbe2f7f3 on 2.1.x 
    Issue #3553385: Remove the RestrictionEnableForm and the...
avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Status: Needs review » Fixed

Now that this issue is closed, please review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, please credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.