Problem/Motivation

There are several changes in Drupal 11.3 that affect this module. I just opened the 1.1.x branch, and I would like to have a 1.1.0 release that removes code from the module that supports earlier versions of Drupal core.

The most significant change is that Drupal core now has a permission that does the same thing as the administer node status permission from this module: see the change record New permission available to control the Published status of Nodes.

Proposed resolution

  1. Change the core compatibility to ^11.3 || ^12.
  2. Remove the administer node status permission. Add an update function that replaces it with the core administer node published status permission.
  3. Remove the @group attribute from the PHPUnit test. (The corresponding attribute was added in #3601597: Automated Drupal 12 compatibility fixes for nodepermissions 1.0.x-dev.)
  4. Remove the .module file and the .services.yml file. (They implement one hook, calling the OO version.)

Remaining tasks

User interface changes

The "Administer node status field" permission will no longer appear on /admin/people/permissions/module/nodepermissions (nor on the main permissions form).

Before

Screenshot showing permissions, including 'Administer node status field'

API changes

None

Data model changes

None

CommentFileSizeAuthor
nodepermissions-with-status.png178.93 KBbenjifisher
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:

Comments

benjifisher created an issue. See original summary.

benjifisher’s picture

Issue summary: View changes
benjifisher’s picture

Version: 1.0.x-dev » 1.1.x-dev
benjifisher’s picture

Status: Active » Needs review

benjifisher’s picture

I used Claude code to write the update function and to do code cleanup. I reviewed all the changes it made.

benjifisher’s picture

Status: Needs review » Reviewed & tested by the community

benjifisher’s picture

Status: Reviewed & tested by the community » Fixed

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.