Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.The D9 release plan for Smart Trim is:
Wait until core 8.8.0 is released.
Start fixing 9.x compatibility bugs in sub-issues, not in this one.
Aim to have a release of Smart Trim that is fully compatible with 8.x and 9.x the day that 9.0 is released.
This seems generic because the upgrade from D8 to D9 will be pretty generic for the vast majority of modules.
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | smart_trim-n3092581-4.patch | 411 bytes | damienmckenna |
| #3 | 3092581-smart_trim-drupal-9.patch | 257 bytes | markie |
Comments
Comment #2
jenlamptonAre there any sub-issues other than https://www.drupal.org/project/smart_trim/issues/3042672?
Comment #3
markie commentedI think the only thing that needs to happen still is adding the `core_version_requirement: ^8 || ^9` into the info.yml.. which the following patch does.. I tested this in the latest dev version of d9 and the module works. Please test and tell me differently (if you find it)
Comment #4
damienmckennaYou should remove the "core" line too.
Comment #5
markie commentedI applied the #4 patch and tested locally. Anyone else want to give it a try, or I'll commit it later.
Comment #6
yogeshmpawarHi @markie - I think you need to commit #3 because of these two change records - https://www.drupal.org/node/3119415 & https://www.drupal.org/node/3070687
As mentioned in the change records -
This specifies that the module is compatible with all versions of Drupal 8 and 9. The core:is required here because Drupal Core versions before 8.7.7 do not recognize the core_version_requirement: key.If this module is only compatible with greater then drupal core 8.7.7 then -
The core: key must not be used here to make sure that versions of Drupal before 8.7.7 will not install the module. Adding both core and core_version_requirement with anything other than core_version_requirement: ^8 || ^9 will result in an exception.Comment #7
damienmckenna@yogeshmpawar: While technically correct, if a site hasn't updated to 8.7.7 since its release last September their site is vulnerable to bugs fixed in 8.7.11 and 8.7.12, so I don't think maintainers should make too much of a fuss.
Comment #9
markie commentedMerged #4. Thanks for your help
Comment #10
yogeshmpawar@DamienMcKenna - Agreed on your comments. Thanks
Comment #11
kristen polTo qualify for the DrupalCares challenge, there needs to be a new release of the module that is D9 compatible. Deadline is today :) The info file was updated in this issue and #3042672: Drupal 9 Deprecated Code Report is fixed so is there any reason not to tag a release?
UPDATED: You probably want to update your issue credit checkboxes too because I see Jen was credited in the commit but not as an issue credit.
Comment #12
kristen polChatted with @markie in Slack and there is a regression to be dealt with before making a new release. I'll make a new issue for specifically this task because this issue is already marked fixed.
UPDATED: I added an explicit ticket for both the release and the project page update: https://www.drupal.org/project/smart_trim/issues/3132567