Replaced Deprecated Actions Module

Created on 5 July 2024, 7 months ago

Problem/Motivation

Actions UI is now a deprecated module and it is recommended to use the contributed module instead: https://www.drupal.org/node/3223395#s-actions-ui β†’

But I can't uninstall from the site because change_author_action has it as a dependency.

Steps to reproduce

Drupal 10.3.1

Check the status report and see a note about the deprecated module.

Proposed resolution

Change the dependency in the info.yml to use action:action instead of drupal:action.

Add a requirement in the composer.json to require drupal/action be installed.

πŸ› Bug report
Status

Active

Version

1.1

Component

Code

Created by

πŸ‡¨πŸ‡¦Canada ryanrobinson_wlu

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

  • Issue created by @ryanrobinson_wlu
  • πŸ‡ΊπŸ‡ΈUnited States rraney

    Following. I have the same issue.

  • First commit to issue fork.
  • Merge request !3Replaced Deprecated Actions Module β†’ (Open) created by oldeb
  • πŸ‡§πŸ‡ͺBelgium oldeb Namur πŸ‡§πŸ‡ͺ
  • πŸ‡§πŸ‡ͺBelgium oldeb Namur πŸ‡§πŸ‡ͺ

    Made the quick change, looks like everything is working as intended after a cache clear.

    Warning : this change break the compatibility with Drupal versions 10.2 and below !

  • πŸ‡¨πŸ‡­Switzerland berdir Switzerland

    Does it? Earlier versions of core have a replace statement for this.

    I recommend not using an open ended version compatibility. This can't be undone, this version will forever claim to be compatible with any core version.

  • πŸ‡§πŸ‡ͺBelgium oldeb Namur πŸ‡§πŸ‡ͺ

    Does it? Earlier versions of core have a replace statement for this.

    Yes because the module now require the contrib Action module which is not compatible with Drupal 10.2 and below.

    I recommend not using an open ended version compatibility. This can't be undone, this version will forever claim to be compatible with any core version.

    Your are right, I changed the version requirements.

  • πŸ‡¨πŸ‡­Switzerland berdir Switzerland

    > Yes because the module now require the contrib Action module which is not compatible with Drupal 10.2 and below.

    There are two things here.

    The .info.yml notation of "project:module". The project part at runtime is completely ignored. "drupal:action" and "action:action" for Drupal is really just "action". You could write "foobar:action" and Drupal is still happy. Modules don't actually have a project group/namespace. The prefix is just for drupal.org to translate it into composer dependencies.

    The other thing is the composer requirement. I was wrong on that. drupal/core used to have replace statements for all modules it provides, but that was reduced to just components in Drupal 9, see composer.json in 8.9.x: https://git.drupalcode.org/project/drupal/-/blob/8.9.x/core/composer.jso....

    Technically you could add your own replace section to your project composer.json, but since 10.1 and older are long EOL anyway, I agree it's easier to just require 10.2 and move on.

    I don't think it's a BC break though (don't think that's a valid issue tag either way), updating required versions of dependencies is allowed in a minor update.

Production build 0.71.5 2024