Problem/Motivation

Drupal 11.3 introduced a change requiring config constraints to use named arguments: https://www.drupal.org/node/3554746

This is especially important as it can lead to a fatal error if not updated.

Steps to reproduce

Inspect the configuration on Drupal 11.3 using the config inspector module, it should result in a crash or deprecation warning.

Proposed resolution

Use named arguments for the constraint

Remaining tasks

Provide MR

Issue fork sitewide_alert-3567470

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

codebymikey created an issue. See original summary.

codebymikey opened merge request !87

codebymikey’s picture

codebymikey commented
Issue summary: View changes
Status: Active » Needs review
Related issues: +#3522497: Passing an $options array to constraint constructors is deprecated, use named arguments instead

codebymikey changed the visibility of the branch 3567470-3.0.x-3567470-regex-constraint-should to hidden.

codebymikey changed the visibility of the branch 3567470-3.0.x-regex-constraint to hidden.

codebymikey’s picture

codebymikey commented

If applying the patch on 3.0.1, you also need the #3538596: Incorrect name for schema file patch to be applied beforehand.

  • codebymikey committed f0b45a55 on 3.1.x 
    fix: #3567470 Regex constraint should use named arguments
smustgrave’s picture

smustgrave commented
Status: Needs review » Fixed

Thanks!

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

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

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

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