Problem/Motivation

Currently, the value for the no_expiration form element is not stored as entity property, but it is used to change the value assigned to the expiration form element. Apparently, this does no longer work on Drupal 11.2.
It would also be helpful to keep the expiration value, so a restriction can be changed from with expiration to without expiration, and back to with expiration, without losing the entered expiration time.

Proposed resolution

  • Add a new no_expiration property to the configuration entity
  • Change the code to use that property

Issue fork user_restrictions-3552220

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 !56

avpaderno’s picture

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

  • avpaderno committed b8afe24e on 3.0.x 
    Issue #3552220: Add a property for the no_expiration form element
avpaderno’s picture

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

avpaderno opened merge request !57

  • avpaderno committed 84a0f3d7 on 2.1.x 
    Issue #3552220: Add a property for the no_expiration form element
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.