Active
Project:
Drupal core
Version:
main
Component:
base system
Priority:
Major
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
29 Sep 2014 at 16:04 UTC
Updated:
25 Jun 2023 at 03:01 UTC
Jump to comment: Most recent
For Rules being able to properly switch between context/configuration being passed on, action (and condition) plugins should not / may not apply data processing like token replacements on the data passed - that may only happen if the user has input a respective value and the configuration user has according permissions.
Add data processing API and allow conditions and actions to use it
-
-
Probably some additions to action and condition base classes / context aware plugins.
Comments
Comment #1
tim.plunkettIs this still major?
Comment #2
fagoYes, we'll need it for being able to be able to use core actions and consequently conditions in Rules. We are still stalled on #2011038: Use Context system for actions though :/
Comment #3
dawehnerComment #10
andypostComment #11
andypostComment #17
mxh commentedIs there any resource (issues, discussions, documentation, project...) about the mentioned data processing API?
Comment #19
andypostComment #20
andypost@mxh please check added related issues
Comment #21
mxh commentedThank you @andypost :)
Comment #24
quietone commentedAction module is approved for removal. See #3266458: [Policy] Deprecate Action (UI) module in D10 and move to contrib in D11
This is now Postponed. The status is set according to two policies. The Remove a core extension and move it to a contributed project and the Extensions approved for removal policies.
It will be moved to the contributed Action project when the Drupal 11 branch is open.
Comment #25
quietone commentedI was on 'autopilot' and the above comment is wrong. It is the Action UI that is being removed. Restoring status.
Sorry for the noise.
Comment #27
quietone commentedSince this is not about the Action UI, moving to the base system.