Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
I think this is the follow-up I suggested in another ticket, thanks for that. I changed the issue title, because this is resolving deprecations, not supporting Drupal 9.3; the latter suggests the module does not work without this patch. Actually, merging these changes would make the module incompatible with Drupal 9.2, so that would have to wait until D9.2 is no longer supported. Lastly, because of that, I also think the info.yml needs an update to denote that the module is only compatible with D9.3+.
Comments
Comment #2
ash2303 commentedComment #3
ash2303 commentedComment #4
eelkeblokI think this is the follow-up I suggested in another ticket, thanks for that. I changed the issue title, because this is resolving deprecations, not supporting Drupal 9.3; the latter suggests the module does not work without this patch. Actually, merging these changes would make the module incompatible with Drupal 9.2, so that would have to wait until D9.2 is no longer supported. Lastly, because of that, I also think the info.yml needs an update to denote that the module is only compatible with D9.3+.
Comment #5
eelkeblokComment #6
aaron.ferris commentedComment #7
aaron.ferris commentedComment #8
aaron.ferris commentedThis will need work, although certain aspects of the patch will still apply others won't - please raise an MR. (Appreciate its old!)
Comment #9
aaron.ferris commentedIve reviewed these changes, they're not applicable anymore as far as I can tell.
Comment #10
aaron.ferris commented