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.We should take advantage of the 3.x branch and 3.0.0 release to clean house a little bit. The following modules are not used by Lightning and are not used by any of the previous five releases (which we test in CI) - and should be removed:
- scheduled_updates
- lightning_scheduled_updates
- features
- config_update
- media_entity
- media_entity_document
- media_entity_image
Comments
Comment #2
gg4 CreditAttribution: gg4 commentedCan you provide any more information regarding the motivation for this issue?
Comment #3
balsamaHi.
Scheduled Updates (the module) does work with Content Moderation. So when we migrated to Content Moderation, we implemented a new solution for scheduling changes to entities' moderation states. That leaves Scheduled Updates in our codebase, but unused by Lightning.
If we just remove it, people who rely on it for other reasons would have broken functionality. So we need to come up with a plan to announce when we're going to remove it so users have a chance to add it as a dependency to their own project.
Comment #4
balsamaLet's just do this in the 3.x branch and include it in our release notes. We should also remove the following modules which Lightning no longer uses:
Comment #5
balsamaWe can also remove Media Entity and it's related modules from our codebase. I'd like to remove WBM too, but we still test that update path. We can remove that in 3.0.2.
Updated IS
Comment #6
balsamaCommitted as part of the 3.x branch:
https://github.com/acquia/lightning/commit/a3f0cf75ff83794b14adc3ac63023...
Comment #8
dalinI'm about to update several sites from Lightning 2.17 where media_entity, media_entity_document, and media_entity_image *are* in use. What's the recommended way forward?