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
Stable9 will not be removed from Drupal 10.
This means that any leftover templates/CSS files referencing removed (in D10) core modules should be removed from this theme.
Steps to reproduce
Proposed resolution
Find leftover templates/CSS files referencing removed (in D10) core modules in Stable 9
Remove them
Remaining tasks
User interface changes
API changes
Since none of the templates removed in this issue were changed during Drupal 9, there is no impact on markup whether subthemes override templates or not.
Data model changes
Release notes snippet
Comment | File | Size | Author |
---|---|---|---|
#11 | 3307225-11.patch | 9.78 KB | Spokje |
| |||
#11 | interdiff_9-11.txt | 886 bytes | Spokje |
Issue fork drupal-3307225
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
- 3307225-remove-leftover-templatescss changes, plain diff MR !2713
Comments
Comment #3
SpokjeComment #4
SpokjeTried to be positive about it, but I just switched back to a patch-only workflow until there's some better hardware in place.
Just can't hang around for 20+ minutes to make sure a commit will eventually popup or not.
Comment #6
SpokjeComment #7
quietone CreditAttribution: quietone at PreviousNext commentedI applied the patch and did lots of searching (grep and find) in core/themes/stable* for the removed modules. Grepping "color" was a bit of fun :-)
I just found one thing that I am not sure about in all the themes stable9 is the only one with a directory and file for ckedito,r core/themes/stable9/css/ckeditor/plugins/language/ckeditor.language.css. Is that needed?
Comment #8
SpokjeThanks @quietone, very nice catch.
At the moment of creating this issue the ckeditor module was still "In Tha House" (meaning still in core both in Drupal 9 and 10).
Since it's now officially gone from d10, I see no reason why it's still supported by Stable9. In fact I think it's an oversight since it was removed from Stable in #3270438: Remove CKEditor 4 from core
I've uploaded a new patch nuking that file.
Comment #9
SpokjeWith the arrival of #3308986: [Meta] Tasks to remove Stable theme from core and move to contrib we can remove the stable references in this patch.
Comment #10
longwaveThis looks pretty close but I found one more straggler:
themes/stable9/templates/admin/color-scheme-form.html.twig
is part of Color module.Comment #11
SpokjeThanks @longwave. I think "stragglers" is becoming the word-of-the-release-beta week :)
Comment #12
longwaveComment #13
nod_Should the forum twig files be removed as well?it's still there.Looks complete to me.
Comment #14
Wim LeersPer @xjm.
Comment #15
SpokjeComment #18
xjmBefore patch:
After patch:
Committed to 10.1.x and cherry-picked to 10.0.x. Thanks!
Comment #19
phenaproximaUnless I'm missing something here, sites which are using Stable 9, or a subtheme of it, and also have one of these now-removed modules (or their contrib versions) installed, will be partially broken.
Therefore, this probably means that the modules in question need to re-implement these changes (follow-ups?), but at the very least this should have a change record.
Comment #20
longwaveI don't think this will break anything. The Stable and Stable 9 themes were designed so we could update core CSS and templates without breaking backward compatibility. However, in the Drupal 9 cycle we did not update any of the templates that were removed in this patch.
Let's take the case of aggregator-item.html.twig. If someone overrode this in their subtheme of Stable 9, then the overridden version will take precedence now, as it did before. If they did not override it, the template from Stable 9 is now gone, but this will just fall back to the aggregator-item.html.twig template shipped with Aggregator module itself, and the end result will be no different.
I double checked all the templates and CSS removed in this patch and the only difference is in comments and relative paths to assets; there are no structural changes.
Given the above, I am not even sure this needs a change record.
Comment #21
catchlongwave's explanation for why this doesn't need a change record makes sense to me. I updated the API changes section of the issue summary to add that explanation, just in case someone lands on this issue and wonders the same thing.