Problem/Motivation

Track the steps needed to remove extension Action from core to contrib. See Remove a core module and move it to a contributed project of the deprecation policy.

The removal of extension Action was approved in #3266458: [Policy] Deprecate Action (UI) module in D10 and move to contrib in D11.

Remaining tasks

  1. Begin finding someone to maintain the contrib version of the extension. (andypost)
  2. Move integrations implemented by other modules to the extension.
    Create child issues or child meta issues, as needed, to address the following points. Not all points will apply to all extensions.
  3. #3413949: Move some Action plugins to Action module
  4. Do a thorough search of core for any remaining references to the extension. If references are found, outside of the extension, then create issues to remove the references.
  5. Create the contrib project with a stable release. #3344683: Unreserve or create "action" module in contrib
  6. Deprecate the core extension. Use the Issue Summary template or core extension deprecation. #3369912: Final steps to deprecate Actions UI (action) module
  7. Release 1.0 in contrib and proceed to #3427413: Stop using action in user module in role entity hooks

Completed tasks

Comments

quietone created an issue. See original summary.

quietone’s picture

Issue summary: View changes

There are no migrations to move, this was already done in #3067299: Move actions migrations and tests to system module.

quietone’s picture

Issue summary: View changes

I did not find action module in any profile.

andypost’s picture

andypost’s picture

Removing references to the extension from database dumps.

Looks that's the only task from summary left

andypost’s picture

There's only one usage in drupal-9.4.0.filled.standard.php.gz (core.extension) and later in routing

'data' => 'a:3:{s:6:"module";a:60:{s:6:"action";i:0;s:14:"automated_cron";i:0;s:3:"ban";i:0;s:10:"basic_auth";i:0;s:5:"block";i:0;s:13:"block_content";i:0;s:4:"book";i:0;s:10:"breakpoint";i:0;s:9:"ckeditor5";i:0;s:7:"comment";i:0;s:6:"config";i:0;s:18:"config_translation";i:0;s:7:"contact";i:0;s:19:"content_translation";i:0;s:10:"contextual";i:0;s:8:"datetime";i:0;s:5:"dblog";i:0;s:6:"editor";i:0;s:5:"field";i:0;s:8:"field_ui";i:0;s:4:"file";i:0;s:6:"filter";i:0;s:4:"help";i:0;s:7:"history";i:0;s:5:"image";i:0;s:8:"language";i:0;s:4:"link";i:0;s:6:"locale";i:0;s:7:"menu_ui";i:0;s:7:"migrate";i:0;s:14:"migrate_drupal";i:0;s:5:"mysql";i:0;s:4:"node";i:0;s:7:"options";i:0;s:10:"page_cache";i:0;s:4:"path";i:0;s:10:"path_alias";i:0;s:5:"pgsql";i:0;s:16:"responsive_image";i:0;s:4:"rest";i:0;s:6:"search";i:0;s:13:"serialization";i:0;s:8:"shortcut";i:0;s:6:"sqlite";i:0;s:10:"statistics";i:0;s:6:"syslog";i:0;s:6:"system";i:0;s:8:"taxonomy";i:0;s:9:"telephone";i:0;s:4:"text";i:0;s:7:"toolbar";i:0;s:4:"tour";i:0;s:7:"tracker";i:0;s:6:"update";i:0;s:4:"user";i:0;s:8:"views_ui";i:0;s:5:"forum";i:1;s:17:"menu_link_content";i:1;s:5:"views";i:10;s:8:"standard";i:1000;}s:5:"theme";a:3:{s:5:"stark";i:0;s:5:"claro";i:0;s:7:"olivero";i:0;}s:7:"profile";s:8:"standard";}',
dww’s picture

Whoops, a bit late to the game. Wish I saw all this in time to have posted this to #3266458: [Policy] Deprecate Action (UI) module in D10 and move to contrib in D11, but that's already done and decided...

While I mostly agree that the "Actions UI" module is confusing and not terribly helpful on its own, #2797583: Dynamically provide action plugins for every moderation state change is categorized as a "Major feature", followed by 152 (which is very high for most core issues). Perhaps that issue can be changed so that you don't have to enable the Action UI to create individual actions for the content_moderation transitions you want, and it would instead dynamically provide actions for everything automatically. But that'd introduce its own UI problems, since then everywhere you get a list of actions, you might have dozens of new actions you have to hide that don't make sense, etc. It's clunky, but having to manually create the actions you actually need (instead of getting everything automatically) is kinda helpful.

Anyway, would love to hear thoughts on how to handle (much needed) functionality like that issue, if we have no more Actions UI in core.

Thanks/sorry!
-Derek

andypost’s picture

As I see we have no contribution to actions at all because of this incomplete transition to contrib

To unblock we should deprecate it or unblock issues

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

quietone’s picture

Issue summary: View changes
quietone’s picture

Issue summary: View changes
quietone’s picture

Issue summary: View changes
quietone’s picture

Issue summary: View changes

Found tests that are not in the action module that are installing the action.

andypost’s picture

curious about tests as node/comment actions require actions UI to be configured

which means we can not do functional testing without it

- https://git.drupalcode.org/project/drupal/-/blob/11.x/core/modules/node/...
- https://git.drupalcode.org/project/drupal/-/blob/11.x/core/modules/comme...

quietone’s picture

Can you point to a specific test? My searching does not find any other test that installs the Action module. The comment tests look like they use actions but not the UI provided by the Action module.

andypost’s picture

Added links to #14 - both plugins require ui to configure keywords

catch’s picture

CommentActionsTest directly updates the plugin configuration to test the keywords functionality, so I think the plugin and tests will continue to work if we move action module to contrib.

However, I'm not sure those two plugins make sense without a UI, so maybe we should also consider an issue to move them into the actions_ui module?

andypost’s picture

Not sure it makes sense to deprecate them, because there's goto,message,email actions in core https://git.drupalcode.org/project/drupal/-/tree/11.x/core/lib/Drupal/Co...

wim leers’s picture

wim leers’s picture

Title: [meta] Tasks to deprecate Action module » [meta] Tasks to deprecate Actions UI module

Oh and per #3266458-11: [Policy] Deprecate Action (UI) module in D10 and move to contrib in D11, I think this issue is a bit misleading — is this tweak accurate? 😅

quietone’s picture

Issue summary: View changes
catch’s picture

andypost’s picture

Issue summary: View changes

Last blocker is RTBC #3413949: Move some Action plugins to Action module

Now it needs infra team to create project and then I can split 1.x branch in #3344683: Unreserve or create "action" module in contrib

andypost’s picture

Issue summary: View changes
andypost’s picture

andypost’s picture

catch’s picture

The project page could use an update: https://www.drupal.org/project/action, it's currently using the template.

andypost’s picture

Status: Active » Reviewed & tested by the community

I did update of project page, looks we can mark it fixed

catch’s picture

Status: Reviewed & tested by the community » Fixed

Yep ready to go now I think!

andypost’s picture

Status: Fixed » Closed (fixed)

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

quietone’s picture

Version: 11.x-dev » 10.3.x-dev