Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Problem/Motivation
There are/will be some deprecated modules in Drupal 9. They should be added to the issue here once they are already deprecated in 9.x as part of this list: https://www.drupal.org/project/drupal/issues/3118154#modules.
Proposed resolution
Remove modules where agreement was made and modules were deprecated in Drupal 9.
Remaining tasks
None :-)
Done
- Seven #3278331: [Meta] Tasks to remove Seven from core and move to contrib
- Classy #3308518: [Meta] Tasks to remove Classy theme from core and move to contrib
- Farbtastic. #3306210: Remove Farbtastic library from core
- Aggregator and Laminas. #3274189: [Meta] Tasks to remove both Aggregator and our dependency on Laminas Feed
- RDF. #3273976: [Meta] Tasks to remove RDF from core and move to contrib
- Quickedit. #3274155: [Meta] Tasks to remove Quick Edit from core and move to contrib
- Color. #3274149: [Meta] Tasks to remove Color from core and move to contrib
- Migrate Drupal Multilingual. #2966859: Remove Migrate Drupal Multilingual module in Drupal 10
- Hal. #3049857: Remove HAL module from core and create a contrib project for it
- CKEditor 4. #3306563: [Meta] Tasks to remove CKEditor (4) from core and move to contrib
- Bartik #3278332: [Meta] Tasks to remove Bartik from core and move to contrib
- Stable #3308986: [Meta] Tasks to remove Stable theme from core and move to contrib
There is a test, MigrateColorTest, that relies on Bartik. To avoid failing tests, Color is planned for removal first, following closing, hopefully the same week, by Bartik.
Comments
Comment #2
gábor hojtsyComment #3
gábor hojtsyAdding migrate.
Comment #4
dwwWhat's the relationship of this issue to #3118154: [meta] Deprecate dependencies, libraries, modules, and themes that will be removed from Drupal 10 core by 9.4.0-beta1? How can #3227033: Remove Quick Edit from core fit into this since it can't have multiple parents / ancestry?
Adding both as related for now.
Thanks,
-Derek
Comment #5
longwave10.0.x is under development and we are starting to remove things, so this can be active now, but I also don't quite understand the relationship with the other meta.
Comment #6
gábor hojtsy#3118154: [meta] Deprecate dependencies, libraries, modules, and themes that will be removed from Drupal 10 core by 9.4.0-beta1 is supposed to be about marking things for removal on 9.4.x (including but not limited to modules) while this META is for actually removing them on 10.x. The separation would make more sense if we did more of the deprecations earlier, but that is what we have now. I think the deprecation and removal issues are still distinct and also the 9.4.0 beta may be at a different time than a 10.0.0 beta, so it still makes sense to separate the tracking and be able to close that when done.
Comment #7
xjmUpdating the IS to list only things that are actually already deprecated
Comment #8
quietone commentedI have the same type of question as #4 and #5, that is, is this issue needed?
With this issue we are tracking the removal of module in two places. Here and the Meta issues tracking the 'deprecation to removal' process for each module, according to the Modules and themes policy, have a step and issue specifically for the 'removal'. That meta also includes the steps to be done post the actual removal, like composer and documentation.
I do see that the new policy for the module deprecation process needs work to identify the version an issue is filed against and will try to get to that this weekend.
Comment #9
xjmUpdated the IS to be more clear. Once a module is deprecated, removing it from 10.0.x is a beta blocker for D10. Otherwise, there is no beta blocker.
With the exception of Aggregator and QuickEdit, all module deprecations are 100% optional. This is part of why mixing 9.4.x work and 10.0.x work in the 9.4.x deprecation meta is not correct.
This issue is to track the must-have followups to the deprecations that are already complete.
Comment #10
xjmComment #11
xjmComment #12
quietone commentedAdd all module removals to the Issue Summary.
Comment #13
quietone commentedComment #14
quietone commentedDiscussed with catch and xjm, the order of removal for Color and Bartik because of the test dependency discussed in the IS of #3301713: Update migration Color tests to not use Bartik. Color will be first followed closely by Bartik.
Comment #15
quietone commentedFix formatting
Comment #16
quietone commentedAdd Farbastic
Comment #17
quietone commentedComment #18
quietone commentedupdate link to CKEditor
Comment #19
chris matthews commentedIs the Book module still planned to be removed from core?
[Policy] Deprecate book module and move it to contrib in Drupal 10
Comment #20
quietone commented@Chris Matthews, the policy issue you refer to would have to be RTBC before the process of deprecation and removal began.
Moved the following to Drupal 11
Comment #21
bbralaComment #22
bbralaToo optimistic, still need some documentation moving.
Comment #23
quietone commentedComment #24
quietone commentedComment #25
wim leersCKEditor 4 removal is complete!
Comment #26
quietone commentedThe remaining work on the themes is to triage the respective issue queues.
Comment #27
quietone commentedCelebrating that removing Bartik is done.
Comment #28
quietone commentedUpdate IS, Bartik and Stable are complete.
Comment #29
quietone commentedThis can be closed now.