Closed (fixed)
Project:
Drupal core
Version:
11.x-dev
Component:
shortcut.module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
23 Jan 2026 at 05:41 UTC
Updated:
5 Sep 2026 at 08:10 UTC
Jump to comment: Most recent
Comments
Comment #3
quietone commentedComment #5
andypostas removed from standard profile/recipes
Comment #6
andypostLooks before deprecation we need to split tests via #3569152: Move some test coverage to the Shortcut module
Comment #7
quietone commentedThis is postponed on the sibling issues.
Comment #8
andyposttests moved
Comment #9
andypostLooks ready to go
Comment #10
andypostCR https://www.drupal.org/node/3578141
Now needs a page update at https://www.drupal.org/docs/core-modules-and-themes/deprecated-and-obsol...
Comment #11
quietone commentedThis is postponed on the sibling issues. I have updated the issue summary.
Comment #12
andypostSiblings are commited and project moved to contrib already
Comment #13
smustgrave commentedlets do it!
Comment #15
sivaji_ganesh_jojodae commentedThe test method
testAccessShortcutsPermissionis throwing error.Comment #16
nicxvan commentedDoes the core module list provider need to be updated?
Comment #17
smustgrave commentedSeems the ignore deprecation was removed in #3576579: Tidy up and tighten deprecation ignores and tests marked #[IgnoreDeprecations] where no deprecations are triggered by mistake. Since it was a small fix moving back
Comment #18
catchThese three tests shouldn't be changed here, we need to refactor them to not rely on shortcut module, or move shortcut-specific assertions to shortcut module, or something like that.
Comment #19
quietone commentedJust catching up here.
The deprecation issue for an extension should only have the deprecation nothing else. The issue summary has the correct scope. All the other steps in the parent need to be completed. The parent issue should always been checked for anything remaining instances that need to be changed. I do see my earlier comment wasn't clear on that point, so trying again now.
Comment #20
smustgrave commentedBlockers are in
Comment #21
smustgrave commentedAdded a section to https://www.drupal.org/node/3223395
Rebased the MR and updated the link to include s-
Believe we are good here.
Comment #22
andypostLooks ready
Comment #23
quietone commentedThere is a failing test, core/modules/shortcut/tests/src/Functional/NavigationSafeBlockDefinitionTest.php
Comment #24
smustgrave commentedckeditor5 failures I believe are unrelated
Comment #25
quietone commented#18 has not been addressed here. And like those, I think NavigationSafeBlockDefinitionTest.php needs to be redone, a Navigation test should not be loading a deprecated plugin.
We need a new issue for those 4 tests.
Comment #26
smustgrave commentedIt’s a shortcut test? I don’t follow
Comment #27
quietone commentedComment #28
quietone commentedThere are two tests with the same name and I got them mixed up. Sorry about that!
So, it is just $18 which can be done in #3617978: Adjust more tests to deprecate Shortcut
Comment #29
quietone commentedSo, it turns out that those tests do not need the IgnoreDeprecations attribute.
Now there is only one test where an IgnoreDeprecations is added outside of the shortcut module. That is core/tests/Drupal/KernelTests/Core/Extension/ModuleConfigureRouteTest.php.
Comment #30
smustgrave commentedSo believe this one is good to go?
Comment #33
catchCommitted/pushed to main and 11.x, thanks!
Manually resolved a merge conflict in
ModuleConfigureRouteTestwhen cherry-picking to 11.x - just the code comment was different.Comment #35
andypostCR looks like need update as removal supposed in 13.x
Comment #36
catch@andypost no this will still be removed in Drupal 12.0.0 - where we're moving modules contrib we've been doing that right up until the next major release because it tends to be a very easy change for sites to make.
Comment #38
catchHad to revert from 11.x https://git.drupalcode.org/project/drupal/-/jobs/11698894 - update and migrate test failures.
Comment #39
quietone commentedThe tests are fixed in #2672340: user_user_role_insert should not exist, so lets wait for that to be committed.
Comment #41
catchAh I should have realised those were the same test failures. That issue landed, so re-applied this to 11.x, thanks!
Comment #43
catchKicked off a manual daily pipeline after both commits went into 11.x and confirmed this doesn't introduce any new test failures on the branch.