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
See #3278332: [Meta] Tasks to remove Bartik from core and move to contrib and #3249109: Deprecate Bartik. Now that Olivero is the default theme for Drupal core, it's time to move Bartik to a contributed project.
Steps to reproduce
Proposed resolution
Remaining tasks
The change record for this issue should include a link to recommendations page, https://www.drupal.org/node/3223395#s-MODULE_NAME. (For example, the CR for removing HAL)Tag this issue 'Needs release note.- Remove the module ;-).
- Remove references from core/phpstan-baseline.neon.
Check for references in @todo.Handle migration tests.In all the functional tests in migrate_drupal_ui make sure that MODULE_NAME is not installed. MODULE_NAME should also be removed from the methods getAvailablePaths() and moved to getMissingPaths() in the tests using those methods.
User interface changes
API changes
Data model changes
Release notes snippet
The Bartik theme has been removed from Drupal 10.0.0, and is now available as a contributed theme. Sites using Bartik should install the contributed theme prior to updating to Drupal 10.
Issue fork drupal-3304256
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:
Comments
Comment #4
longwaveFirst pass, did not regenerate the dictionary yet. Will conflict with the Seven removal patch in a few places, but that's to be expected.
While grepping for Bartik I found a bunch of out of date docs and opened #3304650: Theme stylesheet documentation is out of date
Comment #5
quietone CreditAttribution: quietone at PreviousNext commentedAdding parent, remaining tasks and change record etc
I don't expect any migration tests needs changes and I see that the failing test is not a migration tests, so removing that from remaining tasks.
Comment #6
quietone CreditAttribution: quietone at PreviousNext commentedNothing found in the @todo.
Comment #7
catchThe classy fail looks like the hash test is including comments in classy.theme, and we just need to update the hash because the comments changed. I think?
Comment #8
lauriiiComment #9
mherchelLooking through this, I searched the codebase for "bartik"
I found a number of things that could be removed (not sure if these are in scope).
"themes/bartik/color/preview.html",
in core/.cspell.jsonNot sure all of these are valid, but I think some may be.
Comment #10
quietone CreditAttribution: quietone at PreviousNext commentedGood point to search for bartik, so I checked as well.
First for migrate related.
@mherchel is right, the references to bartik are valid. MigrateColorTest does depend on Bartik being installed but the plan is to remove Color first, then Bartik.
Then for not migrate related
I've made a note to add more thorough searching to the steps to remove a module/theme.
Comment #11
longwaveThe cspell config needs updating, and the dictionary regenerating.
Opened #3304650: Theme stylesheet documentation is out of date for this as the problem is wider than just renaming something.
RDF is also on its way out so I left this alone, but we can fix it here I guess.
Comment #13
dwwRe-ran the recursive grep from #10 (thanks @quietone for posting that!) with the MR branch checked out, and still had:
So I pushed a commit to fix 1 + 2. 😅
Also fixed the file hash in
ClassyPreprocessUnchangedTest
now thatclassy.theme
has changed (only to remove 'bartik' from some comments). Fixed thatassertSame()
to put the expected value as the 1st param, while I was at it.The other test fails don't make much immediate sense, but I don't really have time to investigate now. Maybe random fails? Let's see. 🤞
Comment #14
dwwYeah, passes locally:
Let's hope the bot agrees on this run.😅
Comment #15
dwwYay. So only the release note and the cspell directory regeneration are needed.
Back to NR to get more eyes on this in case anyone spots something else.
Thanks,
-Derek
Comment #16
catchComment #17
catchAdded a release note.
Comment #19
catchWent ahead and committed #3270899: Remove Color module from core which means this needs a re-roll/rebase.
Comment #20
SpokjeYay, one more extension removed!
Let's see if I can do the reroll/rebase
Comment #21
SpokjeRerolled, left comment on the only open thread in GitLab.
Comment #22
lauriiiConfirmed that all of the changes to existing code makes sense. 👍 I was surprised how many references there were still pointing to Bartik 😅 Also confirmed that all of the remaining references to Bartik are related to migration. 👍
Does this need a change record given that we already published https://www.drupal.org/node/3304352? 🤔
Prepared issue credits for another committer ✌️
Comment #23
lauriiiForgot to mention that I also tested manually installing Drupal without Bartik and all worked as expected 👍
Comment #25
catchYeah I was also surprised by the number of Bartik references left, I guess it's test failures vs. grep.
I updated the existing change record since that covers both the deprecation and removal.
Thanks to everyone who worked on this (and on adding Bartik to core in the first place, it did really well for over a decade).
Committed/pushed to 10.1.x and cherry-picked to 10.0.x, thanks!
Comment #27
xjmComment #28
quietone CreditAttribution: quietone at PreviousNext commentedAdded a CR specific for the deprecation, so the branch/version information is correct, and published it.wrong issue
Comment #30
smustgrave CreditAttribution: smustgrave at Mobomo commentedClosed #3259925: Use Olivero instead of Bartik as example theme in documentation as a duplicate and moved over credit.