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
Per #2533886: [meta] Move module-specific migration support into the particular modules supported, move support for system migration into the system module.
Proposed resolution
For the most part, this is a matter of moving files around and updating namespaces. Also, explicit destination module dependencies can be removed.
Migration templates to be moved:
- d6_system_cron
- d6_system_file
- d6_system_filter
- d6_system_image
- d6_system_image_gd
- d6_system_logging
- d6_system_maintenance
- d6_system_performance
- d6_system_rss
- d6_system_site
Remaining tasks
Submit a patch.
User interface changes
N/A
API changes
Namespaces of affected migration plugins will change.
Data model changes
N/A
Comment | File | Size | Author |
---|---|---|---|
#7 | interdiff.txt | 3.61 KB | mikeryan |
#7 | move_module_specific-2534032-7.patch | 17.52 KB | mikeryan |
|
Comments
Comment #1
mikeryanMoved d6_url_alias to a separate issue for the path module - although the url_alias schema is installed by the system module, we only want to migrate aliases if the path module is enabled, so that's the proper place for that migration.
Comment #2
mikeryanHere's the patch, postponed on #2534158: MigrateFullDrupalTestBase must use dynamic test discovery.
Comment #3
phenaproximaUnblocked.
Comment #4
phenaproximaLooks fine.
Comment #5
mikeryanBased on applying all the move patches, I believe the following should also move into the system module:
Comment #6
mikeryanOh, and d6_menu.yml and other menu-related files...
Comment #7
mikeryanComment #8
phenaproximaLooks lovely and straightforward to me.
Comment #9
alexpottCommitted 1743f6c and pushed to 8.0.x. Thanks!