Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Problem/Motivation
currently the node module still contains deprecated code.
Proposed resolution
Remove the following items:
- Remove
\Drupal\node\NodeAccessControlHandler(Interface)::writeGrants()
- Remove
node_delete_action
action - Remove
node_publish_action
action - Remove
node_save_action
action - Remove
node_unpublish_action
action
Comment | File | Size | Author |
---|---|---|---|
#13 | interdiff-3108851-2-13.txt | 496 bytes | JeroenT |
#13 | 3108851-13.patch | 9.18 KB | JeroenT |
#3 | 3108851-2.patch | 8.57 KB | JeroenT |
Comments
Comment #2
andypostComment #3
JeroenTComment #4
JeroenTComment #5
JeroenTComment #6
JeroenTComment #7
BerdirTry searching for @trigger_error() and @deprecated in the whole module, there's quite a bit more to remove. And then also "group legacy" for any tests that are covering the things we are removing.
Comment #8
BerdirUpdating the parent issue. we don't want to remove the whole module :)
Comment #9
Wim Leers😆
Comment #10
JeroenT#7 @Berdir, I searched for @deprecated, trigger_error and group legacy in the node module, but I didn't find anything. Am I missing something?
#8: Woops! 🤦♂️
Comment #11
JeroenTComment #12
Wim LeersWe also still need to remove the implementation of this, at
\Drupal\node\NodeAccessControlHandler::writeGrants()
.Comment #13
JeroenTah good catch.
Comment #14
Wim LeersReally tempted to mark this RTBC, but let's wait for DrupalCI to confirm tests are still passing, and let's wait for @Berdir to respond with what other things he spotted that should be removed.
Thanks for opening this issue, the clear issue summary and the patch, @JeroenT! 🙏
Comment #15
BerdirSorry about that, I probably looked at the wrong branch, we already did node module in #3097428: Remove node.module BC layers
Comment #16
alexpottCommitted 5fca5fe and pushed to 9.0.x. Thanks!
So this was deprecated before our deprecation policy was defined. So there's no @trigger_error() BUT it has been deprecated for the nearly entirety of the Drupal 8 cycle and is completely untested and any contrib or custom implementations of the interface will not be broken by the removal so I think this okay.
Comment #19
AaronBaumanI'm running into WSODs for drupal core views that relied on these, and I'm not the only one.
See #3045570: Plugin missing for node actions
How are/were these views supposed to get updated?
The actions were deprecated, and the install config was updated, which is good for new installs.
D8 early adopters are left in the lurch.
Sorry to necropost, but before I open a new issue I thought I'd check here.
Comment #20
andypost@AaronBauman Please file new issue and link it here, migrations should be in-place as the issue just removes remains
Comment #21
AaronBaumanok, new issue: #3229700: Need update path for deleted core actions